For the complete documentation index, see llms.txt. This page is also available as Markdown.

MCP Inspector

The MCP Inspector is a user interface for documenting and testing MCP tools on an MCP server. There is one Inspector per MCP flow.

Access

For the MCP Inspector to be reachable in a given environment, the Enable Flow Service checkbox must be selected in the Environments page.

There are two ways to open the MCP Inspector for a flow:

  • Inside an MCP flow, click the tools icon in the toolbar, then click MCP Inspector for the relevant environment.

  • Visit the URL https://SOLUTION-HOSTNAME/api/mcp/API-ROOT-PATH in a browser. The solution hostname is environment-specific.

Access to the MCP Inspector is authenticated and requires a role with client access to the environment. The Inspector is available regardless of the Allow external client access setting.

Usage

The Tools panel on the left lists every MCP tool the flow exposes, with each tool's name and description. Selecting a tool opens its detail view, with input fields for the tool's action params (if any) and an Execute button.

Click Execute to call the tool. The response appears under Result as the same JSON payload that an external MCP client would receive — an object containing the action variables and action data sources marked Return from action.

When you call a tool from the Inspector, it runs as your user with your assigned roles. This means that during testing you will often have full access to all object classes and flows. When an external client calls a tool, it runs as the user who approved the connection. If a tool works for you in the Inspector but not when called from a connected app, make sure the connecting user has sufficient permissions.

Last updated

Was this helpful?