Skip to main content
MCPJam Inspector runs three ways: a hosted web app, a desktop app for Mac and Windows, or via your terminal. The web app is HTTPS-only and has no install. Terminal and Desktop support HTTP/S and local STDIO servers.

Web App

Open app.mcpjam.com. HTTPS only. No install. Share servers with your team.

Desktop App

Download for Mac or Windows. HTTP/S and local STDIO.

Terminal

npx @mcpjam/inspector@latest. HTTP/S and local STDIO.

​
Web app

Go to app.mcpjam.com in your browser. No install required. The web app accepts HTTPS MCP server URLs only — for HTTP or local STDIO servers, use the desktop or terminal options below. See Hosted App for more.

​
Desktop app

Download the installer for your OS and run it: The desktop app supports HTTP/S and local STDIO servers, and does not require Node.js.

​
Terminal

Run the command in your terminal: 
npx @mcpjam/inspector@latest
After installing the package, you should see a link to localhost. Open that link up to see the inspector.

​
Docker

Run MCPJam Inspector using Docker, bound to localhost for security: 
docker run -p 127.0.0.1:6274:6274 mcpjam/mcp-inspector
The app is available at http://127.0.0.1:6274. Always use -p 127.0.0.1:6274:6274 (not -p 6274:6274) to keep the inspector local-only. On macOS/Windows, connect to host MCP servers via http://host.docker.internal:PORT instead of 127.0.0.1.

​
Docker with Arguments

You can pass command-line arguments to the Docker container: 
# Launch with STDIO server
docker run -p 127.0.0.1:6274:6274 mcpjam/mcp-inspector -- \
  npx -y @modelcontextprotocol/server-everything

# Launch with HTTP server
docker run --rm -p 127.0.0.1:6274:6274 mcpjam/mcp-inspector -- \
  --url http://host.docker.internal:8080/mcp \
  --name "HTTP Server" \
  --tab tools
For more information check out our docs on Launch from Code
Important for macOS/Windows users:
  • Access the app via http://127.0.0.1:6274 (not localhost)
  • When connecting to MCP servers on your host machine, use http://host.docker.internal:PORT instead of http://127.0.0.1:PORT
Example:
# Your MCP server runs on host at: http://127.0.0.1:8080/mcp
# In Docker, configure it as: http://host.docker.internal:8080/mcp

​
Start with STDIO server

This will open the MCPJam inspector and connect to a STDIO using the commands you provided. 
# Starts MCPJam inspector with a FastMCP server
npx @mcpjam/inspector@latest uv run fastmcp run /path/to/your/server.py
Use Absolute Paths: Always use absolute file paths (e.g., /Users/yourname/project/server.py) to avoid path resolution issues.

​
Start with custom port

This will start the MCPJam inspector with a custom port number. The default port is 6274. 
npx @mcpjam/inspector@latest --port 4000

​
Start with Ollama

This will open the MCPJam inspector and start an Ollama model with the ollama serve <model> command. Make sure you have Ollama installed. 
npx @mcpjam/inspector@latest --ollama llama3.2

​
Start with Configuration File

You can use a configuration file to connect to multiple MCP servers at once: 
# Using npx directly
npx @mcpjam/inspector@latest --config path/to/config.json --server myserver

# If running from the repository
npm run build
npm start -- --config path/to/config.json --server myserver
Note: When using npm start, you need the -- separator to pass arguments to the underlying script.
Example configuration file structure: 
{
  "mcpServers": {
    "everything": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-everything"],
      "env": {
        "HELLO": "Hello MCP!"
      }
    },
    "weather-server": {
      "command": "python",
      "args": ["weather_server.py"],
      "env": {
        "WEATHER_API_KEY": "your-api-key"
      }
    }
  }
}

​
Start with Verbose Logging

Enable verbose HTTP request logging for debugging purposes. This is useful when troubleshooting connection issues with MCP servers. 
npx @mcpjam/inspector@latest --verbose
Or use the short form: 
npx @mcpjam/inspector@latest -v
Verbose mode logs all HTTP requests made by the inspector, which can help diagnose connectivity problems or inspect server communication.