Cartographer MCP
Map codebase capabilities and agent-memory rules with an AST plus sqlite-vec oracle your MCP host can query during A-MEM workflows.
Overview
Cartographer MCP is a Build-phase MCP server that provides a rule-tiered AST and sqlite-vec capability oracle for agent memory workflows.
What is this MCP server?
- Rule-tiered AST analysis paired with sqlite-vec for capability lookup
- Targets A-MEM style agent workflows that need an oracle of what the repo can do
- npm package `@joecwales/cartographer-mcp` version 0.1.3 via stdio
- Positions itself as a capability oracle rather than a flat vector dump
- Suitable for repeated agent sessions that must respect tiered coding rules
- Registry version 0.1.3
- npm identifier `@joecwales/cartographer-mcp` with stdio transport
- Described as rule-tiered AST and sqlite-vec capability oracle in registry metadata
What problem does it solve?
Agents guess at what your codebase allows because flat embeddings and vague rules do not encode tiered capabilities or AST-grounded facts.
Who is it for?
Builders running memory-heavy agent setups on medium or large repos who need MCP-accessible capability oracles tied to AST structure.
Skip if: Tiny weekend projects with no agent memory layer, or teams that only want generic doc search without rule tiers.
What do I get? / Deliverables
After registration, your host can query Cartographer for capability-aware context that aligns with A-MEM style agent memory decisions.
- MCP tools exposing tiered capability and AST-backed oracle queries
- sqlite-vec backed recall aligned with your agent memory workflow
- Clearer agent tool selection grounded in repo structure rather than chat-only context
Recommended MCP Servers
Journey fit
Capability mapping for agents is a Build concern because it shapes what tools and code paths your agent stack can safely use while you ship. agent-tooling holds MCP servers that augment memory, planning, and tool selection—not generic databases unrelated to agent behavior.
How it compares
Developer-tool MCP oracle for agent memory, not a hosted analytics dashboard or a brainstorming skill.
Common Questions / FAQ
Who is Cartographer MCP for?
Solo developers orchestrating A-MEM or similar agent workflows who want MCP-queryable capability maps grounded in AST and sqlite-vec storage.
When should I use Cartographer MCP?
Use it during Build and Operate when agents must pick tools and edits based on tiered repo rules instead of guessing from chat history alone.
How do I add Cartographer MCP to my agent?
Install `@joecwales/cartographer-mcp` from npm, add an stdio MCP server entry in Claude Code or Cursor, and point it at your workspace per the package docs.