MCP Inspector

Inspect MCP configuration JSON with safe preset links, private custom validation, and transport-specific fix guidance before you connect any client.

Config Workbench

Custom JSON stays out of share URLs by default. Only safe preset state is encoded into direct links.

Clear
Safe share URL
Privacy This link only includes the selected preset.
Scope This page validates JSON through the Django request flow, but it does not execute MCP servers or call external MCP endpoints.
Workflow Summary
Current source Remote HTTP server
Share mode Safe preset share URL
Servers 1
Transports HTTP
Env-backed servers 0
Errors 0
Warnings 0
Status Review the transport, required fields, and environment usage before you connect this config in an MCP client.
Next step Use the preset share URL for handoff, or paste a private config to compare it against this working example.
Server Checks
remote-api
Transport: HTTP
Required fields Present: url
Missing: none
URL https://api.example.com/mcp
Env usage 0 variable(s)
Validator status No validator issues
Likely fix Confirm the endpoint URL, authentication headers, and transport before connecting to the remote server.
Example Presets
Local stdio server
Preset
Inspect a local filesystem-style server before you wire it into Claude Desktop, Codex, or another MCP client.
Remote HTTP server
Active
Review the required remote URL shape before you connect an HTTP transport from an MCP client.
Remote SSE stream
Preset
Check an event-stream transport before you hand the endpoint to a client that expects SSE.
Env-backed stdio server
Preset
Verify command, args, and environment variables when a local server depends on runtime credentials.
Broken missing-command example
Preset
See how the validator explains a stdio config that is missing the executable command.
What is MCP?

MCP (Model Context Protocol) is an open standard for connecting AI applications to tools and data sources. It defines how AI models can interact with external servers, services, and data stores through a standardized interface.

How MCP Configuration Works

MCP uses JSON configuration files to define connections to servers. Each server entry specifies a command to run, arguments, environment variables, and the transport type. The most common transport is stdio, which runs the server as a subprocess.

Common Use Cases
  • Validating MCP server configurations before deployment
  • Debugging missing fields or incorrect values in config
  • Inspecting server capabilities and settings
  • Converting between MCP server formats
Frequently Asked Questions

What is the difference between stdio and HTTP transports?

stdio runs the server as a local subprocess, which is simpler and more private but requires the server to be installed locally. HTTP/SSE transports connect to remote servers over the network, enabling distributed architectures.

Why is my server config invalid?

Common issues include missing required fields like 'command', incorrect JSON syntax, wrong value types (args should be an array, env should be an object), or unknown field names.

Is my config sent anywhere?

ComUtil processes the JSON through this page to validate it, but it does not execute MCP servers or call external MCP endpoints. Safe share links keep preset state only, and raw custom JSON is not added to the URL by default.