Skip to main content

Inspector

The MCP Inspector is a visual, interactive tool for testing MCP servers. It enables you to inspect inputs and outputs, and iterate quickly by testing actions in real time without waiting for an LLM or AI agent.
With the Inspector, you can:

  • Discover all available actions in your MCP server.
  • Execute actions with custom inputs.
  • Inspect responses and debug issues.
  • Iterate quickly on action development.

Use this tool to validate your MCP server configuration before connecting to production AI applications.

Using the Inspector​

  1. In the MCP panel, navigate to your MCP server.
  2. In the left panel, click Inspector tab to open the inspector interface.

Open Inspector

Figure 1: Open Inspector Tab
  1. Click Connect to establish a new connection to your MCP server. The Inspector will initialize the connection and negotiate protocol capabilities. A confirmation message will appear once the connection is active.

Establish connection

Figure 2: Connect to MCP Server
  1. Click List Actions to retrieve the list of actions available in your MCP server. The Inspector sends a tools/list request to discover all available actions. Once loaded, you'll see a list of all actions, each with its names and description.

Load Action

Figure 3: List Available Actions
  1. Click on an action from the list to view its details.
    The Inspector displays:
    • Action name: The unique identifier for the action
    • Description: A human-readable description of what the action does
    • Input schema: The parameters the action expects, including types, descriptions, and required fields
    • Example usage: Sample parameter values (if available)

Load Action

Figure 4: Action Details View
  1. Fill in the required parameters for the action.

connecting Inspector

Figure 5: Fill Action Parameters
  1. Optionally provide values for optional parameters.
  2. Click Run Action.
    View the response in the results panel, which shows:
    • Response status: Success or error indication
    • Response body: The structured output from the action
    • Execution time: How long the action took to complete
    • Error details: If the action failed, detailed error information
tip

After you successfully execute actions and verify the results, your MCP server is ready for production use.
Load Action

Figure 6: Action Execution Result

connecting Inspector

Figure 7: Inspector Workflow