広告掲載
MCP.so
ログイン

MCP Inspector認証済み

@modelcontextprotocol

リポジトリホームページ

基本情報

カテゴリ

開発者ツール

ライセンス

NOASSERTION

トランスポート

stdio

作者

modelcontextprotocol

MCP Inspector について

Visual testing tool for MCP servers

MCP Inspector の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

MCP Inspector のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

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

よくある質問

1

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.

2

What are the runtime requirements?

Node.js version ^22.7.5 is required.

3

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.

4

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.

5

What transport protocols does the inspector support?

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

コメント

「開発者ツール」の他のコンテンツ

Casefile

azimov777

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.

3

Foremerge

naw103

Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.

50

Modelglass

Modelglass

Modelglass turns "which model should I use?" into a lookup instead of a guess. Seven tools give your agent live pricing across image, language, video, and audio models. Sourced and versioned, not scraped once and forgott

1

Meticulous

Meticulous

Unipile

unipile

Unipile MCP server: LinkedIn MCP (Sales Navigator, Recruiter), WhatsApp, Instagram, Telegram and email MCP for coding agents. Build your LinkedIn, WhatsApp and email API integration from Cursor, Claude Code, Codex.

広告掲載