Skip to content
atomic-agent docs

MCP

atomic-agent speaks MCP (the Model Context Protocol). Connect external MCP servers and their tools, resources, and prompts are exposed through the same tool registry as the built-in capabilities — they become first-class abilities.

What this gives you

  • Plug in any server in the MCP ecosystem
  • Their tools appear alongside browser, files, shell, git, and documents
  • No special-casing — the agent treats connected tools the same way it treats native ones

Remote control

Beyond MCP, you can drive atomic-agent from Telegram: single-user remote control with owner pairing and inline approval buttons, so you can approve risky steps from your phone when you’re away from the keyboard.

Other providers

The same extensibility applies to models: connect OpenAI-compatible HTTP endpoints or OpenRouter-style providers for text or embeddings — used only when you deliberately configure them.