Deployment settings
When deploying, you can configure these options in the deployment dialog.Branch
Deploy from a specific branch instead of the repository’s default branch.
Leave empty to use
main or whatever your repository’s default branch is.
Environment variables
Add environment variables your MCP server needs at runtime.Environment Variables vs Secrets
Format
Use.env format, one variable per line:
Accessing in your code
OAuth Authentication
Protect your MCP server with OAuth 2.0 authentication. When disabled, your server is publicly accessible.Enable OAuth
Toggle Enable OAuth Authentication in the deployment dialog, then configure:Supported providers
Any OAuth 2.0 / OpenID Connect provider:- Supabase Auth:
https://<project>.supabase.co - Auth0:
https://<tenant>.auth0.com - Keycloak:
https://<host>/realms/<realm> - Okta:
https://<domain>.okta.com
How it works
- MCP Deploy adds a token verification layer to your server
- Clients must include
Authorization: Bearer <token>in requests - Tokens are validated against your authorization server
Client configuration with auth
If your MCP server already implements its own authentication, MCP Deploy won’t override it.
Supported runtimes
MCP Deploy auto-detects your runtime based on project files.Python example
requirements.txt
Resource limits
Resources are managed automatically based on your plan.Cold starts on Free plan may take a few seconds when your server wakes up.