MCP InspectorVerified

@modelcontextprotocol

Basic information

About MCP Inspector

Visual testing tool for MCP servers

MCP Inspector config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "inspector": {
      "command": "npx",
      "args": [
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}

MCP Inspector tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is MCP Inspector?

MCP Inspector is a developer tool for testing and debugging MCP servers. It consists of a React-based web UI (MCPI) that connects to MCP servers via a Node.js proxy (MCPP) supporting stdio, SSE, and streamable-http transports. It is intended for developers building or debugging MCP server implementations.

How to use MCP Inspector?

Run npx @modelcontextprotocol/inspector to start the UI at http://localhost:6274. To inspect a server from its repository, use npx @modelcontextprotocol/inspector node build/index.js with optional arguments and -e flags for environment variables. A Docker image is also available. Ports can be customized via CLIENT_PORT and SERVER_PORT environment variables.

Key features of MCP Inspector

Interactive web UI for testing MCP servers
Supports stdio, SSE, and streamable-http transports
Bearer token authentication with session tokens
Export server launch configurations as mcp.json
Real-time adjustable timeout settings
Persists configuration across sessions

Use cases of MCP Inspector

Debugging MCP server implementations during development
Testing server tools and resources interactively
Validating server configuration for different transport protocols
Exporting server configurations for use in clients like Cursor or Claude Code

Frequently asked questions

Is MCP Inspector a network proxy for intercepting traffic?

No, it functions as both an MCP client and an HTTP server, enabling browser-based interaction with MCP servers via different transport protocols.

What are the runtime requirements?

Node.js version ^22.7.5 is required.

How does authentication work?

The proxy requires a session token (randomly generated) sent as a Bearer token in the Authorization header. The token is shown in the console and can be pre-filled in the UI.

Can I expose the inspector to other devices?

By default it binds only to localhost. Binding to all interfaces (`HOST=0.0.0.0`) is possible but dangerous because the proxy can spawn local processes.

What transport protocols does the inspector support?

It supports stdio, SSE (Server-Sent Events), and streamable-http transports.

Comments

More Developer Tools MCP servers

OrangePro

Aamir Siddiqui

OrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.

LastPing

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

Perfex CRM

themesic

Turn Perfex CRM into an AI-ready workspace. This MCP server exposes your full REST API to Claude, ChatGPT and any AI agent, so leads, invoices and tasks are one prompt away.

GripForge

gripforgeai

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U

Capgo MCP

Cap-go

Console, Backend and CLI to manage Capgo Instant update and Native build for Capacitor apps Build and upload to app store your mobile app