Everything MCP server
Last verified: 2026-09
Reference server that exercises the whole MCP protocol.
Official reference Developer tools No API key Claude Desktop, Cursor, Windsurf, Claude Code, VS Code
What it does
Reference server that exercises prompts, resources, tools, and sampling. For people writing an MCP host or debugging a client. Not a daily-driver tool.
It sits in Developer tools: Split this category in two.
Good for
- Verify a new MCP host actually implements resources, prompts, and tools.
- Reproduce a client bug with a known-good server.
- Teach yourself the protocol without pointing at a real API.
- Remove it from the default config after the test.
Tools
- echo / add / and protocol demos — Used to test the client, not to do work.
Config (Claude Desktop / Cursor / Windsurf)
Paste the JSON below. Same mcpServers shape. Replace placeholder paths and secrets.
Windows paths look like C:\\Users\\you\\project, not /path/to.
Host-side steps →
Claude Desktop
| OS | Config file |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json
(usually C:\Users\<you>\AppData\Roaming\Claude\) |
| Linux | ~/.config/Claude/claude_desktop_config.json |
Cursor
| Scope | macOS / Linux | Windows |
|---|---|---|
| This project | .cursor/mcp.json in the repo root | |
| This user | ~/.cursor/mcp.json |
%USERPROFILE%\.cursor\mcp.json |
Windsurf
| OS | Config file |
|---|---|
| macOS / Linux | ~/.codeium/windsurf/mcp_config.json |
| Windows | %USERPROFILE%\.codeium\windsurf\mcp_config.json |
{
"mcpServers": {
"everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Windsurf remote MCP: use serverUrl instead of url if the block below is HTTP.
One-liner: npx -y @modelcontextprotocol/server-everything
Secrets it wants: none
How to get started
- Install only in a test profile.
- Walk the client's tool list and resource list.
- Remove it from the default config when you are done.
Access risk
Low, but do not leave demo tools in a config that also has GitHub write tokens.
When to skip it
Skip it unless you are building or debugging an MCP client.
Instead: Sequential Thinking.
Vs alternatives
| Server | Official? | Needs a secret? | Best for |
|---|---|---|---|
| Everything | Yes | No | Reference server that exercises the whole MCP protocol. |
| Sequential Thinking | Yes | No | A scratchpad that forces the model to break work into steps. |
More in Developer tools
FAQ
Should this be in my daily config?
No. It is a protocol gym. It does not help you ship.
Does it need secrets?
No.
Why is it in Developer tools?
Because that is where people look when a host misbehaves.
Is it safe?
It is a test server. Still, do not treat random tool output as production data.