(01)The official TypeScript SDK is no longer a beta. v2.0.0 is the stable release line for the 2026-07-28 spec, published as split packages: @modelcontextprotocol/core for schemas and protocol constants, @modelcontextprotocol/server, @modelcontextprotocol/client, and @modelcontextprotocol/express. The old @modelcontextprotocol/sdk package remains the v1 maintenance line, so teams watching only that package will think MCP v2 has not landed. Use the v2 packages for new stateless servers; use the codemod and migration notes when upgrading v1 imports.
Stable v2 server/client development, v1 package-name migrationFree / Open SourceAI-Native
(02)Official Python implementation. mcp 2.0.0 shipped as the stable v2 release on July 28, 2026 and supports the 2026-07-28 MCP revision while serving earlier revisions from the same server. pip install mcp now installs 2.x; v1.x moved to maintenance for critical fixes and security patches. Best fit for Python data tools, local CLIs, and FastMCP-style servers where decorators and Pydantic models keep tool schemas close to business logic.
Stable Python v2 servers, data tools, decorator-based toolsFree / Open SourceAI-Native
(03)First-class MCP deployment on Vercel Functions and Fluid Compute. Wraps your MCP server in a Next.js route or Node function — no persistent process to operate. Streamable HTTP and MCP v2 stateless requests align with ordinary load balancing; OAuth 2.1-style protection keeps remote servers usable by real clients. Prefer Fluid Compute over Edge-only functions for compatibility unless you have a measured edge constraint.
Serverless deployment, Next.js integration, OAuth 2.1Free tier; paid plans – see Vercel pricingAI-Native
(04)High-level Python framework built on top of the official Python SDK. Reduces MCP server boilerplate to near-zero — expose a function as an MCP tool in 3 lines. Handles schema generation from Python type annotations automatically. Best choice for rapid Python MCP prototypes and data-science-adjacent servers. Community-maintained, widely adopted.
Rapid prototyping, minimal boilerplate, type-driven schemasFree / Open SourceAI-Native
(05)Official visual debugging tool for MCP servers. Connects to any MCP server (stdio or HTTP) and provides a web UI to browse available tools, execute them with custom inputs, and inspect raw JSON-RPC messages. Equivalent to Postman for MCP — essential for development and validation. Run locally with `npx @modelcontextprotocol/inspector`.
Debugging, tool exploration, JSON-RPC inspectionFree / Open SourceAI-Native
(06)Not MCP-specific, but still the default companion for defining TypeScript tool input schemas. MCP v2 supports Standard Schema-compatible libraries, including Zod v4, ArkType, Valibot via converter, or raw JSON Schema, but the rule is unchanged: every production MCP server needs runtime validation before a tool touches shell commands, SQL, CRM data, or customer files.
TypeScript schema validation, JSON Schema generationFree / Open Source
(07)Bridges the gap between stdio-only MCP clients (Claude Desktop config) and HTTP-hosted MCP servers. Acts as a local proxy that forwards stdio calls to a remote Streamable HTTP or SSE endpoint. Essential pattern for connecting Claude Desktop or Cursor to production cloud-hosted MCP servers without running them locally.
Transport bridging, stdio-to-HTTP proxyFree / Open SourceAI-Native
(08)One of the major MCP server registries, growing strongly through 2026. Discover, install, and publish MCP servers; hosted remote server infrastructure lets teams run third-party servers without local process management. Compare with Glama.ai (a broad, curated catalog) and the Official MCP Registry (registry.modelcontextprotocol.io) for vetted first-party servers. Treat registry discovery as a starting point, not a trust boundary: audit source, auth, scopes, and egress before production use.
Server discovery, registry, marketplaceFree to browse; premium servers varyAI-Native
