Server settings

Repository, regions, build commands, deploy triggers, scaling, and access control.

The Settings tab is the control panel for a server's configuration. Most changes require a redeploy to take effect, the dashboard prompts you when that's the case.

Server settings: regions, deploy triggers, and danger zone

General

Rename the server and update its description. Renaming doesn't change the server's slug, edit that on the Domains tab.

Repository

See and manage the GitHub connection backing your server. For external (URL-connected) servers, this section is replaced by the External MCP URL field instead.

Deployment paths & triggers

Fine-tune when and how Git pushes deploy:

  • Root directory: the folder containing your server, for monorepos.
  • Branch allow list (globs): which branches are allowed to create deployments. The production branch always deploys.
  • Watch paths (globs): only changes under these paths trigger a deploy.
  • Wait for CI: wait for GitHub checks to pass before building.

Region

Choose where your server runs: AUTO (default), US, EU, or APAC. Specific regions require the Startup plan or higher; AUTO picks the best available location.

Deployment resources

Prevent Scale to Zero keeps your server warm so clients never hit a cold start. Available on paid plans, see Billing & plans.

Build & runtime settings

Override the framework preset's Build Command and Start Command when your project needs custom steps, and set the Dockerfile Path and Port when building from a Dockerfile.

Server configuration (JSON)

Advanced connection configuration for the dashboard's own client (Chat and inspector tabs): custom headers, OAuth settings, and connection overrides, as a JSON document.

IP allowlist

Restrict which IP addresses can reach your server through the gateway, useful for servers that should only be reachable from your own infrastructure. This section is rolling out gradually and may not be visible on your account yet.

Danger zone

Delete Server permanently removes the server, its deployments, URLs, and analytics. This cannot be undone.

On this page