A Model Context Protocol (MCP) server that provides universal cloud platform deployment capabilities. Deploy to Cloudflare Workers/Pages, Vercel, Railway, and more with a single interface.
- Universal Deployment: Deploy to multiple cloud platforms with consistent interface
- Real API Integration: Uses official platform APIs (Cloudflare, Vercel, Railway)
- Cost Comparison: Compare costs and performance across platforms
- Deployment Tracking: Monitor deployment status and analytics
- Multi-Platform Analytics: Get insights across your entire deployment ecosystem
| Platform | Services | Status |
|---|---|---|
| Cloudflare | Workers, Pages, R2, KV | ✅ Production Ready |
| Vercel | Static Sites, Edge Functions, Serverless | ✅ Production Ready |
| Railway | Full-stack Apps, Databases | ✅ Production Ready |
- Install the extension:
claude mcp add chittycloude-mcp -- npx @chittyapps/chittycloude-mcp@latest- Or add manually to your MCP configuration:
{
"mcpServers": {
"chittycloud": {
"command": "npx",
"args": ["@chittyapps/chittycloude-mcp@latest"]
}
}
}- Start the server:
MCP_HTTP_MODE=true npx @chittyapps/chittycloude-mcp@latest --http- Add to your MCP client:
{
"mcpServers": {
"chittycloud": {
"type": "http",
"url": "http://localhost:3000"
}
}
}- Clone and install:
git clone <repo-url>
cd chittycloud
npm install- Run development server:
npm run devBefore deploying, authenticate with your chosen platforms:
Use the 'authenticate' tool with:
- platform: "cloudflare"
- credentials: {
"apiToken": "your-cloudflare-api-token",
"accountId": "your-account-id"
}
Get your credentials:
- Go to Cloudflare Dashboard
- Create API token with permissions:
Zone:Read,Account:Read,Cloudflare Workers:Edit - Get Account ID from the right sidebar of any domain
Use the 'authenticate' tool with:
- platform: "vercel"
- credentials: {
"apiToken": "your-vercel-token"
}
Get your token:
- Go to Vercel Account Settings
- Create new token with appropriate scopes
Use the 'authenticate' tool with:
- platform: "railway"
- credentials: {
"apiToken": "your-railway-token"
}
Get your token:
- Go to Railway Account Settings
- Create new token
Authenticate with a cloud platform
{
platform: "cloudflare" | "vercel" | "railway",
credentials: Record<string, string>
}Deploy a project to any platform
{
config: {
platform: "cloudflare" | "vercel" | "railway",
projectName: string,
environment?: "development" | "staging" | "production",
buildCommand?: string,
outputDirectory?: string,
environmentVariables?: Record<string, string>,
domains?: string[],
region?: string
}
}Check deployment status
{
platform: "cloudflare" | "vercel" | "railway",
deploymentId: string
}Compare costs across platforms
{
config: {
projectName: string,
buildCommand?: string,
outputDirectory?: string,
// ... other deployment config without platform
},
platforms?: ["cloudflare", "vercel", "railway"] // optional filter
}List all deployments
{
platform?: "cloudflare" | "vercel" | "railway", // optional filter
limit?: number // default 20, max 100
}Get detailed analytics for a project
{
projectName: string,
platforms?: ["cloudflare", "vercel", "railway"] // optional filter
}- Authenticate with a platform:
"Authenticate with Cloudflare using my API token abc123 and account ID def456"
- Deploy your project:
"Deploy my 'portfolio-site' to Cloudflare with build command 'npm run build' and output directory 'dist'"
- Check deployment status:
"Check the status of my portfolio-site deployment"
- Compare costs across platforms:
"Compare the cost of deploying my portfolio-site across Cloudflare, Vercel, and Railway"
Multi-platform strategy:
"Deploy my app to Railway for the backend API and Vercel for the frontend, then compare their performance"
Analytics and optimization:
"Show me analytics for my 'ecommerce-app' across all platforms and suggest optimizations"
Team workflows:
"List all deployments from the last week and show me which ones failed"
- ✅ Workers deployment
- ✅ Pages deployment
- ✅ Global edge network
- ✅ Environment variables
- ✅ Custom domains
- ⏳ R2 storage integration (coming soon)
- ⏳ KV namespace management (coming soon)
- ✅ Static site deployment
- ✅ Serverless functions
- ✅ Edge functions
- ✅ Environment variables
- ✅ Custom domains
- ✅ Framework detection
- ✅ Build logs
- ✅ Full-stack applications
- ✅ Database services
- ✅ Environment variables
- ✅ Service networking
- ✅ Build logs
- ✅ Resource monitoring
Authentication Errors:
- Verify API tokens have correct permissions
- Check account/team IDs are correct
- Ensure tokens haven't expired
Deployment Failures:
- Check build commands are correct
- Verify output directory exists after build
- Review platform-specific requirements
Cost Calculation Issues:
- Some platforms may not provide real-time usage data
- Costs are estimates based on current pricing
- Free tier usage may show as $0.00
Enable detailed logging:
DEBUG=chittycloud:* npx @chittycorp/chittycloude-mcp@latestCheck log files:
- Info:
/tmp/chittycloude-mcp.log - Errors:
/tmp/chittycloude-mcp-error.log
- Netlify integration
- Render.com integration
- Fly.io integration
- Automatic platform recommendations
- Deployment rollback capabilities
- Team collaboration features
- CI/CD pipeline integration
- SSO authentication
- Audit logging
- Cost budgets and alerts
- Custom deployment strategies
We welcome contributions! Please see our Contributing Guide for details.
- Fork and clone the repository
- Install dependencies:
npm install - Make your changes
- Test with:
npm test - Submit a pull request
MIT License - see LICENSE file for details.
- 📖 Documentation
- 🐛 Report Issues
- 💬 Discussions
- 📧 Email: support@chitty.cc
ChittyCloude™ MCP - Universal cloud deployment, unified experience. ☁️