StackMap
Subscribe
Explore / graphicle

graphicle alternatives

Curated alternatives to graphicle — and why you'd switch.

codebase-memory-mcp

Code intelligence MCP in pure C: tree-sitter knowledge graph over 158 languages, average repo indexed in milliseconds, sub-ms queries, 10x fewer tokens. Single static binary, zero deps.

Why switchBoth serve a tree-sitter code knowledge graph to agents over MCP. codebase-memory-mcp is pure C and code only; Graphicle adds docs, decisions and session memory.
Full comparison →
gortex

Code-intelligence engine in one static Go binary: tree-sitter graph over 257 languages, compiler-grade resolution for 17, multi-repo, 175 configurable MCP tools — up to 50x fewer tokens. 100% local.

Why switchBoth are single-binary code-intelligence engines over a tree-sitter graph for agents.
Full comparison →
code-review-graph

Local-first code intelligence graph for AI coding tools: Tree-sitter AST graph + blast-radius analysis served over MCP, so agents read ~82x fewer tokens per review question.

Why switchBoth build a local code graph for AI coding tools. code-review-graph focuses on review blast radius; Graphicle adds memory.
Full comparison →
claude-mem

Cross-harness session memory: hooks capture what the agent does, an LLM compresses it into observations, and the next session gets the relevant ones back via progressive-disclosure MCP tools.

Why switchFor the memory half: both remember past agent sessions. claude-mem compresses observations; Graphicle ties them to the code graph.
Full comparison →
cortexdb

Agent memory plus a knowledge graph with ontology constraints in one SQLite file: pure Go, no server, no embedding model required. Plugins for Claude Code, Codex, dsh and Obsidian.

Why switchBoth are local, single-install memory for coding agents with structured recall. Graphicle ties memory to a code graph; CortexDB to a typed knowledge graph in SQLite.
Full comparison →