Manage deployments
Control and monitor your deployed MCP servers.
After deploying an MCP server, manage it from its detail page.
Deployment statuses
| Status | Meaning |
|---|---|
| Pending | The deployment is queued and about to start. |
| Building | Source code is being built. |
| Deploying | The built server is being released. |
| Running | The server is live and accepting tool calls. |
| Needs setup | The server is built but not running. Either its required environment variables are missing, or it stopped responding after it started. It doesn't accept tool calls until setup is finished. |
| Stopped | The server is paused and not accepting tool calls. |
| Error | The deployment didn't complete; check the detail page. |
| Deleting | The deployment is being removed. |
Actions
Start, stop, or restart deployments.
Skip setup starts a server in Needs setup without the environment variables it seems to need. Use it when the server doesn't actually require them. If it doesn't respond after starting, it can return to Needs setup.
Rebuild re-builds the server from its original source. Use it after pushing new code, publishing a new package version, or changing configuration. Your secrets are preserved.
Delete permanently removes the deployment. You can't undo this, and you'll be asked to confirm.
Environment variables and secrets
If your deployment needs API keys or configuration, you set these on the deployment detail page. See Environment Variables for details.