Install mcp-inspector with Homebrew, MacPorts

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• mcp-inspector

Project history

The public repository was created under the modelcontextprotocol GitHub organization in October 2024, shortly before MCP tooling became a common dependency of AI-editor and desktop-agent workflows. Its README describes a two-part architecture: a React-based MCP Inspector Client and a Node.js MCP Proxy that bridges the browser UI to MCP servers.

The official MCP documentation treats the Inspector as a developer tool and links it from the developer-tools section of the docs site. Later README updates added explicit proxy authentication and security guidance after the project became a common way to run local MCP processes from a browser-driven workflow.

Adoption history

The Inspector is distributed primarily as an npm-executed tool, with the README documenting `npx @modelcontextprotocol/inspector` as the quick-start path and a container image as an alternative. Homebrew packaging gives macOS and Linux package-manager users a pinned `mcp-inspector` executable for the same official tool.

GitHub repository metadata showed more than ten thousand stars and more than a thousand forks by July 2026, which is unusually high for a protocol-specific debugging utility and reflects its role as the default manual test harness for MCP server authors.

How it is used

Typical use is to launch the Inspector with no arguments for UI mode, or to pass an MCP server command such as `node build/index.js` so the tool can start the server and connect through its proxy. The README documents default local ports 6274 for the client UI and 6277 for the proxy server.

The Inspector can export server entries or complete MCP server files for use in clients such as Cursor, Claude Code, or the Inspector CLI. Its docs also warn that the proxy can spawn local processes and should not be exposed to untrusted networks.

Why package nerds care

For package users, MCP Inspector is the rough equivalent of a protocol REPL plus GUI debugger: it lets a packaged MCP server be smoke-tested without building a bespoke client. That made it a natural Homebrew formula despite the upstream Node-centric install path.

Its significance is also operational. Because MCP servers often ship as tiny CLI packages launched by larger clients, a standalone inspector gives maintainers a reproducible way to debug transport, environment-variable, and authentication issues outside any one host application.

Timeline

• 2024: GitHub repository created under modelcontextprotocol/inspector.
• 2025: Inspector documented as the official MCP visual testing and debugging tool.
• 2025: Proxy authentication and security guidance documented in the README.
• 2026: Repository metadata showed broad adoption with thousands of stars and forks.

Related projects

• modelcontextprotocol/registry provides the official MCP server registry and publisher CLI.
• sparfenyuk/mcp-proxy and geelen/mcp-remote solve adjacent MCP transport-bridging problems.
• MCP SDKs and example servers provide the protocol implementations commonly tested with the Inspector.

Sources

• https://api.github.com/repos/modelcontextprotocol/inspector
• https://github.com/modelcontextprotocol/inspector
• https://github.com/modelcontextprotocol/inspector#readme
• https://modelcontextprotocol.io/docs/tools/inspector
• source_facts.description
• source_facts.package-manager-url