Inspector (MCP Inspector)

The MCP Inspector is a developer tool designed to verify that an MCP server is working correctly. It provides a user interface for manually calling tools and reading resources.

Use Cases

• Debugging: Inspecting raw JSON-RPC messages to find errors in tool execution.
• Validation: Ensuring that tool schemas accurately reflect the required arguments.
• Prototyping: Testing a server's behavior before integrating it with a full AI client.

Developers often use the Inspector to refine their servers before deploying them for use by AI agents.

Payload Inspection with HasMCP

HasMCP takes debugging to a production-grade level with its Payload Inspector and Streaming Debug Console. While traditional inspectors are designed for local development, HasMCP’s tools allow developers to see the "before" and "after" of their data transformations in real-time. By providing visibility into exactly how JMESPath Pruning or Goja JS Interceptors modified a response, HasMCP ensures that developers can fine-tune their optimization logic with precision, leading to higher performance and lower token costs in live environments.

Questions & Answers

What is the primary purpose of the MCP Inspector?

The MCP Inspector is a developer tool used for testing and debugging MCP servers. It provides a UI for manually calling tools and reading resources to verify they function as expected.

How can the Inspector help with tool schema validation?

By using the Inspector, developers can manually input arguments into tool schemas and see if the server processes them correctly, ensuring the schemas accurately reflect the required parameters before deployment.

How does HasMCP extend the concept of inspection to production environments?

HasMCP provides a production-grade Payload Inspector and Streaming Debug Console that allows developers to see real-time data transformations (like pruning or JS-based modification) within the proxy layer.