echo
Echoes back the input string
LABSCO SUMMARY
Not a server you use for work — a fixture for finding out which parts of MCP your client actually handles.
Its own README says as much: it is not meant to be useful, it is meant to exercise the protocol. The value is in the awkward corners — progress notifications, subscriptions, sampling, elicitation, tasks — because those are the features a client can appear to support until something sends them for real. It speaks stdio, SSE and Streamable HTTP from one package, so the transport layer can be tested from the same fixture.
What it is
A reference server for people building MCP clients. It implements tools, prompts, resources, sampling, elicitation, progress and tasks so a client can be exercised against every part of the protocol.
What you get
- Plain request/response tools to check the basics — echo, get-sum, get-tiny-image
- Structured output with an output schema attached, so you can test client-side validation (get-structured-content)
- Resource behaviour: links returned in bulk, a single resource reference, and a file compressed into a session resource (get-resource-links, get-resource-reference, gzip-file-as-resource)
- Long operations with progress notifications, via trigger-long-running-operation
- A task-based flow with staged status updates and an optional elicitation for clarification, via simulate-research-query
- Toggles for the noisy parts — simulated logging at random levels, and resource-update notifications to subscribers
- Annotated content and an environment dump, for checking how your client renders metadata and for debugging a server's configuration
Requirements
Nothing to authorize. Published on npm as @modelcontextprotocol/server-everything and run through npx; on Windows launch it via cmd /c. The same package serves stdio, SSE and Streamable HTTP — pass stdio, sse or streamableHttp on the command line.
Setup effort
One command — npx -y @modelcontextprotocol/server-everything
USE CASES
01
Checking a new client against the protocol before real servers are involved
Start with the trivial calls, then work up to structured output and resource references, so a failure points at your client rather than at someone's API.
02
Seeing whether your UI survives a long call
Trigger an operation that runs over a set duration and reports progress, and watch what the interface does between the first and last update.
03
Testing resource handling without hosting resources
Pull back a batch of resource links, then a single concrete resource, then a file compressed into a session-scoped one.
04
Exercising subscriptions and log levels on demand
Switch simulated logging and subscriber updates on, watch the client handle the stream, then switch them off again.
05
Debugging why a server sees the wrong configuration
Dump the environment the server process actually received, instead of the one you think you set.
13 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get-annotated-message
Demonstrates how annotations can be used to provide metadata about content.
get-env
Returns all environment variables, helpful for debugging MCP server configuration
get-resource-links
Returns up to ten resource links that reference different types of resources
get-resource-reference
Returns a resource reference that can be used by MCP clients
get-structured-content
Returns structured content along with an output schema for client data validation
get-sum
Returns the sum of two numbers
get-tiny-image
Returns a tiny MCP logo image.
gzip-file-as-resource
Compresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request during the current session.
simulate-research-query
Simulates a deep research operation that gathers, analyzes, and synthesizes information. Demonstrates MCP task-based operations with progress through multiple stages. If 'ambiguous' is true and client supports elicitation, sends an elicitation request for clarification.
toggle-simulated-logging
Toggles simulated, random-leveled logging on or off.
toggle-subscriber-updates
Toggles simulated resource subscription updates on or off.
trigger-long-running-operation
Demonstrates a long running operation with progress updates.
BEFORE YOU INSTALL
What to know first
Tools you get
13 tools when we connected. Six more tools, for a documented total of 19, register only when your client supports roots, elicitation, sampling or tasks, so the count you see depends on your client.
Requires
npx on PATH
Where it runs
All 4 documented setups run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 13 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @modelcontextprotocol/server-everythingMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}Claude Desktop — Windows
CLAUDE DESKTOP — WINDOWS · JSON
{
"mcpServers": {
"everything": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}VS Code — Windows
VS CODE — WINDOWS · JSON
{
"servers": {
"everything": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
