> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/reference/flows/mcp-inspector.md). # MCP Inspector The MCP Inspector is a user interface for documenting and testing [MCP tools](/reference/flows/mcp-servers.md#mcp-tools) on an [MCP server](/reference/flows/mcp-servers.md). There is one Inspector per MCP flow. ## Access For the MCP Inspector to be reachable in a given environment, the **Enable Flow endpoints and schedules** checkbox must be selected in the [Environments](/reference/configuration/environments.md) 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](/reference/flows/mcp-servers.md#enabling-external-clients) 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](/reference/flows/mcp-servers.md#external-clients) 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.appfarm.io/reference/flows/mcp-inspector.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.