Files
Marcelo Trylesinski b42d5cd5fe Extract protocol types into a standalone mcp-types package
Convert the repository into a uv workspace mirroring pydantic/httpx2. The
root pyproject becomes a pure coordinator (package = false) and the two
distributable packages live nested under src/<pkg>/<pkg>/ each with their
own pyproject:

- src/mcp/mcp/ -> mcp
- src/mcp-types/mcp_types/ -> mcp-types (import mcp_types)

The protocol types (_types.py, jsonrpc.py) move into mcp_types, which only
depends on pydantic and typing-extensions. mcp depends on mcp-types via
uv-dynamic-versioning, so installing mcp still pulls the types in. The
mcp.types module path is removed; all imports now use mcp_types. The
curated re-exports on the top-level mcp package are unchanged.
2026-06-02 18:06:12 +02:00
..

MCP Everything Server

A comprehensive MCP server implementing all protocol features for conformance testing.

Overview

The Everything Server is a reference implementation that demonstrates all features of the Model Context Protocol (MCP). It is designed to be used with the MCP Conformance Test Framework to validate MCP client and server implementations.

Installation

From the python-sdk root directory:

uv sync --frozen

Usage

Running the Server

Start the server with default settings (port 3001):

uv run -m mcp_everything_server

Or with custom options:

uv run -m mcp_everything_server --port 3001 --log-level DEBUG

The server will be available at: http://localhost:3001/mcp

Command-Line Options

  • --port - Port to listen on (default: 3001)
  • --log-level - Logging level: DEBUG, INFO, WARNING, ERROR, CRITICAL (default: INFO)

Running Conformance Tests

See the MCP Conformance Test Framework for instructions on running conformance tests against this server.