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.
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:
- Production branch: which Git branch serves your canonical production URL and always auto-deploys.
- 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.
Rate limiting
Optionally throttle traffic at the gateway per caller (by real client IP):
- Disabled by default — turn on with the toggle on the Settings tab.
- Requests per minute — max requests each caller can make in a rolling 60-second window (default 1,000 when enabled without a custom value).
- Exceeded callers receive
429 Too Many Requestsuntil the window resets.
Applies independently to this server. Does not replace plan-level credit enforcement on the Free tier.
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.
Analytics capture
Toggles here control what the gateway stores for Usage & traffic (including the Issues card) and Sessions. Changes apply immediately — no redeploy required.
| Toggle | What it enables |
|---|---|
| Capture payloads | Store request and response bodies for gateway events — powers session timeline previews, output token estimates, tool-definition sizing, and richer error context |
| User intent capture | Inject an optional user_intent field on tool calls so AI goal discovery and session classification can cluster what users are trying to accomplish |
Sensitive data
Payloads can contain user data. Enable capture only when you need it, and disable it again when you're done debugging.
The Capture payloads toggle also appears on the Gateway Requests tab for quick access while debugging.
Danger zone
Delete Server permanently removes the server, its deployments, URLs, and analytics. This cannot be undone.