inspector vs everything
Side-by-side comparison to help you pick between these two MCP servers.
inspector by mcp-use | everything by modelcontextprotocol | |
|---|---|---|
| Stars | ★ 13 | ★ 85,748 |
| 30d uses | — | — |
| Score | 42 | 77 |
| Official | — | ✓ |
| Categories | Developer ToolsAI / LLM Tools | Developer ToolsAI / LLM ToolsOther |
| Language | TypeScript | TypeScript |
| Last commit | this month | this month |
inspector · Summary
A modern MCP Inspector for testing and debugging remote MCP servers with support for Apps SDK and browser-based UI.
everything · Summary
Official MCP test server exercising all protocol features for client builders.
inspector · Use cases
- Developers testing MCP server functionality before integration
- Debugging tools and resources during MCP server development
- Visualizing and interacting with multiple MCP servers simultaneously
everything · Use cases
- Testing MCP client implementations against all protocol features
- Learning MCP protocol capabilities through a reference server
- Validating client compatibility with different transport methods
inspector · Install
Install and run the MCP Inspector:
# Run locally
npx @mcp-use/inspectorFor Claude Desktop, add this to your claude_desktop_config.json:
{
"mcpServers": {
"inspector": {
"command": "npx",
"args": ["@mcp-use/inspector"]
}
}
}Or use the online version: https://inspector.mcp-use.com/inspector
everything · Install
NPX (recommended)
{
"mcpServers": {
"everything": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-everything"]
}
}
}On Windows, use cmd /c:
{
"mcpServers": {
"everything": {
"command": "cmd",
"args": ["/c", "npx", "-y", "@modelcontextprotocol/server-everything"]
}
}
}Docker
{
"mcpServers": {
"everything": {
"command": "docker",
"args": ["run", "-i", "--rm", "mcp/everything"]
}
}
}Global install
npm install -g @modelcontextprotocol/server-everything@latest
npx @modelcontextprotocol/server-everything