Federated MCP

Why it's ranked here

The project has useful building blocks and unusually broad deployment ambitions, but the supplied implementation does not consistently match its documentation. The core server uses a simple message envelope rather than its defined JSON-RPC types, while the Deno entry point serves a fixed response and exposes most management through an interactive terminal.

What's good

The code separates protocol types, server behavior, authentication, edge handlers, and provider deployment concerns. It includes explicit capability descriptions, structured error responses, configurable logging, JWT signing and verification, HTTP and WebSocket entry points, Cloudflare Durable Object session handling, and a detailed protocol schema covering tools, resources, prompts, cancellation, and completion.

Tradeoffs

Several advertised features are clearer in the README than in the supplied code. The core message handler only recognizes information and capability requests. The Cloudflare worker uses its own message types, and task processing stores input before returning a generic success result. The package manifest supplies one dependency but no scripts, package identity, or documented Node entry point. The Deno launch command requests broad permissions.

How to use it well

Use it as source material for a TypeScript prototype spanning Deno, edge functions, HTTP, and WebSockets. It best suits engineers prepared to reconcile its protocol layers and complete provider integration themselves. Treat the schema and adapters as a starting kit, not a finished federation platform or a general model orchestration product.

Observed

License

MIT License

Primary language

TypeScript

Package surface

package.json declares @modelcontextprotocol/sdk directly from the TypeScript SDK GitHub repository

Interfaces

Interactive Deno terminal, HTTP endpoints, WebSockets, edge HTTP routes, and reusable TypeScript server classes

Runtime and platform support

Deno server code and Cloudflare Workers code are present; the README also states Node.js, Supabase, and Fly.io support

Protocol definitions

JSON-RPC 2.0 TypeScript types and a draft-07 MCP JSON Schema are included

Test configuration

A ts-jest configuration expects tests under a tests root and matches specification or test naming patterns