Manage MCP servers
Keep a configured server working, decide who else can use it, and check what it offers before a conversation needs it.
Find a server
The MCP page lists servers in pages. Search narrows the list by name or description, and the ownership and status filters narrow it further. Sort orders it by name or by tool count; the default order keeps personal and instance servers grouped.
Ownership and scope
- Personal servers belong to the account that created them. Only that account can manage or use them, and in a shared conversation they are available only on that account's turns. Removing the account removes its personal servers.
- Instance servers are shared across eligible conversations, and only administrators manage them.
A conversation can use instance servers and the current account's personal servers. Names must be unique within each scope, so a personal server cannot take the name of an instance server.
A remote HTTP server can move between the instance scope and your personal scope; a move never hands it to another account. A stdio server cannot change scope, so create it again in the target scope.
Personal servers connect when one of their tools is first used, while instance servers connect when the MCP plugin starts. A personal server needs one successful tool discovery before its tools can be called.
Connection states
| State | Meaning |
|---|---|
| Connected | The server answered and its tools are available. |
| Disconnected | The server is enabled but has no live connection; reconnecting is safe. |
| Error | The last attempt failed; the detail shows the last error. |
| Disabled | The server is intentionally not connected. |
An enabled server can still be disconnected, which is different from turning it off. A server that is waiting for sign-in keeps that state until the authorization is finished; see Sign in to an MCP server.
Reconnect a server
- Fix what the error names: the address, the command or the credentials.
- Select Reconnect on the server or in its detail.
- Wait for the new state. Reconnecting closes the current connection and discovers the tools again.
Reconnect all retries the servers that are disconnected or in error and reports how many connected, needed sign-in or failed, with a message for each failure. It skips servers waiting for sign-in and legacy servers that cannot connect.
Act on several servers
Select several servers to enable, disable or delete them together. The confirmation names the count, and deleting makes the tools unavailable immediately.
Remove server deletes one server's configuration, stops its connection and makes its tools unavailable. It also clears the credentials stored for that server.
Tools and resources
Each discovered tool appears as mcp__<server>__<tool>, for example mcp__github__create_issue. The server owns the tool and its input fields; you can inspect them on the MCP page but must change them on the server itself.
Servers that publish resources also offer ListMcpResources and ReadMcpResource. They are loaded only when needed and follow the same visibility rules as the server's tools.
In an authorized chat, the assistant can add, list, reconnect and remove servers for you under the same access rules. The MCP Connector Plugin lists those operations and what each one reports.
Related guides
See Connect tools through MCP for adding a server and MCP Integration for timeouts, tool loading and ownership choices.