MCP Startup Framework
https://github.com/f/mcp-startup-framework- Category
- Developer Tools
- Rank
- No. 1601Tools index
Previous survey · No. 1608 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- f
- GitHub
- 127 stars
- Date
About
Opinionated TypeScript starter for shipping production MCP servers fast — by Fatih Kadir Akın.
What it does
MCP Startup Framework supplies the working parts around a remote tool server: user accounts, OAuth authorization, PostgreSQL persistence, paid-tool checks, web routes, and customizable pages. Developers register tools and routes, configure credentials, then deploy the resulting service, with Cloudflare Workers as the documented default.
Why it's ranked here
This is a substantial starting point for teams whose MCP product needs identity, persistence, billing, and web endpoints together. The code goes beyond a minimal protocol demo, including token handling, PKCE validation, authenticated user context, and payment flows. Its value drops when those product assumptions do not match your architecture.
What's good
Tool handlers receive authenticated user context, which supports per-user behavior without repeating authorization plumbing. The OAuth model covers authorization codes, refresh tokens, expiry checks, revocation, scope verification, and PKCE. Public and authenticated REST routes share the same application, while PostgreSQL stores users, clients, grants, and tokens.
Tradeoffs
Adoption brings a large operational bundle: PostgreSQL is required, Cloudflare setup is assumed by the quick start, and Stripe credentials are needed for paid tools. The included search and fetch tools return mock data, so they demonstrate contracts rather than useful integrations. Alternative deployment targets are described, but their configuration is left to the adopter.
How to use it well
Choose it for a TypeScript team building a hosted, account-based MCP service that may charge for selected tools. Start by replacing the example and mock tools, then audit authentication, database initialization, secrets, and payment behavior before launch. It does not supply real search, content retrieval, or a general data-connector layer.
Technical notes+
src/server/index.ts builds a Hono application around McpServer, creates a fresh StreamableHTTPServerTransport per authenticated request, and adapts Hono requests through the Node-style mocks in src/server/shim.ts. src/auth/oauth2.ts implements authorization-code and refresh-token flows, PKCE checks, revocation, and fixed token lifetimes through @node-oauth/oauth2-server. src/database/index.ts creates PostgreSQL tables and hashes user passwords and grant tokens, but its shown dynamic client registration stores a generated client secret directly, while src/auth/security.ts provides separate bcrypt helpers. src/tools/search.ts and src/tools/fetch.ts explicitly return mock content. package.json is private and exposes Wrangler development, deployment, type generation, and TypeScript checking scripts, with no test script shown.
Observed
- License
- MIT
- Primary language
- TypeScript
- Packaging
- Private npm project installed from a cloned repository with npm install
- Interfaces
- MCP over Streamable HTTP, legacy SSE forwarding, REST routes, and OAuth endpoints
- Default deployment
- Cloudflare Workers through Wrangler
- Database
- PostgreSQL, with direct connection strings or Cloudflare Hyperdrive
- Client reach
- Documented for desktop, web, and mobile MCP clients
Read from README.md, package.json, src/index.ts, src/types.ts, src/tools/me.ts, src/tools/add.ts, src/auth/index.ts, src/tools/index.ts, src/auth/oauth2.ts, src/server/shim.ts, src/tools/fetch.ts, src/server/index.ts, src/tools/search.ts, src/auth/security.ts, src/database/index.ts.
What it can do
Generate TypeScript MCP server boilerplate
Project configuration and requirements → Complete TypeScript starter project structure
Set up production-ready build configuration
TypeScript source code → Optimized build pipeline and configuration files
Configure MCP server protocols and handlers
Server specifications and endpoints → Configured MCP server with proper protocol handling
Generate development environment setup
Project requirements → Development scripts and environment configuration
Create deployment-ready server structure
Application code and dependencies → Production-ready MCP server deployment package
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.