- Zero-config deployment — no DevOps, no infrastructure setup
- Built-in monitoring — see tool calls, errors, latency in real-time
- Observability — logs, traces, and metrics out of the box
- Auth integration — connect Clerk, Auth0, or other providers directly on the platform
- GitHub CI/CD — push to GitHub, automatically deploy to production
Option 1: GitHub Integration (Recommended)
Connect your GitHub repository and deploy automatically on every push.Step 1: Create a Project
Go to ship.leanmcp.com and create a new project.Step 2: Connect GitHub
Link your GitHub repository to the project. LeanMCP will automatically detect yourleanmcp.config.js or package.json.
Step 3: Push and Deploy
Every push to your main branch triggers a deployment:https://your-project.leanmcp.link.
Option 2: LeanMCP CLI
Deploy directly from your terminal using the LeanMCP CLI.Step 1: Install and Login
Step 2: Create a Project
Step 3: Deploy
Full CLI Workflow
Monitoring and Observability
Once deployed, the LeanMCP dashboard shows you:- Tool call analytics — which tools are called, how often, success rates
- Error tracking — see errors with full stack traces
- Latency metrics — p50, p95, p99 response times
- Real-time logs — stream logs from your production MCP
Auth on the Platform
If your MCP needs authentication, you can configure it directly on LeanMCP Platform:- Go to your project settings
- Select your auth provider (Clerk, Auth0, Cognito, etc.)
- Add your credentials
- Enable auth for your MCP
Why LeanMCP Platform?
| Feature | LeanMCP Platform | DIY Deployment |
|---|---|---|
| Setup time | Minutes | Hours to days |
| Monitoring | Built-in | Configure yourself |
| Auth | One-click setup | 600+ lines of code |
| Scaling | Automatic | Manual configuration |
| Cost | Pay per use | Infrastructure + DevOps |