모델 컨텍스트 프로토콜(MCP) 서버를 검사하는 개발자용 도구입니다. 단일 패키지 [@modelcontextprotocol/inspector로 제공되며, 서버를 검사하는 네 가지 방법을 제공합니다:

• Web — Node 백엔드를 가진 Vite + React + Mantine 단일 페이지 앱입니다.
• CLI — 자동화, CI, 빠른 에이전트 피드백 루프를 위한 스크립트 가능한 명령줄 클라이언트.
• TUI — Ink로 만든 인터랙티브 터미널 UI.
• mcpdo (experimental) — 연결 CLI: 한 번 연결한 후, 암묵적인 로컬 데몬을 통해 지정된 연결된 연결에 대해 여러 명령을 실행합니다. clients/mcpdo를 참조하세요.

처음 세 개는 하나의 전역 mcp-inspector 바이너리를 통해 실행됩니다; mcpdo는 같은 패키지 내 두 번째 바이너리입니다:

[! 경고] 인스펙터는 비밀 — OAuth 토큰, OAuth 클라이언트 비밀, stdio env: 값 — 을 관리하며, 가능하면 기본적으로 OS 키체인에 저장합니다. 키체인이 없는 기기 — libsecret이나 Secret Service가 없는 Linux, 헤드리스 및 SSH 세션, Termux, 마운트된 볼륨이 있는 컨테이너 — 에서는 키를 제공하지 않는 한 암호화되지 않은 채 ~/.mcp-inspector/secrets.json에 저장됩니다.

MCP Inspector

A developer tool for inspecting Model Context Protocol (MCP) servers. It ships as a single package, @modelcontextprotocol/inspector, that provides four ways to inspect a server:

• Web — a Vite + React + Mantine single-page app with a Node backend.
• CLI — a scriptable command-line client for automation, CI, and fast agent feedback loops.
• TUI — an interactive terminal UI built with Ink.
• mcpdo (experimental) — a connection CLI: connect once, then run many commands against the named connection through an implicit local daemon. See clients/mcpdo.

The first three run through one global mcp-inspector binary; mcpdo is a second binary in the same package:

npx @modelcontextprotocol/inspector                   # web UI (default)
npx @modelcontextprotocol/inspector --cli             # CLI
npx @modelcontextprotocol/inspector --tui             # TUI
npx -p @modelcontextprotocol/inspector mcpdo --help   # mcpdo

[!WARNING] The Inspector manages secrets — OAuth tokens, OAuth client secrets, and stdio env: values — and stores them in the OS keychain, if available, by default. On a machine with no keychain — Linux without libsecret or a Secret Service, headless and SSH sessions, Termux, and containers with a mounted volume — they are saved to ~/.mcp-inspector/secrets.json instead, unencrypted unless you supply a key. See Where secrets are stored for how to get a keychain back, encrypt the file, or keep secrets in memory only.

Upgrading from v1? Read the v1 → v2 migration guide — CLI flags, the new --config vs. --catalog split, the Node engine bump, and what no longer ships.

Repo status. This is the v2 line of the Inspector. Active development happens on v2/main (the develop branch — all v2 PRs target it), which is merged into main at milestone releases; main is the default branch and holds the latest released v2, published to the npm latest tag. The legacy v1 line lives on v1/main — security fixes only, published straight from that branch to the npm v1-latest tag (npx @modelcontextprotocol/inspector@v1-latest). See AGENTS.md for branch/board conventions.

Quick start (development)

Requires Node >=22.19.0.

npm install          # at the repo root; postinstall cascades into every client
npm run build        # web → cli → tui → launcher

For day-to-day web iteration, run Vite directly — fast HMR, no launcher build needed:

cd clients/web && npm run dev

The launcher-driven scripts run the built launcher, so build first:

npm run web        # prod web launcher against clients/web/dist
npm run web:dev    # web launcher in --dev mode (Vite)