AXIOM runs on your own machine — the client starts it, so there is no endpoint to ping. 49 installs a week from npm. Last commit 20 Oct 2026.
Transactional write gate for coding agents: plan, canonical manifest, checks, two-phase apply.
We read the source, 19 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(
return new Uint8Array(await readFile(path.join(contentDir, rel)));
/** `apply_patch` V4A format: `*** Update|Add|Delete File: <path>` headers, `+` lines are new content. */
export function parseApplyPatch(patch: string): GateTarget[] {
const out: GateTarget[] = [];
let cur: { rawPath: string; op: "write" | "delete"; lines: string[] } | undef…
"expr": "manifest.name == 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx…
import { appendFileSync, existsSync, readdirSync, readFileSync } from "node:fs";
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add axiom -- npx -y @codai/axiom-mcp
{
"mcpServers": {
"axiom": {
"command": "npx",
"args": [
"-y",
"@codai/axiom-mcp"
]
}
}
}
[mcp_servers.axiom]
command = "npx"
args = ["-y", "@codai/axiom-mcp"]
{
"mcpServers": {
"axiom": {
"command": "npx",
"args": [
"-y",
"@codai/axiom-mcp"
]
}
}
}
{
"servers": {
"axiom": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@codai/axiom-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
AXIOM_SIGNING_KEY (Optional Ed25519 private key (base64 PKCS#8 or raw seed) used by axiom_sign; never stored under a root).
Transactional email for coding agents: send, test, verify domains, webhooks, logs.
The local security layer for coding agents: secret redaction, injection checks and an MCP proxy.
i18n for coding agents: extract, check and translate an app's text, with drafts a person approves
Local-first biological memory for coding agents: recall, consolidation, and pre-action Guard checks.
Distributed Two-Phase Commit (2PC) transaction coordinator for atomic multi-agent state mutations wi
Local mandate gate and proof trail for AI agents that take consequential actions.
Mechanical write gates, evidence receipts, and adversarial review for AI coding agents.
LSP-backed IDE intelligence plus concurrency-safe, transactional edits for AI coding agents.
Answers built from our own checks of this server.