Manage MCP servers
List, update, regenerate, and retire the endpoints your AI clients use to reach your tools.
Where to find it: MCP Servers in the sidebar
Each row is a personal address (URL + token) that exposes one of your toolboxes. It acts as you: your connections and permissions.
You need mcp:create for your own servers. Managing someone else’s requires mcp:manage.
What the list shows
Typical columns and labels:
| Information | Meaning |
|---|---|
| Name / toolbox | Which Mine toolbox the server exposes |
| Auth | URL token only, or API token when require-API-token is on |
| Meta tools | Auto, Always, or Never |
| Created / expiry | Lifecycle metadata |
Actions
| Action | What it does |
|---|---|
| Edit | Change name, expiry, require-API-token, or meta-tools mode — does not change the URL |
| Regenerate URL | Revokes the old token, mints a new URL (shown once), so you can re-point clients without creating a new server |
| Delete | Removes the server and revokes its token |
After Regenerate URL, update Claude Desktop, Cursor, Dust, or the desktop app with the new address. The old URL stops working immediately.
Warning
Treat every MCP URL like a password. Regenerate if it might have leaked, and delete servers you no longer use.
Keep servers tidy
- Open MCP Servers.
- Confirm each server still points at the toolbox you intend.
- Regenerate URL for anything that may have leaked, then update clients.
- Delete unused servers.
You'll know it worked when: Only active servers remain, and each client’s config matches a current URL.
Good to know
- A server can only do what you can do through that toolbox’s connections.
- Tools blocked by restrictions are never offered.
- The token can’t be shown again after the first reveal — regenerate to get a new one.
- Deleting a Mine toolbox also removes MCP servers built on it.