Hex Line
Let your agent edit files through hash-verified line operations and a token-efficiency hook instead of fragile full-file rewrites.
Overview
io.github.levnikolaevich/hex-line-mcp is a Build-phase MCP server that offers 11 hash-verified line editing tools plus a token efficiency hook for AI coding agents.
What is this MCP server?
- 11 MCP tools dedicated to AI coding agent file and line workflows
- Hash-verified edits so changes fail safely when content drifted
- Token efficiency hook to shrink noisy edit/read patterns
- stdio npm @levnikolaevich/hex-line-mcp v1.9.0
- Complements Hex Graph and Hex Research in the same skills monorepo
- 11 MCP tools for AI coding agents
- MCP server version 1.9.0
- npm package @levnikolaevich/hex-line-mcp
Community signal: 488 GitHub stars.
What problem does it solve?
Agent edits often break when files change underneath partial rewrites, burning tokens on re-reads and leaving the repo in a half-applied state.
Who is it for?
Solo builders who delegate most typing to agents and want guard-railed, line-accurate edits on real codebases.
Skip if: Workflows that only need read-only docs or pure graph exploration—use Hex Graph or plain search instead.
What do I get? / Deliverables
After you add Hex Line, the agent can apply verified line-level patches with tooling tuned for efficiency, reducing failed edits and context churn.
- Eleven MCP tools for verified line-oriented file changes
- Hash mismatch detection before corrupting stale file views
- Token efficiency improvements on agent read/edit loops
Recommended MCP Servers
Journey fit
Build is where daily agent-driven edits happen; verified line tools directly reduce broken patches and wasted context. Agent-tooling subphase covers MCP servers that change how agents mutate the repo—hex-line is specialized edit infrastructure with 11 tools.
How it compares
Hash-verified line-edit MCP with 11 tools, not a research graph or coaching scenario server.
Common Questions / FAQ
Who is hex-line-mcp for?
It is for indie developers using MCP agents who want safer, line-level file edits with verification and token-saving hooks during implementation.
When should I use hex-line-mcp?
Use it during Build agent-tooling whenever agents edit source files frequently and you need hash-checked patches instead of blind full-file replacements.
How do I add hex-line-mcp to my agent?
Install @levnikolaevich/hex-line-mcp from npm, configure the stdio MCP server in your client, and enable the 11 editing tools per the Hex Line README.