BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to the Claude Observatory

@mcp-use/inspector

Connector Development Solid
Works inClaude Code Claude Cowork Claude Chat
Solid Scanned — metadata only

Reduces debugging time and integration friction when deploying Claude MCP servers by providing real-time visibility into server state, request/response flows…

MCP Inspector - A tool for inspecting and debugging MCP servers

10,342 starsMIT (commercial OK)FreeNo code needed

Reduces debugging time and integration friction when deploying Claude MCP servers by providing real-time visibility into server state, request/response flows, and error conditions.

Platform engineers and DevOps teams integrating MCP servers into production Claude deployments.

Claude Code Claude Cowork Claude Chat

https://www.npmjs.com/package/@mcp-use/inspector

By GitHub Actions

How to Get It

Option 1: Claude Desktop AppOpen the Customize panel in the sidebar → browse connectors → search and add. Works in Claude Code, Claude Cowork, and Claude Chat.
Option 2: Paste into Claude CodeCopy the command below and paste it into a Claude Code conversation. Claude will run it for you.
Command
npx -y @mcp-use/inspector

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.

First thing to try

Once it’s connected, paste this into Claude:

Help me debug MCP server connections and identify why integrations fail unexpectedly
CostFree

Trust Signals Auto-scanned

Stars10,342Last updated2026-07-23LicenseMIT (OK for commercial use)Weekly downloads50,435Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-07-23 · scanner v1

Data & Access

Data processingPrompts sent to Anthropic API. Enterprise/Team plans exclude training.

Community Pulse New

No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 10,342 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

Things to check

  • Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation

Ease of Use
4/5
Versatility
5/5
Reliability
3/5
Security
3/5
Overall score3.85 / 5.00 SolidEvaluatedJul 2026
Scored from trust signals (evidence-eval-v1): 10,342 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

← Back to the Claude Observatory

Rolling Claude out in your org? Let's talk.

Start a conversation →