---
title: "Everything MCP Server for ToolPiper · ModelPiper"
description: "Reference test server exercising every MCP feature. Everything is not a useful server. It is a reference test fixture that exercises every part of the MCP protocol so client developers can verify their implementation. Pr"
canonical: "https://modelpiper.com/mcp-tools/everything"
---

# Everything MCP Server for ToolPiper · ModelPiper

> Reference test server exercising every MCP feature. Everything is not a useful server. It is a reference test fixture that exercises every part of the MCP protocol so client developers can verify their implementation. Pr

E

# Everything MCP Server

✓ verified

Reference test server exercising every MCP feature.

Install Everything in ToolPiper

Don't have ToolPiper? We'll take you to the download.

[Open repository →](https://github.com/modelcontextprotocol/servers/tree/main/src/everything)

Publisher

[Anthropic](https://github.com/modelcontextprotocol/servers)

License

MIT

Transport

Local subprocess

Tools

5

## What this server does

Everything is not a useful server. It is a reference test fixture that exercises every part of the MCP protocol so client developers can verify their implementation. Prompts, tools, resources, sampling, progress reporting, cancellation, all wired up in one binary. Tools include trivial demos (\`echo\`, \`add\`) and protocol-exercising ones. \`long\_running\_operation\` emits progress events you can use to verify your client's progress UI and cancellation path. \`sample\_llm\` triggers server-initiated sampling, which is one of the harder MCP features to test. Resources, prompts, and roots are also registered. Three transports ship in the same package: stdio (default), the deprecated HTTP+SSE, and the current Streamable HTTP. After \`npm install -g @modelcontextprotocol/server-everything\`, run \`npx @modelcontextprotocol/server-everything <transport>\` to pick. The full list of registered primitives lives in \`docs/features.md\` inside the upstream repo. When to reach for it: writing an MCP client, debugging why a feature does not work in your host, or learning what the protocol can actually do beyond simple tool calls. When not to: any real workflow. The tools are deliberately useless, and pointing a model at it will burn tokens calling \`add(1, 2)\` and \`echo\` for no benefit.

## Tools included

-   echo
    
    Echo back the input message.
    
-   get\_sum
    
    Add two numbers and return the sum.
    
-   get\_tiny\_image
    
    Return a small base64-encoded image resource.
    
-   trigger\_long\_running\_operation
    
    Demonstrates progress reporting and cancellation.
    
-   trigger\_sampling\_request
    
    Demonstrates server-initiated sampling.
    

The authoritative list comes from the server's tools/list at runtime. This catalog entry may lag the upstream until the next ToolPiper release.

## Install in ToolPiper

ToolPiper handles the JSON configuration. Click Install, fill in any required tokens, and the server is ready in your chat.

Install Everything in ToolPiper

Don't have ToolPiper? We'll take you to the download.

## Install in another client

Install in another MCP client (Claude Desktop, Cursor, Continue, Cline)

Claude Desktop Cursor Continue Cline

Add this to ~/Library/Application Support/Claude/claude\_desktop\_config.json.

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

Copy

## Example prompts

-   "Echo back the message 'hello world'."
    
    Copy
-   "Add 17 and 25."
    
    Copy
-   "Start the long-running operation and report progress as it advances."
    
    Copy
-   "Use the sampling primitive to ask yourself what 2 plus 2 is."
    
    Copy

## Security notes

No credentials, no network calls, no file access. Safe to run anywhere. The only practical risk is billing noise: \`long\_running\_operation\` exists specifically to emit progress events, and \`sample\_llm\` calls back into the host's LLM. If you wire this server into an MCP host that bills per token, a curious model can rack up calls by playing with the sandbox. Not a security risk, just a budget one. Run it locally for client development and disconnect when you are done.

## Related tools

-   [
    
    G
    
    ### GitHub
    
    ✓ verified
    
    Create issues, manage pull requests, and search repositories from your AI assistant.
    
    Developer ToolsLocal subprocess5 tools
    
    
    
    
    
    ](/mcp-tools/github)
-   [
    
    G
    
    ### GitHub (Remote)
    
    ✓ verified MAX
    
    OAuth-protected GitHub MCP. Manage repos, issues, and pull requests with no token to copy.
    
    Developer ToolsRemote HTTP5 tools
    
    
    
    
    
    ](/mcp-tools/github-remote)
-   [
    
    G
    
    ### Git
    
    ✓ verified
    
    Read, search, and manipulate Git repositories on disk.
    
    Developer ToolsLocal subprocess5 tools
    
    
    
    
    
    ](/mcp-tools/git)
-   [
    
    G
    
    ### GitLab
    
    ✓ verified
    
    Manage GitLab projects, issues, and merge requests.
    
    Developer ToolsLocal subprocess5 tools
    
    
    
    
    
    ](/mcp-tools/gitlab)

[← Back to all MCP tools](/mcp-tools)