MCP servers
Connect, rename, refresh, trust and disconnect the outbound MCP servers your workspace's agents can be granted, from a terminal.
standards mcp mounts third-party MCP servers into your workspace, so agents you grant them to can call their tools: servers are granted to agents one by one (mcp:<serverId>). Servers with no auth or a static header connect from here; OAuth servers connect from the app. You need connectors on your key. Read Outbound MCP for what happens once a server is mounted.
Commands
| Command | What it does | What it prints |
|---|---|---|
standards mcp list | Lists the mounted servers. | One row per server. |
standards mcp catalog | Lists the vendored entries you can instantiate. | One row per entry; pass an id as --catalog-entry on connect. |
standards mcp connect --slug docs --name "Docs search" --url https://mcp.example.com/mcp | Mounts a server. --slug, --name and --url are required. | The created server. |
standards mcp refresh <serverId> | Re-discovers the server's tools and refreshes its status. | The refreshed server. |
standards mcp rename <serverId> "<name>" | Changes the server's display name. The slug, which prefixes its tool names, never changes. A name another visible server already carries is refused. | The renamed server. |
standards mcp trust <serverId> | Lets the server's tools run without per-call approval. --revoke withdraws it. | The updated server. |
standards mcp disconnect <serverId> --yes | Deletes the server and unmounts its tools. Refuses to run without --yes. | Nothing. |
disconnect --yes is the only destructive command; without the flag it refuses to run.
Connect
| Flag | Description |
|---|---|
--auth-type <type> | none (default) or header. |
--header-name <name> | Header to send when --auth-type header. |
--secret <value> | Header value when --auth-type header. |
--visibility <v> | workspace (default) or private. |
--catalog-entry <id> | The catalog entry this server instantiates. |
standards mcp connect --slug crm --name "CRM" --url https://mcp.example.com/mcp --auth-type header --header-name Authorization --secret "Bearer xyz"--auth-type header requires both --header-name and --secret; the CLI checks this before it sends anything. oauth is not accepted here.
Trust and revoke
A server is trusted from the moment it is connected, so its tools run without per-call approval. mcp trust <serverId> --revoke withdraws that and puts every call back behind approval; mcp trust <serverId> grants it again, which is also how you re-trust a server that a refresh demoted after its tools changed. See Outbound MCP for what trust does and does not cover.
Refresh
mcp refresh re-discovers a server's tools after they change on the other side and refreshes its status; a server that stops answering shows it here before an agent trips on it.
Next steps
- Outbound MCP: how mounted tools are namespaced, approved and re-synced.
- Workspaces and API keys: grant the
connectorspermission. - CLI: output formats and exit codes.
- Book a demo