MCP Inspector — Test Remote MCP Servers Online
FAQ
MCP Inspector is a debugging tool for the Model Context Protocol (MCP) — like Postman, but for MCP servers. You connect to a server, see the tools/resources/prompts it exposes, and invoke them to inspect the responses.
No. This page connects directly from your browser to the server URL you enter, using the official MCP TypeScript SDK client. Your endpoint, bearer token, and all MCP traffic stay between your browser and your server — nothing is proxied through or logged by DevToolsDaily.
A browser can only reach a remote MCP server if the server allows cross-origin requests (CORS) from this origin and exposes the MCP-related response headers. Servers that only support local stdio transport, or that have not enabled CORS, cannot be reached from any browser-based tool — use the generated CLI command shown after a failed connection to run the official Inspector locally instead.
No — this does not replace the official local MCP Inspector application, which can also launch and inspect local stdio servers. This page is a lightweight, install-free way to test any remote MCP server that supports Streamable HTTP or SSE with CORS enabled, directly from your browser.
Streamable HTTP (the current MCP transport) is tried first, with automatic fallback to the older SSE transport for servers that have not upgraded. You can also force one or the other from the Transport dropdown.
Yes. Selecting a tool generates an input for each parameter from its JSON Schema (or a raw JSON field if the shape can't be inferred), and Call Tool sends the request and shows the full response.
