mcporter and frontmcp
These are complements: mcporter provides a lightweight TypeScript wrapper to *call* existing MCPs as if they were simple APIs, while FrontMCP is a framework for *building* MCPs with structured TypeScript-first development, so you'd use FrontMCP to create an MCP and mcporter to integrate it into applications.
About mcporter
steipete/mcporter
Call MCPs via TypeScript, masquerading as simple TypeScript API. Or package them as cli.
Supports zero-config MCP discovery across Cursor, Claude Desktop, Codex, and Windsurf with automatic transport pooling and environment variable expansion. Generates typed TypeScript clients (`.d.ts` or runnable wrappers), single-command CLIs with optional bundling, and provides ergonomic camelCase APIs with built-in OAuth caching, JSON-schema validation, and content helpers (`.text()`, `.markdown()`, `.json()`, `.images()`). Handles stdio, HTTP, and SSE transports uniformly with ad-hoc endpoint support and auto-detected OAuth promotion for hosted MCPs.
About frontmcp
agentfront/frontmcp
TypeScript-first framework for the Model Context Protocol (MCP). You write clean, typed code; FrontMCP handles the protocol, transport, DI, session/auth, and execution flow.
Provides decorator-based capability organization (@App, @Tool, @Resource, @Prompt, @Agent), Zod-validated typed tool schemas, and stateful/stateless session modes over HTTP+SSE with optional OAuth/JWKS authentication. Includes a scoped dependency injection system, agent orchestration, mid-flow user elicitation, and plugins (Cache, Remember, CodeCall) alongside OpenAPI adapter support and E2E testing utilities—all as a modular monorepo (@frontmcp/sdk, @frontmcp/auth, @frontmcp/plugins, etc.).
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work