> This page is for MCP Generator.

> For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://buildwithfern.com/learn/llms.txt.

# Manage in the dashboard

> Find, connect, and manage your hosted MCP servers in the Fern dashboard.

The [Fern CLI](/learn/mcp-generator/get-started/quickstart) generates and deploys your MCP servers from your API spec. The dashboard is where you find them, connect agents, and manage them once they're live.

#### Find your server

Go to `https://dashboard.buildwithfern.com/<your-org>/mcp`, or choose **MCP Servers** in the left menu. During the beta, the menu entry isn't shown for every organization, but the URL works for all.

If the page says **Let's build your MCP server**, nothing is deployed for your organization yet.

Each server appears in the list with its **Status**, **URL**, number of **Tools**, and when it was last **Updated**. Select a server to open its overview. The overview shows the **Connection URL**, the number of tools, when the server was last generated, and recent activity.

The **Generation log** on the overview lists recent generations, newest first, with who or what generated each one. To restore an earlier successful generation, select **Roll back** on its row. Fern creates a new deployment from that version, and it takes over serving. Rolling back requires edit access.

#### Connect an agent

Select **Connect**. Choose the credential your API needs, then choose the tab for your agent: **Claude Code**, **Cursor**, **VS Code**, **JSON**, or **URL**. Copy the snippet into your agent's settings.

If an agent can't reach the server, check that your network allows `*.fernmcp.dev`. Ask your IT team to add it to the allowlist if it's blocked.

#### Review and manage the server

* **Tools** lists every tool generated from your spec.
* **Analytics** shows how often agents call the server. It stays empty until the first calls arrive.
* **Settings** has the server controls:

  * **Pause server** takes the endpoint offline without deleting anything. While paused, every agent request gets an error. **Resume server** puts the server back on the deployment it had.
  * **Delete server** removes the server permanently. The endpoint stops serving immediately, the URL returns 404, and the server's deployment history is removed.

  Only organization admins can pause, resume, or delete a server.