Manage servers

The Servers page gives you a central, at-a-glance view of all MCP servers for an app — their health, recent traffic, and public endpoints — and lets you act on each one without navigating to the individual publish page.

Finding a server

Below the summary you can:

• Filter by status with the tabs — All, Published, Draft, or Disabled (each shows a count).

• Search by name, branch, or slug. Press ⌘K (Ctrl+K on Windows/Linux) to jump straight to the search box.

Reading a server card

Each server is shown as a card with:

• Name and a status badge — Published, Draft, or Disabled

• Health pill — Healthy, Degraded, Down, or Not deployed (derived from recent traffic)

• Endpoint — the public MCP URL, with a Copy button

• A short deploy line — when it was last deployed (or "Never deployed")

• A metrics strip — tool calls in the last 24h, error rate, average latency, and server errors

• Actions — Test, Playground, Logs, History, and Manage

When a server is Degraded or Down, the card surfaces a notice with the error rate and an Investigate → link to its logs.

Unpublishing a server

Click Unpublish on any Published server to take it offline immediately. A confirmation dialog appears before the change is made. AI clients connected to that server will stop working until you re-publish.

To re-publish or view the full publish details (MCP config snippets, tool blockers), click Manage to open the server's publish page.

Creating servers

Servers are created per branch. Click New server (or Spin up a new server on the empty card) to go to Settings → Branches, where you can add a branch.