For agents mid-task
Connect an agent
The Agent projection is hosted at /mcp/ — nothing to install, nothing to cache, no local corpus. It serves the one active Release.
Two ways in
Claude Code plugin
Marketplace command
/plugin marketplace add aj604/agentic-atlas-plugin
Then install agentic-atlas.
Three skills cover the three design moments — reviewing-agent-designs audits an existing skill, agent, or plugin against the patterns; designing-agent-systems interviews, consults once, and proposes a cited decomposition; applying-a-pattern turns one named pattern into a cited edit plan. Two read-only agents (pattern-librarian, design-auditor) return bounded, path-cited distillations.
Any MCP client
Streamable HTTP, no auth.
Hosted MCP URL
https://agentic-atlas.dev/mcp/
CLI wiring command
claude mcp add --transport http atlas https://agentic-atlas.dev/mcp/
The ladder, briefly
Consult in order of cost, not in a fixed sequence: atlas_orient, then atlas_cards, then one addressed Section off atlas_read, then — for the one or two ids the decision actually turns on — the complete Node. Consultation cost stays proportional to relevance.
Every payload names the Release it was read from. Pass that value back as expected_revision on every later call of the same consultation: a promotion between calls is refused with revision_changed, never silently crossed.
Read the full copyable discipline →
The entire supported surface. A name not in this table does not exist; there are no aliases.
Verify the wiring with one call: atlas_orient on ordinary design vocabulary, for example “context budget.” A successful payload returns candidate identities with status and hook — a miss is itself a successful payload, not an error.