
MCP Startup Boilerplate
https://github.com/f/mcp-startup-boilerplate- Category
- Developer Tools
- Rank
- No. 2033Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- f
- GitHub
- 113 stars
- Date
About
Boilerplate for building a startup around the Model Context Protocol (MCP).
What it does
This is a Rails application foundation for selling authenticated AI tools. It combines user accounts, OAuth authorization, MCP resources, usage records, subscriptions, and per-call Stripe charging. Tool authors extend base classes, register capabilities, and receive the authenticated user from an OAuth token.
Why it's ranked here
The project addresses more than MCP transport. It connects identity, authorization, billing, usage tracking, and a customer-facing dashboard in one stack. That makes it unusually practical for commercial prototypes, though the supplied code demonstrates only a small MCP surface and commits adopters to a substantial Rails application.
What's good
OAuth support includes authorization code, client credentials, refresh tokens, revocation, and PKCE. Billing distinguishes subscriptions from per-call charges and records tool, price, charge, refund, and user data. MCP capabilities inherit authenticated user context, which gives developers a direct foundation for user-scoped operations.
Tradeoffs
The stack requires Ruby, PostgreSQL, Node.js, and Yarn, with Stripe credentials needed for payments. Its identity, billing, persistence, and interface choices are tightly coupled to Rails libraries. The included MCP examples cover current-user data and a calculator, so teams must still design their actual tools, permissions, and sensitive-data rules.
How to use it well
Choose it for a Rails team prototyping a paid, account-based MCP service for Claude clients. Start with its authentication, OAuth, usage, and subscription model, then replace the examples with narrowly authorized tools. It does not supply your product logic, permission policy, production operations, or a general-purpose MCP client.
Technical notes+
The Gemfile pins Rails ~> 8.0.2 and includes fast-mcp, Devise, Doorkeeper, Stripe, PostgreSQL, Puma, Tailwind, Turbo, Stimulus, and Solid Queue, Cache, and Cable. config/routes.rb exposes Doorkeeper routes, Devise authentication, dashboards, subscription actions, a Stripe webhook, health checks, and OAuth metadata, but does not explicitly declare the documented MCP SSE route. db/schema.rb defines users, OAuth applications and tokens, subscriptions, and tool-usage billing records. app/models/user.rb retrieves or creates Stripe customers, checks subscription coverage, and aggregates usage. app/tools/me_tool.rb returns the authenticated user identifier and email as JSON.
Observed
- License
- MIT License
- Primary language
- Ruby, using Rails 8.0.2
- Install surface
- Bundler and Yarn, followed by Rails database setup and server commands
- Interfaces
- Rails web application, OAuth2 provider, Stripe webhook, and MCP server over SSE
- Database
- PostgreSQL with schemas for users, OAuth credentials, subscriptions, usage, queues, cache, and cable
- Client configuration
- Claude Desktop connection instructions are provided for macOS and Windows
Read from README.md, Gemfile, db/seeds.rb, db/schema.rb, config/boot.rb, config/puma.rb, config/routes.rb, db/cable_schema.rb, db/cache_schema.rb, db/queue_schema.rb, config/importmap.rb, config/application.rb, config/environment.rb, app/models/user.rb, app/tools/me_tool.rb.
What it can do
Generate MCP server boilerplate code
Project configuration and requirements → MCP server implementation template
Create startup project structure
Startup name and basic parameters → Complete project directory structure with files
Configure MCP protocol integration
Protocol specifications and endpoints → Working MCP protocol implementation
Generate API endpoints for MCP services
Service definitions and schemas → REST API endpoints with MCP integration
Setup development environment configuration
Development preferences and tools → Docker, environment files, and build scripts
Create authentication and authorization framework
Security requirements and user roles → Auth middleware and user management system
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.