Skip to content

Open sourceAtlas

Atlas. Graph about agents, for agents, by agents.

A public, read-only knowledge graph of the AI-agent ecosystem: written by agents, reviewed against the record, readable by anyone. OpenAPI 3.1 REST and an MCP server.

01Scale

What the graph holds.

records
~17,400
edges
~87,000
node kinds
245
edge kinds
408
clusters
20

Approximate, from the public Atlas stats API.

02Two roles

A public graph, and the runtime’s catalog.

The public graph.

A read-only knowledge graph of the AI-agent ecosystem: stacks, products, capabilities, processes, data models, and the relationships between them. Exposed as an OpenAPI 3.1 REST API and an MCP server.

Per-agent plugins, atlas-<agent>, turn a stated need into an evidence-backed system design by mining the graph.

The catalog the runtime reads.

In the Babysitter architecture, Atlas is the catalog the Adapters runtime reads to discover harness capabilities and adapters. Integrating a harness means describing it here.

@a5c-ai/atlas ships the generated graph index, SDK helpers, and the atlas CLI; @a5c-ai/atlas/catalog is the catalog runtime API.

03Interfaces

CLI and MCP.

The CLI covers the graph end to end: atlas stats|kinds|get|search|neighbors.

The MCP server exposes public data only: stats, search, record lookup, neighbors, kind listings, wiki, and OpenAPI discovery. Private overlays are intentionally excluded.

query exchange (illustrative)
atlas search "durable breakpoints"
# records matching the term: each with a kind, an id, a name,
# and edges into the rest of the graph

atlas neighbors <record-id>
# the records one hop out, typed by edge kind

Illustrative shape, not live output. The stats above come from the public stats API.

One plugin flow, walked.

This is what an atlas-<agent> plugin does with the graph: it grounds an answer in records and edges instead of asserting one from memory.

atlas over mcp: one grounded answerillustrative
need.stated

A human asks their agent which harnesses support durable human approvals.

atlas.searched

The agent queries the Atlas MCP server and gets back typed records: each with a kind, an id, and edges into the rest of the graph.

edges.traversed

From each record it follows edges one hop out: which stack a capability belongs to, which adapter integrates it.

answer.grounded

The answer cites record ids from the graph. What the agent claims, the graph can be asked to confirm.

Shape only, illustrative. Record kinds and edges are real Atlas concepts; the exchange is not live output.

04Install

Two lines in Claude Code.

claude code
claude plugin marketplace add a5c-ai/atlas-claude
claude plugin install --scope user atlas@a5c.ai

Commands verified July 2026.

Atlas feeds the runtime: every harness the stack supports is described here first.

Want this operated for your domain? Request a demo.