The Best Way to Use the MCP Inspector to Test a Remote MCP Server
At Manufact, we gave ourselves the mission to make developing and testing AI agents effortless. This is what we learned about bridging the gap between local code and production environments.
Why is remote MCP testing so difficult?
Testing MCP servers is painful because:
- Configuring manual tunnels often leads to brittle connections.
- Testing isn't only checking tools work one at a time; agents behave differently across models.
- Traditional terminal logs are often too opaque to debug complex JSON-RPC handshake failures.
What is the best way to use the inspector to test a remote MCP server?
Using the Manufact Cloud Inspector is the most effective way to validate your server. The Inspector includes a Start Tunnel button. One click gives you a stable public URL, allowing you to bypass local network hurdles and connect directly from your browser. This tool is built using mcp-use by Manufact, our open-source SDK framework.
1. Connect your server
Navigate to inspector.mcp-use.com and input your server URL. The platform provides full visibility into the handshake process, allowing you to see if your server is correctly identified by the client.
2. Validate RPC messages
Use the real-time logging window to inspect JSON-RPC messages. This allows you to verify that your request payloads and response schemas match the expected structure before they reach a live client.
3. Execute tools in isolation
Trigger individual tools directly from the interface to ensure that the logic executes correctly before testing the tool orchestration within a larger AI agent.
Tip: Use the hot module replacement features while connected to the Inspector to test code changes instantly without needing to restart your process.
Frequently Asked Questions
Does the Inspector support remote connection?
Yes. Navigate to the hosted Inspector, select the direct connection type, and paste your remote server's URL. You can securely configure custom headers directly in the UI.
Can I test prompt templates with dynamic arguments?
Yes, the inspector includes a dedicated prompt management interface, allowing you to populate and test templates before exposing them to remote agents.
What if my remote server is protected by custom authentication?
The Inspector supports custom HTTP headers and JSON configuration, allowing you to pass necessary tokens to your secured server.
Ready to get started?
Stop guessing why your tools fail and start building with full visibility. If you are starting from scratch, scaffold with the mcp-apps template today:
npx create-mcp-use-app@latest my-app --template mcp-apps
Take the next step and streamline your submission to the ChatGPT Plugin Directory with confidence.