Integrations

Built for the agents you already use.

Atlas serves cited repository context to coding agents over MCP. Support levels and limitations stay explicit.

Claude CodeSupported
CursorSupported
CodexSupported
MCP clientsExperimental

Support

One index, three primary agents.

The desktop app owns the local index and config writes. Agents consume it through their MCP support.

  • 01

    Claude Code Supported

    Connect Atlas as an MCP server and ask repo-aware questions from your Claude Code workflow.

  • 02

    Cursor Supported

    Give Cursor cited local context instead of re-explaining the same files each session.

  • 03

    Codex Supported

    Use Atlas context when planning changes, debugging behavior, or mapping an unfamiliar repo.

  • 04

    MCP-compatible clients Experimental

    Atlas exposes 18 MCP tools. Validate against your client before relying on it.

Config

The shape is boring on purpose.

Atlas launches as a local stdio MCP server. The desktop app writes the exact client config and keeps backups.

mcp handoffdeterministic
01

Connect

Choose Claude, Cursor or Codex in the Atlas desktop app.

02

Write config

Atlas adds only its own MCP entry and preserves existing servers.

03

Restart agent

The agent loads the config and can query the local index.

What does an agent receive?
scan indexlocalrepository graph and evidence store stay on disk
MCP responseselectedonly cited context returned by the query
model provideragent pathyour agent may send selected context under its own terms