Skip to main content
Glama
mcp-everything

mcp-everything

by mohammad-k13

Everything MCP Server

Architecture | Project Structure | Startup Process | Server Features | Extension Points | How It Works

This MCP server attempts to exercise all the features of the MCP protocol. It is not intended to be a useful server, but rather a test server for builders of MCP clients. It implements prompts, tools, resources, sampling, and more to showcase MCP capabilities.

Tools, Resources, Prompts, and Other Features

A complete list of the registered MCP primitives and other protocol features demonstrated can be found in the Server Features document.

Related MCP server: mcp-test-server

Usage with Claude Desktop (uses stdio Transport)

Add to your claude_desktop_config.json:

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

On Windows, use cmd /c to launch npx:

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

Usage with VS Code

For quick installation, use one of the one-click install buttons below...

Install with NPX in VS Code Install with NPX in VS Code Insiders

Install with Docker in VS Code Install with Docker in VS Code Insiders

For manual installation, you can configure the MCP server using one of these methods:

Method 1: User Configuration (Recommended) Add the configuration to your user-level MCP configuration file. Open the Command Palette (Ctrl + Shift + P) and run MCP: Open User Configuration. This will open your user mcp.json file where you can add the server configuration.

Method 2: Workspace Configuration Alternatively, you can add the configuration to a file called .vscode/mcp.json in your workspace. This will allow you to share the configuration with others.

For more details about MCP configuration in VS Code, see the official VS Code MCP documentation.

NPX

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

On Windows, use:

{
  "servers": {
    "everything": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-everything"]
    }
  }
}

Running from source with HTTP+SSE Transport (deprecated as of 2025-03-26)

cd src/everything
npm install
npm run start:sse

Run from source with Streamable HTTP Transport

cd src/everything
npm install
npm run start:streamableHttp

Running as an installed package

Install

npm install -g @modelcontextprotocol/server-everything@latest

Run the default (stdio) server

npx @modelcontextprotocol/server-everything

Or specify stdio explicitly

npx @modelcontextprotocol/server-everything stdio

Run the SSE server

npx @modelcontextprotocol/server-everything sse

Run the streamable HTTP server

npx @modelcontextprotocol/server-everything streamableHttp

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

13 tools
echoEcho ToolA
Read-onlyIdempotent

Echoes back the input string

Inputs: message (required).

get-annotated-messageGet Annotated Message ToolC
Read-onlyIdempotent

Demonstrates how annotations can be used to provide metadata about content.

Inputs: messageType (required), includeImage.

get-envPrint Environment ToolA
Read-onlyIdempotent

Returns all environment variables, helpful for debugging MCP server configuration

Inputs: no named parameters.

get-resource-referenceGet Resource Reference ToolC
Read-onlyIdempotent

Returns a resource reference that can be used by MCP clients

Inputs: resourceId, resourceType.

get-structured-contentGet Structured Content ToolB
Read-onlyIdempotent

Returns structured content along with an output schema for client data validation

Inputs: location (required). Returns: humidity, conditions, temperature

get-sumGet Sum ToolA
Read-onlyIdempotent

Returns the sum of two numbers

Inputs: a (required), b (required).

get-tiny-imageGet Tiny Image ToolA
Read-onlyIdempotent

Returns a tiny MCP logo image.

Inputs: no named parameters.

gzip-file-as-resourceGZip File as Resource ToolA
Idempotent

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.

Inputs: data, name, outputType.

simulate-research-querySimulate Research QueryA

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.

Inputs: topic (required), ambiguous.

toggle-simulated-loggingToggle Simulated LoggingA

Toggles simulated, random-leveled logging on or off.

Inputs: no named parameters.

toggle-subscriber-updatesToggle Subscriber UpdatesA

Toggles simulated resource subscription updates on or off.

Inputs: no named parameters.

trigger-long-running-operationTrigger Long Running Operation ToolB
Read-onlyIdempotent

Demonstrates a long running operation with progress updates.

Inputs: steps, duration.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 13 tools

    Disambiguation3/5

    Most tools target distinct MCP demos, but several overlap: get-resource-links and get-resource-reference both concern resources, get-annotated-message and get-structured-content both return content metadata, and trigger-long-running-operation and simulate-research-query both demonstrate long-running progress. Descriptions help, but boundaries are not always crisp.

    Naming Consistency5/5

    All tool names use kebab-case and are almost entirely verb-first or get_-prefixed. Minor variations like echo and gzip-file-as-resource still fit the overall verb-led convention.

    Tool Count5/5

    At 13 tools, the set is well-scoped for a feature-demonstration server. Each tool appears to demonstrate a specific MCP capability, so the count does not feel bloated or thin.

    Completeness3/5

    The implied domain is demonstrating MCP features, but the surface leaves notable gaps such as prompts, sampling, and full resource lifecycle operations. It covers many individual demos without providing complete coverage of the protocol area it claims to represent.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A test server implementing all features of the MCP protocol, including prompts, tools, resources, and sampling, designed for testing MCP clients rather than practical applications.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive testing server for validating MCP scanner tools and implementations, providing diverse tools, resources, and prompts that exercise various aspects of the Model Context Protocol specification.
      16 npm
      MIT