MCP servers for Atomic Agent

Atomic Agent is an MCP client. Any MCP server you add shows up in the agent’s toolbox next to the built-in browser, shell and file tools, under the name mcp.<server>.<tool>. This section has one page per popular service: the exact config for that service’s official MCP server, what to ask the agent once it is connected, where the token lives, and what to do when the server will not start.

If you are new to MCP in Atomic Agent, read the MCP client reference first. It covers every config field, the three transports and the approval rules these pages rely on.

Connect an official server

Linear Hosted server at mcp.linear.app over Streamable HTTP, API key in a header. Read-only endpoint available.

Sentry Hosted server at mcp.sentry.dev with a Sentry-Bearer token, or the local npx server for self-hosted Sentry.

Stripe Hosted server at mcp.stripe.com with an agent API key. Start in a sandbox.

Grafana Local mcp-grafana server via uvx with a service account token. Dashboards, Prometheus, Loki.

Chrome DevTools Local chrome-devtools-mcp via npx. Performance traces, console, network, screenshots.

AWS AWS MCP Server through the local SigV4 proxy, using your AWS CLI credentials.

Zapier Hosted Zapier MCP with a connection token. Reach the apps you already connected in Zapier.

Build your own

How to build an MCP server and use it with Atomic Agent A minimal working server in TypeScript and Python with the official SDKs, connected, tested and debugged.

Three ways to add a server

Every page below gives you one JSON object. You can add it in any of three places, and all three write the same mcp.servers list in ~/.atomic-agent/config.json (the desktop app and the terminal share that folder):

Where	How	When it connects
config.json by hand	Add the object to the mcp.servers array	On the next start of the agent
Terminal UI	Run /mcp add (or press n in the /mcp panel) and paste the object	Right away
Desktop app	Settings › Connections › MCP servers › Add server, paste, press ⌘Enter (Ctrl+Enter on Windows and Linux)	Press Restart on the new row

The paste box in the TUI and the desktop app also accepts the {"mcpServers": {"name": {...}}} shape that most MCP servers print in their README, as long as it holds exactly one server. Hand-edited config.json needs the canonical shape with a transport block, which is what these pages show.

Before you connect anything

• Approvals. Tools from an MCP server ask before they run unless the server marks a tool read-only (readOnlyHint), you set the server’s trust to pure_read, you run at approval level 5 (full trust), or you allowed the category for the session. Leave write-capable servers at the default.
• No OAuth. Atomic Agent sends static headers only. Every service page here uses a token or API key path for that reason. Servers that accept OAuth only cannot be connected today.
• Tokens are stored in plain text. Header values and per-server env live in config.json. The agent writes that file with owner-only permissions (0600) on macOS and Linux, but it is not encrypted.
• Each tool costs prompt space on every turn. A server with dozens of tools makes every request longer, which matters most on small local models. Several pages show how to load fewer tools.