mcp-cloud-deploy
Allows running projects locally with Docker Compose, including auto-generation of Dockerfiles and compose files with optional PostgreSQL, MongoDB, and Redis services.
Allows provisioning MongoDB Atlas clusters, including project and cluster creation, database users, IP whitelisting, and different tiers.
Allows deploying applications to Railway, with optional PostgreSQL, Redis, and MongoDB plugins, and configurable environment variables and regions.
Allows deploying projects to Vercel, with automatic framework detection, production/preview deployments, environment variables, and custom build commands.
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., "@mcp-cloud-deployDeploy my project to Vercel and create a Neon PostgreSQL database"
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.
MCP Cloud Deploy
Model Context Protocol server for deploying projects to multiple cloud platforms via CLI.
Deploy your projects to Vercel, Railway, Neon (PostgreSQL), MongoDB Atlas, Docker (local), or run them as local dev servers — all through natural language commands from any MCP-compatible client (Kiro, Claude Desktop, etc.).
Features
Tool | Description |
| Deploy frontend/fullstack apps to Vercel |
| Deploy apps to Railway with database plugins |
| Create serverless PostgreSQL on Neon |
| Create MongoDB Atlas clusters |
| Run with Docker Compose (auto-generates configs) |
| Start native local dev server |
| Full-stack deploy combining multiple services |
| Verify which CLIs are installed |
Related MCP server: project-scaffold
Quick Start
1. Install
# Clone or download this project
cd mcp-cloud-deploy
# Install dependencies
npm install
# Build
npm run build2. Configure in your MCP client
For Kiro / Claude Desktop — add to your MCP config:
{
"mcpServers": {
"cloud-deploy": {
"command": "node",
"args": ["/absolute/path/to/mcp-cloud-deploy/dist/index.js"]
}
}
}For development (with auto-reload):
{
"mcpServers": {
"cloud-deploy": {
"command": "npx",
"args": ["tsx", "/absolute/path/to/mcp-cloud-deploy/src/index.ts"]
}
}
}3. Get your API tokens
Service | Where to get token |
Vercel | |
Railway | |
Neon | |
MongoDB Atlas | Organization > Access Manager > API Keys |
4. Install CLIs (only the ones you need)
# Vercel
npm install -g vercel
# Railway
npm install -g @railway/cli
# Neon
npm install -g neonctl
# MongoDB Atlas
brew install mongodb-atlas-cli # macOS
# Or: https://www.mongodb.com/docs/atlas/cli/stable/install-atlas-cli/
# Docker (for local deployments)
# https://docs.docker.com/get-docker/Usage Examples
Deploy a Next.js app to Vercel
"Deploy my project at /home/user/my-app to Vercel. Here's my token: vercel_xxxxx"The MCP will call deploy_to_vercel with:
Auto-detect framework (Next.js)
Deploy as preview (or production if specified)
Return the deployment URL
Full-stack: Vercel + Neon PostgreSQL
"Deploy my app to Vercel with a PostgreSQL database on Neon.
Vercel token: vercel_xxx
Neon API key: neon_xxx
Project name: my-saas-app"The orchestrate_deploy tool will:
Create a Neon project + database
Get the connection string
Deploy to Vercel with
DATABASE_URLinjected
Deploy everything on Railway
"Put my project on Railway with a PostgreSQL database.
Token: railway_xxx
Path: /home/user/my-api"Railway handles app + database in one platform.
Local development with Docker
"Start my project locally with Docker, include PostgreSQL and Redis"This will:
Auto-generate a Dockerfile (based on project type)
Generate docker-compose.yml with app + PostgreSQL + Redis
Build and start all containers
Return URLs for each service
Quick local dev server
"Run my project locally at /home/user/my-app on port 4000"Auto-detects Node.js/Python/Go/Rust and runs the appropriate dev command.
Tools Reference
deploy_to_vercel
Parameter | Required | Description |
| Yes | Absolute path to project |
| Yes | Vercel API token |
| No | Deploy to production (default: false) |
| No | Vercel Team ID |
| No | Custom project name |
| No | Environment variables object |
| No | Custom build command |
| No | Framework preset |
deploy_to_railway
Parameter | Required | Description |
| Yes | Absolute path to project |
| Yes | Railway API token |
| No | Railway project name |
| No | Service name |
| No | Add PostgreSQL (default: false) |
| No | Add Redis (default: false) |
| No | Add MongoDB (default: false) |
| No | Environment variables |
| No | Deploy region |
provision_neon_database
Parameter | Required | Description |
| Yes | Neon API key |
| Yes | Neon project name |
| No | Database name (default: main) |
| No | Role name (default: app_user) |
| No | Region (default: aws-us-east-1) |
| No | Path to .sql schema file |
| No | Migration command to execute |
| No | Working directory for migrations |
provision_mongodb
Parameter | Required | Description |
| Yes | Atlas public API key |
| Yes | Atlas private API key |
| Yes | Atlas Organization ID |
| Yes | Atlas project name |
| Yes | Cluster name |
| No | Tier: M0 (free), M2, M5, M10... |
| No | AWS, GCP, AZURE (default: AWS) |
| No | Region (default: US_EAST_1) |
| No | Database name (default: main) |
| No | Username (default: app_user) |
| No | Password (auto-generated) |
| No | Allow all IPs (default: false) |
| No | List of IPs to whitelist |
deploy_docker_local
Parameter | Required | Description |
| Yes | Absolute path to project |
| No | Docker service name (default: app) |
| No | Port to expose (default: 3000) |
| No | Include PostgreSQL container |
| No | Include MongoDB container |
| No | Include Redis container |
| No | Additional env vars |
| No | Custom Dockerfile path |
| No | Auto-generate Dockerfile (default: true) |
| No | Generate docker-compose.yml (default: true) |
| No | Build before start (default: true) |
| No | Run in background (default: true) |
deploy_local
Parameter | Required | Description |
| Yes | Absolute path to project |
| No | Port (default: 3000) |
| No | Install dependencies (default: true) |
| No | Migration command |
| No | Seed command |
| No | Environment variables |
| No | Path to .env file |
| No | Custom start command (auto-detected) |
| No | Run in background (default: true) |
orchestrate_deploy
Parameter | Required | Description |
| Yes | Absolute path to project |
| Yes | One of: |
| Yes | Object with tokens for each service |
| Yes | Project name |
| No | Production mode (default: false) |
| No | Additional env vars |
| No | Path to DB schema file |
| No | Port for local targets (default: 3000) |
check_deploy_prerequisites
No parameters. Returns a table showing which CLIs are installed.
Architecture
mcp-cloud-deploy/
├── src/
│ ├── index.ts # Entry point - stdio transport
│ ├── server.ts # MCP server with all tools registered
│ ├── tools/
│ │ ├── vercel.ts # Vercel deployment logic
│ │ ├── railway.ts # Railway deployment logic
│ │ ├── neon.ts # Neon PostgreSQL provisioning
│ │ ├── mongodb.ts # MongoDB Atlas provisioning
│ │ ├── docker-local.ts # Docker Compose local deployment
│ │ ├── local.ts # Native local dev server
│ │ └── orchestrator.ts # Multi-service orchestration
│ ├── auth/
│ │ └── token-manager.ts # In-memory token handling
│ └── utils/
│ ├── cli-runner.ts # Safe CLI execution wrapper
│ └── logger.ts # Stderr logger (MCP-safe)
├── dist/ # Compiled JavaScript
├── package.json
└── tsconfig.jsonSecurity
Tokens are NEVER persisted to disk — they exist only in memory during the session
Tokens are passed per-call — each tool invocation includes the token it needs
stderr for logging — all logs go to stderr to not interfere with MCP stdio
CLI execution is sandboxed — commands run with timeouts and buffer limits
Supported Project Types (Auto-detection)
The Docker and local tools automatically detect your project type:
Type | Detection | Dev Command | Docker Base |
Next.js |
|
| Multi-stage Node 20 |
Nuxt |
|
| Node 20 |
SvelteKit |
|
| Node 20 |
Vite |
|
| Node 20 |
Express/Fastify |
|
| Node 20 |
Python/FastAPI |
|
| Python 3.12 |
Django |
|
| Python 3.12 |
Go |
|
| Go 1.22 multi-stage |
Rust |
|
| Rust multi-stage |
Development
# Run in development mode (with tsx)
npm run dev
# Build for production
npm run build
# Run built version
npm start
# Clean build output
npm run cleanLicense
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceUnified deployment dashboard MCP server for AI agents. 9 tools to manage services across Vercel, Render, Railway, and Fly.io — deploy status, logs, service listing, environment variables, rollback, and health checks from one endpoint. Free tier: 50 requests/IP/day.3MIT
- AlicenseAqualityDmaintenanceAn MCP server that scaffolds full-stack projects with consistent structure, Docker setup, CI/CD pipelines, and database configuration.6MIT
- Flicense-qualityBmaintenanceAn MCP server that enables Claude to deploy full-stack web apps to Cloudflare, including databases, authentication, and file storage, directly through natural language.
- AlicenseAqualityBmaintenanceMCP server for managing a self-hosted Coolify instance. Provides full REST CRUD, deploy/watch capabilities, and an optional host-ops tier for live log streaming, SSH, Docker, and database access.228MIT
Related MCP Connectors
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server for InsForge BaaS — database, storage, edge functions, and deployments
A MCP server built for developers enabling Git based project management with project and personal…
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/fallegri/mcp-deploy'
If you have feedback or need assistance with the MCP directory API, please join our Discord server