Hex Graph
Give your coding agent a deterministic layered code graph with framework overlays and SCIP interop so navigation and refactors stay grounded in structure, not guesses.
Overview
io.github.levnikolaevich/hex-graph-mcp is a Build-phase MCP server that provides a deterministic layered code graph with framework overlays and SCIP interop for coding agents.
What is this MCP server?
- Deterministic layered code graph instead of ad-hoc ripgrep-only exploration
- Framework overlays for richer structure beyond flat file lists
- SCIP interoperability for standards-aligned symbol and reference data
- stdio npm package @levnikolaevich/hex-graph-mcp v0.9.1
- Pairs with other Hex MCP servers from the same Claude Code skills repo
- MCP server version 0.9.1
- stdio MCP transport
Community signal: 488 GitHub stars.
What problem does it solve?
Agents waste tokens and introduce architectural drift when they explore large repos without a stable, layered map of how code and frameworks connect.
Who is it for?
Solo builders on multi-package or framework-heavy repos who want agent context that respects layers and SCIP-style indexing.
Skip if: Tiny single-file prototypes where a plain file search is enough, or teams that refuse local graph/index generation overhead.
What do I get? / Deliverables
After registration, your agent can query a deterministic graph-backed model of the codebase so navigation, refactors, and reviews track real layers and SCIP-compatible structure.
- Agent-queryable layered code graph for the registered repository
- Framework overlay context on top of deterministic structure
- SCIP-interoperable symbol/reference alignment for agent tasks
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the server exists to augment day-to-day implementation and agent edits with a stable graph of the repo. Agent-tooling is where MCP servers that reshape how agents read code belong—hex-graph is infrastructure for trustworthy codebase context.
How it compares
Code-graph MCP integration, not a markdown planning skill or hash-based line editor.
Common Questions / FAQ
Who is hex-graph-mcp for?
It is for developers using Claude Code, Cursor, or similar agents who need deterministic, layered codebase graphs—including framework overlays and SCIP interop—during implementation and review.
When should I use hex-graph-mcp?
Use it when the agent must understand module layers and framework structure across a growing repo, especially before large refactors or when review needs the same graph after changes.
How do I add hex-graph-mcp to my agent?
Install @levnikolaevich/hex-graph-mcp via npm, add the stdio MCP server entry from the registry to your client config, and point it at your project per the hex-graph documentation.