orchestrate_deploy
Orchestrate full-stack deployment across Vercel, Neon, Railway, MongoDB, or Docker, provisioning databases and connecting environment variables automatically.
Instructions
Orchestrate a full-stack deployment combining multiple services. Targets: vercel+neon, vercel+mongodb, railway-fullstack, docker-local, local. Provisions databases and deploys apps with all environment variables connected automatically.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectPath": "<projectPath>",
"target": "<target>",
"tokens": "<tokens>",
"projectName": "<projectName>"
},
"name": "orchestrate_deploy"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| port | No | Port for local deployments | |
| target | Yes | Deployment target combination: vercel+neon (frontend on Vercel, PostgreSQL on Neon), vercel+mongodb (frontend on Vercel, MongoDB Atlas), railway-fullstack (everything on Railway), docker-local (Docker containers locally), local (native local dev server) | |
| tokens | Yes | API tokens for the services being used | |
| envVars | No | Additional environment variables | |
| dbSchema | No | Path to database schema file (.sql or migration) | |
| production | No | Production deployment | |
| projectName | Yes | Name for the project across services | |
| projectPath | Yes | Absolute path to the project |