Free Tool

Free MCP Inspector Command Generator

An MCP Inspector command generator builds ready-to-run terminal commands for testing Model Context Protocol servers. Choose npm, PyPI, local Node, local Python, or remote HTTP/SSE, add server arguments and environment variables, then copy a command for the Inspector UI or a repeatable CLI smoke test.

MCP Inspector command builder

Pick how your MCP server starts, add arguments and environment variables, then copy a command for the Inspector UI or CLI smoke tests.

Server type
Output

Environment variables

How to generate an MCP Inspector command

  1. Choose the server type. Pick npm, PyPI, local Node, local Python, or remote HTTP/SSE based on how your MCP server is started.
  2. Enter package, path, URL, and arguments. Add the server package name or local entry point, then paste the arguments that the server expects.
  3. Add environment variables. Include local API keys, tokens, or feature flags as environment variables so the server starts with the same settings your MCP client uses.
  4. Copy the UI or CLI command. Use Inspector UI mode for interactive debugging, or CLI mode to list tools and run repeatable terminal smoke tests.
  5. Open Inspector and test capabilities. Connect to the server, check capability negotiation, inspect tools and resources, and test edge cases before wiring the server into a production client.

Common MCP Inspector command patterns

npm package servers

Use npm package mode when a server starts with npx. This is the fastest path for official and community MCP servers published to npm.

Python package servers

Use PyPI mode for servers that run through uvx. It keeps the Inspector command short while still allowing repository paths, tokens, and custom arguments.

CLI smoke tests

Switch to CLI smoke test mode when you want a scriptable command for checking tools, prompts, or resources after a server change. This is useful before adding the server to Claude Code, Cursor, Codex CLI, or another MCP client.

MCP Inspector FAQ

What is the MCP Inspector?

The MCP Inspector is an interactive tool for testing and debugging Model Context Protocol servers. It can launch a local MCP server, connect to it, and inspect tools, prompts, resources, notifications, and protocol messages.

How do I run MCP Inspector for an npm server?

Use npx to launch the Inspector and pass npx plus the MCP server package name as the server command. For example, use the generator's npm package mode and enter the package plus any server arguments.

Can MCP Inspector test Python MCP servers?

Yes. Use uvx for a published Python MCP package, or use uv with --directory and run for a local Python project. The generated command keeps package arguments and environment variables together.

What is MCP Inspector CLI mode for?

CLI mode runs protocol operations from the terminal, such as listing tools or calling a tool. It is useful for smoke tests, CI scripts, and quick checks after changing a server.

Should I put API keys in the generated command?

Use environment variables while testing locally and avoid committing commands with real secrets. Replace sample values before sharing logs, scripts, or issue reports.

Related tools

MCP Server Config Generator

Create MCP client config for Claude Code, Cursor, Codex CLI, Claude Desktop, and VS Code.

Open tool

Claude Code Settings Generator

Generate Claude Code settings JSON with permissions, env vars, and model defaults.

Open tool

AGENTS.md Generator

Create repository instructions for OpenAI Codex and coding-agent projects.

Open tool