Loading environmental conditions…
live
< 7d
< 30d
older
stale
Query your enterprise from inside Claude Desktop — capabilities, boundaries, owners, blast radius — synced from GitHub. Stop re-explaining the org every session.
> list_atlases({org_slug: "PlatAtlas"}) { "atlases": [{ "id": "a1b2c3d4-…", "title": "PlatAtlas Workflows", "org_slug": "PlatAtlas" }] } > get_atlas({atlas_id: "a1b2c3d4-…"}) { "atlas": { "title": "PlatAtlas Workflows", "sections": [{ "heading": "Billing", "owners": ["@finance-eng"] }, { "heading": "Auth", "owners": ["@platform"] }], "raw_markdown": "…" }} // answered from the plat — no repo grep, // no re-explaining the org this session.
server.rs
The workflow-atlas plugin measures every Claude Code session it
sees — effective tokens, cache-hit rate, spend per commit — so the
cost of working with the atlas is observable, not guessed at.
The figures below are a representative window, not your live data.
An estimate, not a measurement: the cost of an agent re-discovering your org from raw source each session, versus reading the same answer from the atlas. Your numbers will vary with org size and how much you grep.
Tap any monument and the plat lights its blast radius — what's downstream, who owns it, which commits touched it. As agents work the same map, scattered effort coalesces into effective masses along the surveyed traverses.
Today the plat already answers "if I change this, what breaks, and who do I tell?" — blast radius and ownership, drawn straight from the synced atlas.
Tap a node → downstream nodes, recent commits, declared owners. The rings on the plat.
Every traverse carries its owner and status — who is walking which parcel right now.
The trajectory: agents that read the same map stop re-treading walked ground and meet on one branch. Described here as where this is headed — not shipping yet.
Packages, flows, boundaries, milestones — hand-authored where it
matters, derived from git everywhere else. Deployed, with
wildcard subdomains per org. It's plain JSON your agent can read.
Every package, service, and capability — kind, owners, the paths it covers.
How work moves across monuments — ordered steps, each with status and owner.
Where one capability ends and another begins — eng / finance / data.
Where the org is pointed this edition, and what's still unsurveyed.
{
"families": [
{ "id": "billing", "label": "Billing" }
],
"nodes": [
{
"id": "stripe-webhook",
"label": "Stripe webhook",
"kind": "cloud-function",
"family": "billing",
"owners": ["@finance-eng"],
"paths": ["workers/stripe/**"]
}
]
}
The survey office for your org: invite teammates, set roles, mint
API keys, manage the subscription, browse the atlas. Today it lives at
platatlas.com/console.
| Member | Handle | Role |
|---|---|---|
| Ada L. | @ada | Owner |
| Grace H. | @grace | Admin |
| Katherine J. | @kj | Member |
| Finance Eng | @finance-eng | Member |
acme.platatlas.com — with the live console on your own subdomain is coming.
PlatAtlas ships as a Claude Code plugin and an MCP server. Install the plugin, point Claude Desktop at the MCP, and read your org.
PlatAtlas is installed as the workflow-atlas plugin.
> /plugin marketplace add \ RobotRegistryFoundation/claude-code-plugins > /plugin install \ workflow-atlas@robotregistryfoundation
The brand is PlatAtlas; the package is workflow-atlas.
Drop this into your Claude Desktop MCP config and sign in with GitHub.
{
"platatlas": {
"command": "/path/to/target/release/platatlas",
"args": ["mcp", "--meta",
"~/.platatlas/meta"]
}
}
Build from source with cargo build --release -p platatlas-cli. A pre-built @platatlas/cli npm wrapper is in flight (not yet published). Auth uses the same GitHub login as the trial.
From any Claude Desktop chat, query your org by capability.
> list_orgs() > list_atlases({ org_slug: "MyOrg" }) > get_atlas({ atlas_id: "<uuid>" }) > view_atlas({ atlas_id: "<uuid>" })
Five read tools ready immediately: list_orgs, list_atlases, get_atlas, query_traces, view_atlas.
A genuine PlatAtlas org you can browse right now, plus the full documentation for the plugin, the MCP, and the schema.
The real PantryAtlas org, rendered as a browsable atlas — monuments, traverses, blast radius. No install, no login.
pantryatlas.platatlas.comQuickstart, connecting Claude Desktop, the atlas schema, plugin commands, and concepts — token economy and blast radius. Coming soon.
docs.platatlas.comSign in with GitHub, provision your org, start a 14-day Pro trial. Starter is self-serve today; Pro and Enterprise start as a trial or a conversation while seat-aware billing lands.
Only Starter is self-serve today. Pro starts you in the per-org trial; per-seat checkout and the live cloud meter are on the way. No per-seat self-serve checkout exists yet — we'd rather say so.
The map your agent reads before it touches your code — your enterprise's capabilities, boundaries, and blast radius, queryable from where your agent already lives.
Loading environmental conditions…