Log inSubmit server
Server Everything logo

Server Everything

by modelcontextprotocol

Protocol test server covering tools, resources, prompts, notifications, transports, and newer MCP behaviors.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Server Everything

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "modelcontextprotocol-server-everything": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-everything"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

modelcontextprotocol/server-everything exercises MCP features through a collection of diagnostic tools, resources, prompts, and protocol interactions. It supports stdio and Streamable HTTP from one process, serving both 2026-07-28 and 2025-era clients with era-specific behavior. Use it to develop or validate MCP client implementations rather than as a production data or business integration. Its tools cover structured outputs, resource references, notifications, logging, progress reporting, and other protocol mechanics.

Use cases

  • Test an MCP client's tool and resource handling
  • Validate structured content and output-schema support
  • Exercise progress updates and long-running operations
  • Inspect protocol-version and transport behavior
  • Debug MCP configuration through environment inspection

Key features

  • Supports stdio and Streamable HTTP transports
  • Serves 2026-07-28 and 2025-era protocol clients
  • Demonstrates tools, resources, prompts, and sampling
  • Exercises structured content, annotations, and resource links
  • Triggers progress, logging, and resource-change notifications
  • Includes gzip resource and tiny image examples

Tools16

What Server Everything lets your agent do. Expand a tool for its parameters.

Verified live~1.6k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

31/31 checks healthy over the last 79d

What it can do

From the 16 tools this server returned when we ran it; 16 declare their own safety hints.

Makes network requests · 4Read-only tools · 16
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceSigned build
Package age702 days
Maintainers6

Observed 2026-10-23 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · @modelcontextprotocol/server-everything (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars91kStargazers on the source repository.
npm downloads257kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Tools exposed16Callable tools this server registers over MCP.
Directory activity11 viewsConfig copies, upvotes, and views on AllMCPs.

How Server Everything works

What modelcontextprotocol/server-everything does

modelcontextprotocol/server-everything is a reference and test server for MCP client builders. Rather than connecting an agent to a business system, it exposes protocol behaviors that clients need to handle, including tools, resources, prompts, sampling, elicitation, roots, notifications, structured content, and images.

The server includes simple callable operations such as echoing text and adding two numbers, alongside cases designed to test client implementations. These cases cover annotations, output schemas, resource links, resource references, environment inspection, compressed files, long-running work, progress updates, and list or resource-change notifications.

How it works

One process serves both protocol eras. A 2026-07-28 client uses discovery, sends its identity and capabilities with each request, and connects without a session. A 2025-era client uses the traditional initialize handshake and session model. The server adapts features such as subscriptions, logging, sampling, elicitation, and roots through the relevant protocol behavior.

Streamable HTTP is available at /mcp when running the HTTP transport. The server also supports stdio, and it can start an HTTP+SSE endpoint for 2025-era clients. Streamable HTTP is the preferred HTTP option; HTTP+SSE is deprecated.

Setup and configuration

Running through npx or from source requires Node.js 24 or later. The default installed-package command uses stdio:

Terminal
npx @modelcontextprotocol/server-everything

The package can also be started explicitly with stdio, streamableHttp, or sse. To run Streamable HTTP from the source tree, install dependencies under src/everything and start the Streamable HTTP script. The endpoint uses port 3001 by default; the PORT environment variable overrides it.

Claude Desktop can launch the package with npx -y @modelcontextprotocol/server-everything. Windows configurations use cmd /c before the npx command. VS Code supports NPX and Docker installation configurations, either through its user MCP configuration or a workspace .vscode/mcp.json file.

Tools and capabilities

Available tools include:

  • echo for returning an input string and get-sum for basic arithmetic.
  • get-annotated-message, get-structured-content, and get-header-params for metadata, schemas, headers, and structured tool results.
  • get-resource-links, get-resource-reference, and get-tiny-image for resource-oriented responses.
  • get-env for returning environment variables during configuration debugging.
  • gzip-file-as-resource for producing compressed resource data or a downloadable resource link.
  • trigger-long-running-operation for progress updates.
  • trigger-list-changed and trigger-resource-update for change notifications.
  • trigger-log-messages, toggle-simulated-logging, and toggle-subscriber-updates for notification and logging tests.

The server also demonstrates cache hints, multi-round-trip requests, request state, per-request log levels, the tasks extension, and JSON Schema 2020-12 tool schemas for the newer protocol era.

Limitations and notes

This server is intended for MCP client development and protocol testing, not for delivering a practical external service. get-env returns all environment variables, so use it only in an environment where that output is appropriate. Logging and resource subscription tools tied to the 2025-era behavior are deprecated for 2026-07-28 clients, which use per-request log levels and subscription streams instead. Browser HTTP requests are accepted only from localhost origins; non-browser requests without an Origin header are unaffected.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Server Everything

modelcontextprotocol/server-everything is an MCP server that connects MCP clients to a broad protocol test surface, with tools for echoing, arithmetic, environment inspection, structured content, resources, images, gzip files, notifications, logging, and long-running operations. It is intended for building and testing MCP clients rather than production workflows.

Install it with `npm install -g @modelcontextprotocol/server-everything@latest`, or run it directly with `npx @modelcontextprotocol/server-everything`. Node.js 24 or later is required when running through `npx` or from source.

Run `npx @modelcontextprotocol/server-everything streamableHttp`, or start the Streamable HTTP script from the source tree. The endpoint is `http://localhost:3001/mcp` by default, and `PORT` can change the port.

Yes, VS Code supports the server through an NPX or Docker MCP configuration. You can add it to the user MCP configuration or to a workspace `.vscode/mcp.json` file.

Related MCP servers

All in Other Tools and Integrations All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewServer Everything AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/modelcontextprotocol-server-everything?style=directory)](https://allmcps.com/mcp/modelcontextprotocol-server-everything)
HTML Embed
<a href="https://allmcps.com/mcp/modelcontextprotocol-server-everything"><img src="https://allmcps.com/api/badge/modelcontextprotocol-server-everything?style=directory" alt="Server Everything on AllMCPs" /></a>