MCP
one server, four tools
Less
tokens the model never sees
Cursor
the editor you already use
Hexum
Architecture control built for coding agents.
Smaller context. Architecture that does not drift. Same editor.
Check architecture.hexum on the path the agent already uses.
Get an API key and paste the MCP snippet →Originalsrc/ui/App.tsx
import { getOrders } from "../data/orders";
export function App() {
return getOrders();
}hexum_checkdrift_detected
! layer violation: ui → data
rule no_ui_to_data
hint: call services instead
LoopMCP
hexum_check
status: healthy
violations: 0
connect → ship → check the agent loop, in the editor you already run
4 toolsMCP v1 surface
0 CLINo local binary for customers
0 Web IDECursor stays the editor
One MCP. Two jobs.
Cut what the model is billed for, then fail the turn when architecture
breaks. You keep Cursor, Claude, or Antigravity.
01 Connect
One hexum_live_ key in the agent you already run.
02 Context
The model sees enough to ship. You are not reprinting the repo.
03 Edit
The agent writes in your tree. Git stays the source of truth.
04 Check
architecture.hexum gates layer imports. Deterministic.
Paste one JSON block.
Keys from /app. Engine is MCP. Login uses the account you already have.
Get API key