Best for
- Developers building production MCP servers with TypeScript
- Teams needing built-in authentication, sessions, transport, and dependency injection
- Projects deploying one codebase across Node and serverless platforms
F
49FMRS · D
FrontMCP is an Apache-2.0-licensed, TypeScript-first framework for building MCP servers, with decorators, dependency injection, authentication, sessions, Streamable HTTP, SSE, plugins, adapters, and testing support. The source provides no callable tool list or client configuration example.
FrontMCP is a TypeScript-first framework for building MCP servers. Developers write typed code with decorators, Zod schemas, and app classes while the framework handles the protocol, transport, dependency injection, sessions, authentication, and execution flow. It supports Streamable HTTP and SSE and can deploy to Node, Vercel, AWS Lambda, Cloudflare Workers, or serverless bundles.
Tools
The tool list has not been reviewed yet.
Setup
Node.js 24 or later is required. For a new project, run npx frontmcp create my-app. For an existing project, install npm i -D frontmcp @types/node@^24, then run npx frontmcp init. Keep all @frontmcp/* packages on the same version.
Fit and risk
Not for
- Users who only want to consume existing MCP tools
- Projects that do not use TypeScript or JavaScript
- Use cases requiring ready-made business tools rather than an MCP server framework
Required permissions
- The source does not specify concrete runtime system permissions, network permissions, or credential scopes.
- When authentication, OAuth, JWKS, or the credential vault is enabled, required credentials and access scopes depend on the configuration.
Risks and side effects
- Node.js 24 or later is required; older runtimes may not work.
- Misconfigured authentication, sessions, or HTTP deployment may create access-control or session-management risks.
- A mismatch among `@frontmcp/*` package versions causes a boot-time version mismatch error.
- The framework supports multiple deployment platforms, but the source does not provide platform-specific configuration or security requirements.
Troubleshooting
- Confirm that Node.js is version 24 or later.
- Confirm that all `@frontmcp/*` packages use the same version.
- Review the app, tool, resource, and server decorator configuration.
- Check Streamable HTTP or SSE transport settings and the configured port.
- Use the available `frontmcp doctor`, `inspect`, `dev`, and `build` commands for diagnostics or build checks.
Use cases
Building typed MCP servers
Defining tools, resources, prompts, and apps with decorators
Adding authentication, sessions, dependency injection, and HTTP transport to MCP servers
Generating tools from OpenAPI interfaces
Writing end-to-end tests for MCP servers
Supported clients
Supported clients have not been confirmed yet.