Manage MCP Servers Without Hand-Editing YAML

Getting Atmos connected to an MCP server, or letting your AI assistant call Atmos's own tools, used to mean opening atmos.yaml and hand-writing a mcp.servers entry — then, separately, remembering which atmos mcp command actually pushes it into Claude Code, Cursor, or VS Code. If all you wanted was "let my AI assistant use Atmos," there was no single command that got you there.

The Fix

atmos mcp add and atmos mcp remove manage mcp.servers in atmos.yaml directly — no YAML editing required. Two built-in presets skip the boilerplate entirely: self wires up Atmos's own MCP server, and atmos-pro wires up the Atmos Pro MCP server. Run atmos mcp add with no arguments at all and it defaults to atmos mcp add self, so the entire "let my AI assistant use Atmos" flow is one command.

On the other side, atmos mcp uninstall is the mirror image of the existing atmos mcp install — it removes servers from an AI client's config without touching atmos.yaml. add/remove manage the declarative source of truth; install/uninstall push and pull it to your client. They compose, but never step on each other.

atmos mcp list and atmos mcp status also now mention these commands directly instead of just saying "no servers configured," and nudge you to run atmos mcp add atmos-pro if Atmos Pro is already configured but its MCP server hasn't been added yet.

How to Use It

# Let your AI assistant use Atmos's own tools -- writes mcp.servers.atmos,
# prompts to enable mcp.enabled if it's off, and installs into detected clients.
atmos mcp add self --install

# Add the Atmos Pro MCP server.
atmos mcp add atmos-pro

# Add an external server -- name and transport are inferred.
atmos mcp add "uvx awslabs.aws-documentation-mcp-server@latest"
atmos mcp add https://mcp.example.com/mcp --header "Authorization: Bearer ${TOKEN}"

# Remove a server, and uninstall it from wherever it was pushed.
atmos mcp remove aws-docs
atmos mcp uninstall aws-docs

See the MCP documentation for the full command reference and built-in preset details.

Get Involved

Questions or feedback? Open an issue on GitHub or join the conversation in our community Slack.