// devtools · MCPJam/inspector

inspector

inspector es un proyecto de herramientas de desarrollo de código abierto de MCPJam (MCPJam/inspector en GitHub). Tiene 2.246 estrellas en GitHub y 295 bifurcaciones, se publica bajo la licencia Apache-2.0 y se actualizó por última vez en GitHub el 8 de octubre de 2026.

MCPJam Inspector: chat with, inspect, debug, and evaluate MCP servers across clients and models.

★ 2,2k estrellas⑂ 295 bifurcacionesApache-2.0actualizado oct 2026
▦ visual: el README de este proyecto no incluye ninguna captura incrustable,
así que aquí va un marcador. La guía de abajo está completa de todos modos.
// datos del proyecto

Datos del proyecto

Repositorio
MCPJam/inspector
Estrellas en GitHub
2.246
Bifurcaciones
295
Licencia
Apache-2.0
Última actualización en GitHub
8 de octubre de 2026
Tipo de ficha
Guía de instalación completa
Sitio oficial
Official site
// cómo funciona

Cómo funciona

  1. Clarify your goal

    Decide how you will run it: hosted app for HTTPS servers, or locally via npx or desktop for STDIO and local servers.

  2. Get the project

    Start the inspector with npx (or clone and build the Docker image if you prefer containers).

  3. Install and configure

    Connect your MCP server, then explore its tools, resources, and prompts and run them by hand with full JSON-RPC logs.

  4. Run your first task

    Chat against the server in the playground, debug OAuth if you use it, and define eval test cases to catch regressions in CI.

// características

Por qué gusta tanto

Playground with full traces

A cross-client chat interface that emulates host UIs and shows every tool call, agent step, and JSON-RPC message in one timeline, including a widget emulator for app UIs.

OAuth debugger

Step-by-step visualisation of OAuth and related flows, with guided conformance checks across several MCP protocol versions and registration methods.

Manual server debugging

Run tools, resources, templates, prompts, and elicitation flows by hand with complete request and response observability.

Cross-client evaluations

Define test cases with expected tool calls and run them across many models and client configurations, tracking accuracy and latency over time.

Workspaces and skills

Shared server groups sync in real time for teams, and reusable skills can extend model behaviour inside the playground.

CLI, SDK, and CI/CD support

Probe servers and run checks from the terminal, drive inspections programmatically, and gate pull requests with conformance and eval runs.

Advertisement
// ejecútalo

Ejecútalo tú mismo

  1. Clone and build a Docker image (optional)

    There is no published image, so Docker users build from source and keep it bound to localhost.

    git clone https://github.com/MCPJam/inspector.git
    cd inspector
    docker build -t mcpjam/mcp-inspector:local -f mcpjam-inspector/Dockerfile .
  2. Run locally with npx

    This is the quickest local route for HTTP/S and STDIO servers.

    npx @mcpjam/inspector@latest
  3. Connect a server and test

    Open the printed localhost URL, add your MCP server, and run its tools in the playground. # see README for connection steps

    docker run -p 127.0.0.1:6274:6274 mcpjam/mcp-inspector:local # alternative Docker route
// casos de uso

Qué puedes crear

Advertisement
// preguntas frecuentes

Preguntas frecuentes

Who maintains it?

It is maintained by the MCPJam team on GitHub.

Is it free to use?

Yes, the inspector is open source under Apache License 2.0 per its README; MCPJam also offers a hosted app and paid platform features around it.

Does it need a paid API key?

Not for inspecting a server by hand. To chat against it with models or run LLM-based evals you use your own model access through the platform.

How does it compare to a well-known alternative?

The original MCP Inspector from the protocol project focuses on basic manual testing; MCPJam adds cross-client playgrounds, OAuth debugging, evals, workspaces, and CI gating.

How do I get started?

Run npx @mcpjam/inspector@latest, open the localhost link it prints, and connect your server.

// sigue explorando

Herramientas similares

Herramientas de desarrollo

csharp-sdk

The official C# SDK for the Model Context Protocol — build MCP servers and clients in .NET

★ 4,6k estrellasApache-2.0
Ver la guía →
Herramientas de desarrollo

cortex

Generate interactive API docs, typed SDKs in 12 languages and MCP servers from your API specs.

★ 3,2k estrellasMIT
Ver la guía →
Herramientas de desarrollo

java-sdk

The official Java SDK for building Model Context Protocol servers and clients.

★ 3,7k estrellasMIT
Ver la guía →
Herramientas de desarrollo

mcporter

Call MCP servers from TypeScript or the CLI — MCP tools disguised as a simple TypeScript API.

★ 5,1k estrellasMIT
Ver la guía →
Herramientas de desarrollo

rust-sdk

rmcp: the official Rust SDK for the Model Context Protocol — tokio-based servers and clients

★ 4,0k estrellasNOASSERTION
Ver la guía →
Herramientas de desarrollo

GrapeRoot

MCP graph engine that compounds context across AI coding assistants.

★ 1,0k estrellasApache-2.0
Ver la guía →
// alternativas

Alternativas en Herramientas de desarrollo

Los demás proyectos de Herramientas de desarrollo con más estrellas del catálogo de LibreAI: la lista realista de alternativas si inspector no es lo que buscas.

// más en devtools

Más en Herramientas de desarrollo

Proyectos de Herramientas de desarrollo cercanos en el catálogo, los más próximos en estrellas a inspector: sigue explorando a ambos lados.

Consigue inspector

Gratis y abierto: consigue el código fuente, dale una estrella al repositorio y empieza a crear.