monoceros remove-mcp-server

Takes an MCP server away from the agents in a workbench. The registration disappears from the agent’s config on the next monoceros apply. The inverse of monoceros add-mcp-server.

monoceros remove-mcp-server <name> <connector>

<connector> is the name as it stands in the yml’s mcpServers: block, so this works for a server you wrote in by hand as well as for a catalog connector. acme below is a sample workbench name.

Examples

A catalog connector, by its name:

monoceros remove-mcp-server acme context7

A server you wrote into the yml yourself, by the name: you gave it:

monoceros remove-mcp-server acme acme-crm

Behavior

• Idempotent. Removing a server that is not in the config is a no-op.
• Leaves the credential alone. Where the connector had one, the ${VAR} key stays in your env file, so re-adding it later does not mean fetching the key again. Delete the line yourself if you want it gone. A connector that signs in interactively has no key here, and the grant it holds inside the container survives the removal as well.
• Edits the yml only. Run monoceros apply to drop the registration from the agents in the container.
• Only touches what Monoceros registered. A server you added yourself inside the container with claude mcp add is not managed here and is not affected.

See also

• monoceros add-mcp-server - the inverse.
• monoceros list-components - browse the connectors in the catalog.