LaunchFrame MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LaunchFrame MCPscaffold a new NestJS module for 'orders' following project conventions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@launchframe/mcp
MCP server that gives AI agents (Claude Code, Cursor, etc.) architectural knowledge about your LaunchFrame project — auth patterns, entity conventions, queue usage, cron jobs, webhooks, and more.
Installation
Running launchframe init automatically configures this MCP server in your project. No manual setup needed.
What It Does
Instead of bloating CLAUDE.md with rules, agents call tools on demand to pull the exact pattern they need:
Tool | Description |
| Auth system, guard hierarchy, session flow |
| Exact decorator for a given auth need |
| Guard class + import for admin/user/credits |
| How feature gates are stored and queried |
| Copy-paste feature check snippet |
| Decorator + guard for route-level credit deduction |
| Code snippet for programmatic credit addition |
| Overview of free/subscription/credits/hybrid modes |
| Available Bull queues and their purpose |
| Producer injection snippet for a given queue |
| Processor class scaffold for a queue + job name |
| Receipt/processing separation, retry logic |
| Controller + processor scaffold for a provider/event |
| Where crons live, available schedules, rules |
| Cron method scaffold to add to CronService |
| NestJS module folder structure and conventions |
| Full module scaffold (module + service + controller + entity) |
| TypeORM entity conventions and required decorators |
| TypeORM entity file scaffold |
| Centralized |
| Base / Multi-tenant / B2B2C variant differences |
| Full DB schema with tables, columns, types, and common SQL snippets |
| Subscription plans system: plan groups, annual billing, API shape |
| Overall architecture: services, modules, patterns, infrastructure |
| Email system: sending patterns, templates, built-in templates |
| Handlebars template stub for a new transactional email |
| NestJS code to send an email (direct or queued) |
| Start Docker services (detached) |
| Stop all running Docker services |
| Build Docker images (all or specific service) |
| Fetch a snapshot of Docker service logs |
| Destroy ALL Docker resources — irreversible |
| Run all pending TypeORM migrations |
| Create a new empty TypeORM migration file |
| Revert the most recently applied migration |
| Execute a SQL query (local or remote via SSH) |
| List available optional services |
| Install an optional service non-interactively |
| List available optional modules |
| Install a module non-interactively |
| Build production images and push to GHCR |
| Deploy latest images to VPS via SSH |
| Sync plan features to production DB — destructive |
| Start the waitlist service locally |
| Stop the local waitlist service |
| Build and deploy waitlist service to VPS |
| Fetch waitlist service logs from VPS |
| Create a random test user in the local DB |
| Run npm install inside a service via Docker |
| Generate and inject logo/favicon assets |
| Show local service cache info |
| Force-update the local service cache |
| Delete the entire local service cache |
Manual Install
If you prefer a global install:
npm install -g @launchframe/mcpThen in .mcp.json:
{
"mcpServers": {
"launchframe": {
"command": "launchframe-mcp"
}
}
}Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/launchframe-dev/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server