Test any remote MCP server in your browser
Paste an HTTPS endpoint, optionally add a token and see the server capabilities, tools, resources and prompts it exposes.
Know what a server exposes before you wire it into an agent.
The official MCP Inspector is the reference tool for exploring and debugging MCP servers. This browser-based tester follows the same core flow: initialize a client, discover capabilities and list the tools a server makes available.
Paste a remote Streamable HTTP endpoint, add a Bearer token or X-API-Key only when the server needs one, and inspect the response without installing a local CLI. Your credentials are sent only with the test request and are not stored by this page.
When a tool looks useful, select it, provide a JSON object and call it from the same surface. That makes the gap between connection success and useful behavior visible early.
Inspect the connection before you trust the workflow.
A useful MCP test is about more than getting a 200 response.
See the tool surface
Read tool names, descriptions and input schemas as the connected client receives them.
Keep auth optional
Test public servers directly or send a Bearer token or X-API-Key for one request.
Run a real call
Select a tool, enter JSON arguments and inspect the returned MCP result in place.
Four checks before your agent depends on an MCP.
Use the tester to turn a server URL into evidence.
- 01
Paste the endpoint
Enter the public HTTPS MCP URL you want to inspect.
- 02
Add auth if needed
Choose Bearer or X-API-Key when the remote server requires it.
- 03
List capabilities
Review tools, resources, prompts and the server information returned.
- 04
Call one tool
Run a representative JSON request and check the result before integration.