What Is Everything MCP Server?

Everything MCP Server is a reference implementation maintained by the Model Context Protocol team that exposes all core MCP primitives — resources, prompts, and tools — in a single server. It exists specifically for testing MCP clients and exploring how the protocol behaves across its full feature surface.

Quick Facts

FieldValue
Package@modelcontextprotocol/server-everything
Installnpx @modelcontextprotocol/server-everything
Compatible withClaude Code, Claude Desktop, any MCP client
Statusactive
GitHubhttps://github.com/modelcontextprotocol/servers/tree/main/src/everything

What You Can Do With It

  • MCP client testing: Verify that your client correctly handles resources, prompts, and tool calls by running them against a known-good implementation.
  • Protocol exploration: Inspect how each primitive type is structured and returned without needing a production server or external API.
  • Developer reference: Use it as a canonical example when building your own MCP server to confirm expected request/response shapes.

How to Set It Up

Run the server directly without installation:

npx @modelcontextprotocol/server-everything
To register it with Claude Code, add the following to your `.claude/mcp.json` file:

```json
{
  "mcpServers": {
    "everything": {
      "command": "npx",
      "args": ["@modelcontextprotocol/server-everything"]
    }
  }
}

For Claude Desktop, add the same block to claude_desktop_config.json, typically located at:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "everything": {
      "command": "npx",
      "args": ["@modelcontextprotocol/server-everything"]
    }
  }
}

Restart Claude Desktop after editing the config. No API keys or environment variables are required.

Works Best With

Everything MCP Server is designed to be client-agnostic and is explicitly compatible with Claude Code, Claude Desktop, and any other MCP-compliant client. It is most useful in environments where you need predictable, schema-valid responses — making it the default choice when debugging a new client integration or validating client-side parsing logic. If you are writing an MCP client from scratch, this server gives you a stable target to test against before connecting to production services.

Known Limitations

  • No real-world data: All resources, prompts, and tools are synthetic. The server demonstrates the protocol structure but does not connect to external APIs, filesystems, or databases.
  • Not for production use: This is a testing artifact, not a server you would expose to end users or build application logic on top of.
  • npx cold starts: Running via npx incurs a small startup delay on first run due to package resolution. If startup time matters in your test suite, install the package globally (npm install -g @modelcontextprotocol/server-everything) and invoke it directly.
  • No authentication layer: The server accepts all connections without auth. Do not expose it on a public network interface.
  • Feature parity tracks the spec: Behavior may change as the MCP specification evolves. Pin to a specific package version if you need stable test fixtures across time.

Community Resources

This article contains affiliate links. We may earn a commission at no extra cost to you. Learn more.

Share: X