servers/src/everything
Repository files (latest commit first)
Filename Latest commit message Latest commit date
shaun smith 3a32d1024b
Add URL Elicitation cases (#3334)
* url elicitation

* single tool for normal and error path

* Address review feedback on URL elicitation tool

- Remove src/everything/pnpm-lock.yaml (monorepo uses npm workspaces)
- Drop redundant TriggerUrlElicitationSchema.parse(args) in the handler;
  destructure directly from args like the other tools, since the SDK
  validates against the registered schema before invoking the handler
- Add explicit accept/decline/cancel messaging in the request path,
  mirroring trigger-elicitation-request.ts
- Clarify the registerTool count comment in registrations.test.ts
  (task-based tools register via registerToolTask, counted separately)
- Add tests covering the no-url / undefined-capability registration
  guards, the randomUUID() elicitationId fallback, and the
  decline/cancel response paths (100% coverage of the tool)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* Add tool annotations to trigger-url-elicitation

Match the annotations block on sibling elicitation tools and the
CLAUDE.md guidance. Uses openWorldHint: true since the tool drives an
external browser flow.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: cliffhall <cliff@futurescale.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-03 18:10:07 -07:00
..
__tests__ Add URL Elicitation cases (#3334) 2026-06-03 18:10:07 -07:00
docs Add URL Elicitation cases (#3334) 2026-06-03 18:10:07 -07:00
prompts [WIP] Refactor everything server to be more modular and use recommended APIs. 2025-12-09 17:47:38 -05:00
resources fix(everything): allow re-registration of session resources 2026-01-26 09:10:58 -05:00
server Fix #3234 - 2026-01-23 13:35:32 -05:00
tools Add URL Elicitation cases (#3334) 2026-06-03 18:10:07 -07:00
transports Fix #3234 - 2026-01-23 13:26:02 -05:00
.prettierignore [WIP] Refactor everything server to be more modular and use recommended APIs. 2025-12-05 13:26:08 -05:00
AGENTS.md docs: add root CLAUDE.md and fix AGENTS.md typo 2026-03-27 14:37:53 +01:00
Dockerfile fix warnings: - FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 1) 2025-01-02 12:56:40 -03:00
index.ts [WIP] Refactor everything server to be more modular and use recommended APIs. 2025-12-12 20:12:18 -05:00
package.json upgrade everything-server to zod v4, latest MCP sdk 2026-05-11 14:29:58 +03:00
README.md Merge pull request #3659 from ShionEria/fix/issue-3460-windows-npx-docs 2026-04-17 18:59:54 -04:00
tsconfig.json [WIP] Refactor everything server to be more modular and use recommended APIs. 2025-12-05 13:26:08 -05:00
vitest.config.ts Add Vitest tests for Everything Server 2026-02-06 23:20:05 +02:00

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.

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