@a5c-ai/atlas
Atlas catalog graph package. It ships the generated graph index, SDK helpers for graph interaction, and the atlas CLI.
Usage
import { getStats, getRecord, searchRecords } from "@a5c-ai/atlas";
console.log(getStats());
console.log(getRecord("some-node-id"));
console.log(searchRecords("codex"));
atlas stats
atlas kinds
atlas get <node-id>
atlas search codex --limit 10
atlas neighbors <node-id> --depth 2
Catalog Runtime
Atlas also ships the catalog runtime API as @a5c-ai/atlas/catalog. Use this
subpath for graph-backed agent metadata, discovery snapshots, UI projections,
fallback harness metadata, host detection rules, plugin targets, and
package/process topology.
import {
getCatalogDiscoverySnapshot,
getFallbackHarnessMetadata,
listPluginTargetDescriptors,
resolveCatalogAssetPath,
} from "@a5c-ai/atlas/catalog";
const discovery = getCatalogDiscoverySnapshot();
const claude = getFallbackHarnessMetadata("claude-code");
const pluginTargets = listPluginTargetDescriptors();
const assetPath = resolveCatalogAssetPath("discovery-snapshot.json");
Build and validate the catalog surface with atlas:
npm run build --workspace=@a5c-ai/atlas
npm run test:atlas-catalog-contracts
MCP
The Atlas MCP surface is exposed by the Atlas WebUI as a Streamable HTTP endpoint:
http://localhost:3000/api/mcp
Start the WebUI locally:
npm install
npm run dev -w @a5c-ai/atlas-webui
Then connect any MCP client that supports Streamable HTTP directly to that endpoint.
Example remote MCP client config:
{
"agentic-ai-atlas": {
"url": "http://localhost:3000/api/mcp"
}
}
For clients that only speak stdio, bridge to the remote MCP endpoint with npx:
npx -y mcp-remote http://localhost:3000/api/mcp
Example stdio client config through npx:
{
"agentic-ai-atlas": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"http://localhost:3000/api/mcp"
]
}
}
Current MCP scope is public Atlas data only:
- graph stats and clusters
- search
- record lookup
- incoming and outgoing neighbors
- node-kind and edge-kind listings
- wiki pages
- OpenAPI discovery for the public REST surface
Authenticated overlays, user-uploaded subgraphs, and other private workspace data are intentionally excluded for now.