MCP server management
These tools manage the third-party MCP servers connected to your projects — the same connections described in MCP servers under Flows — but driven through Anter's own MCP server instead of the dashboard.
Two different MCP servers, one set of tools
These tools manage the MCP servers you connect to Anter (Tavily, a vector database, an internal API) so your agents can use their tools. They have nothing to do with the Anter MCP Server you're currently connected through to call them.
| Tool | What it does |
|---|---|
list_mcp_servers | Lists servers connected to a project (or the whole org if projectId is omitted), with a query argument to narrow by name or tool |
get_mcp_server | Returns one server's details and its discovered tool catalog (names, descriptions, input schemas) |
add_mcp_server | Registers a new server connection |
update_mcp_server | Updates a server's name, description, URL, or credentials — merges into the existing config |
remove_mcp_server | Removes a server connection |
test_mcp_server_connection | Re-probes a server, refreshing its cached tool catalog |
Adding a server
add_mcp_server currently supports streamable HTTP servers — the same transport a customer's server would offer as a "streamable MCP server." You provide a name, description, URL, and authentication:
authType: "api_key"— the server is usable immediately, credentials stored encrypted.authType: "oauth"— the call returns anauthorizationUrl; open it in a browser to complete the OAuth handshake before the server's tools become available.
Discovering a server's tools
Right after adding a server (or completing its OAuth flow), call test_mcp_server_connection — it performs a real handshake and refreshes the cached tool catalog, so get_mcp_server/list_mcp_servers reflect what the server actually exposes. Every server in list_mcp_servers's response reports a catalogStatus of discovered or not_yet_discovered, so you can tell at a glance whether a re-probe is needed.
Secrets aren't echoed back
list_mcp_servers and get_mcp_server never include a server's stored auth header or API key in
their response — same policy as LLM provider secrets.
Removal is blocked while tools are wired in
remove_mcp_server fails with an error, rather than a silent no-op, if any of the server's tools
are still attached to a sub-agent. Detach the tools from the affected sub-agents first.