Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y @codai/[email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add codai-axiom-schema -- npx -y @codai/axiom-schema@3.0.0Ejecútalo en una terminal.
{ "mcpServers": { "codai-axiom-schema": { "command": "npx", "args": [ "-y", "@codai/[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDocs · Quickstart · Install · Harnesses · Packages · Changelog · Contributing
AXIOM is the transactional write gate for coding agents. It sits between an agent and your repository: every write and shell command the agent attempts is judged before it runs, and a change set the agent submits is applied as one transaction you can undo byte for byte.
git push --force, git reset --hard, rm -rf /, …) are allowed, asked about or denied.apply runs only with the digest you inspected, re-checks every file's prior hash at commit (two-phase), and rolls back to the byte-identical tree on any failure.axiom journal undo --session <id> restores every file one agent session wrote, including allowed writes outside the repository..axiom/decisions.jsonl (redacted); axiom explain last says which rule decided, from which profile, and how to fix it; axiom report renders a static HTML report.gh attestation verify can check.No telemetry. AXIOM sends nothing anywhere. It reads and writes only the roots you allow
and ~/.axiom/; the only outbound network access is a ref source fetch you opt into with
--allow-net.
npm i -g @codai/axiom-mcp
cd your-repo
axiom setup init # detects the harness, writes the hook + MCP entry + .axiom policy
axiom setup doctor # bin on PATH, hook wired, gate latency, policy valid (exit 2 = a check failed)
setup init writes an enforcing policy: the built-in deny list (.git/**, .env*,
lockfiles, node_modules, …), the house command pack, and four hard codes that no mode or
override can relax: house.forcePush, house.resetHard, house.cleanForce,
house.worktreeRemoveForce. Preview it first with axiom setup init --dry-run.
Now ask the agent to force-push, or to write .env. The harness blocks the call and the agent
is told why (the hook also prints the reason on stderr):
AXIOM GATE DENY house.forcePush: Force-push rewrites remote history, --force-with-lease included; ask the user first.
AXIOM GATE DENY path.deny: path matches a denied glob (.env)
Ask why, at any time:
axiom explain last # decision, rule, profile, the command or path, and FIX: what to do instead
With "undo": true in the gate policy, the gate keeps the pre-image of every file it lets
through, so one session can be rolled back after the fact:
axiom journal undo --session <agent-session-id> --dry-run # what would be restored
axiom journal undo --session <agent-session-id> # restore it; conflicts are skipped and reported
Trying the gate before enforcing it? Set "mode": "warn": denies become warnings the agent
sees (hard codes still deny), and axiom setup stats / axiom setup suggest-profile show what
would have been blocked. Every key: profiles.md.
The full walk-through, including a first transactional apply:
quickstart.
[!WARNING] Hooks need the global bin.
npxtakes seconds to resolve, the harness times the hook out, and every harness fails open on a timeout.
The bin is also installed as axgate. Axiom, Inc. ships an unrelated
CLI named axiom; if it is first on your PATH, call AXIOM as axgate (axgate setup init,
axgate gate --stdin …). Binaries ship with SHA256SUMS and Sigstore provenance, npm packages
with npm provenance: SECURITY.md. Every channel:
install.md.
axiom setup init --harness <name> wires one; auto (the default) detects it from the files in
the repository.
Hook files, payload formats, how a deny reaches each agent, and per-harness caveats: harnesses.md.
flowchart LR
accTitle: AXIOM in front of an agent
accDescr: A tool call from an agent goes through the gate, which allows, asks, warns or denies it. A change set goes through compile, checks and a digest-confirmed two-phase apply that writes the journal and can be rolled back.
A[Agent] -->|tool call| G{gate<br/>policy and rules}
G -->|allow or warn| T[Repository tree]
G -->|ask| H[Human]
G -->|deny and reason| A
A -->|Plan| P[compile<br/>canonical Manifest]
P --> C[checks<br/>whole change set]
C -->|pass| X[apply<br/>confirmDigest and 2PC]
X --> T
X --> J[(journal<br/>decisions and undo)]
J -.->|rollback or undo| T
Policy lives in .axiom/: the gate reads .axiom/axiom.json ({ version: 3, gate, checks, extends }),
and check profiles are built-in or .axiom/profiles/<name>.json.
The gate judges each tool call in milliseconds (a resident daemon answers hooks in a few
milliseconds). The pipeline checks a whole change set ("touch the schema, touch the
migration", dependency budgets, secrets, paths) and applies it atomically. Terms:
glossary. Concepts: pipeline,
trust model, invariants.
axiom plan …, axiom journal …, axiom keys …, axiom hook …,
axiom setup …, plus explain, report, pin, mcp, serve, snapshot, gc, schema),
generated from one command table; axiom <command> --help prints that command only. The 2.x
verbs (axiom gate, axiom init, axiom apply, …) keep working as hidden aliases until 4.0.
Every command: cli.md.axiom mcp --root <dir>, stdio or Streamable HTTP. 19 tools; the default
core set is the 6 an agent needs to write through AXIOM (axiom_write, axiom_status,
axiom_check, axiom_apply_dry_run, axiom_apply, axiom_rollback); --tools full adds
the plan, manifest and task plumbing. mcp-tools.md.axiom gate --stdin --format <harness>, fail-closed, or the resident daemon
axiom hook daemon. hooks.md.All public packages share one version and release together. schema and canon are leaves;
plan, checks and apply depend only on them; nobody depends on mcp (enforced by
check-package-deps). Design: v2-architecture.md.
3.0 keeps 2.x inputs working: axiom.dev/v2 plans parse, old verbs are hidden aliases, and
.axiom/gate-profile.json / .axiom/profiles/*.json are still read.
axiom setup migrate --profile writes the new .axiom/axiom.json. What changed and why:
MIGRATION.md. Release history: CHANGELOG.md.
Decisions and stories: PLAN.md · TRACKER.csv.
pnpm 12 · Node ≥ 22.14 · TypeScript 7 · tsdown · Biome · Vitest 5 · fast-check · Changesets.
pnpm install --frozen-lockfile
pnpm lint # biome check .
pnpm build # before typecheck: exports point at dist/
pnpm typecheck
pnpm test
pnpm guards # node scripts/run-guards.mjs: the repo invariants in scripts/check-*.mjs
All green with the output shown, a .changeset/*.md for any change under packages/*/src,
and the ripple closed. Details: CONTRIBUTING.md and .github/instructions/.
Discussions for questions · Issues for bugs and features · SUPPORT.md · SECURITY.md (private reporting) · CODE_OF_CONDUCT.md · CITATION.cff.
MIT © Dragos Catalin Vladulescu.
Zod v4 schemas, closed error codes and JSON Schema for AXIOM v2 Plan, Manifest, CheckReport, ApplyResult, Profile and Journal
{ "mcpServers": { "codai-axiom-schema": { "command": "npx", "args": [ "-y", "@codai/[email protected]" ] } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
@codai/axiom Schema se ejecuta localmente por stdio.
Última comprobación: 2026-10-28. Zod v4 schemas, closed error codes and JSON Schema for AXIOM v2 Plan, Manifest, CheckReport, ApplyResult, Profile and Journal