Persistent memory, decisions, and safety guardrails for Claude Code
Axme Code MCP server exists for a simple reason — assistants are far more useful when they can act on Axme Code directly instead of describing what you should do. Persistent memory, decisions, and safety guardrails for Claude Code.
Stop re-explaining your architecture on session 47. Stop losing memory between session handoffs. Stop hoping the agent won't run git push --force to main. AXME Code remembers what happened, enforces your architectural decisions, continues where the last session stopped, and blocks dangerous commands before they execute — so you can focus on building.
Once Axme Code is connected, these are the calls the assistant has available:
Cursor — ** ~/.cursor/mcp.json or .cursor/mcp.json (per-project)Windsurf — ** ~/.codeium/windsurf/mcp_config.jsonCline — ** VS Code Settings → Cline MCP → cline_mcp_settings.jsonVerify-only — when the agent completed the close checklist (lighter, cheaper)Errors — category and bounded error class for failures in audit, setup, hooks, and auto-updateCategory — What it storesOracle — Project structure, tech stack, coding patterns, glossaryDecisions — Architectural decisions with enforcement levelsMemory — Feedback from mistakes, validated patternsSafety — Protected branches, denied commands, filesystem restrictionsBacklog — Persistent cross-session task trackingHandoff — Where work stopped, blockers, next stepsYou will need 2 environment variables: AXME_TELEMETRY_DISABLED, DO_NOT_TRACK. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Axme Code's toolset — Cursor, Windsurf, Cline and 11 more — is a fair guide to whether it matches your workflow. It is maintained by axmeai; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Cursor | ** ~/.cursor/mcp.json or .cursor/mcp.json (per-project) |
| Windsurf | ** ~/.codeium/windsurf/mcp_config.json |
| Cline | ** VS Code Settings → Cline MCP → cline_mcp_settings.json |
| Verify-only | when the agent completed the close checklist (lighter, cheaper) |
| Errors | category and bounded error class for failures in audit, setup, hooks, and auto-update |
| Category | What it stores |
| Oracle | Project structure, tech stack, coding patterns, glossary |
| Decisions | Architectural decisions with enforcement levels |
| Memory | Feedback from mistakes, validated patterns |
| Safety | Protected branches, denied commands, filesystem restrictions |
| Backlog | Persistent cross-session task tracking |
| Handoff | Where work stopped, blockers, next steps |
| Worklog | Session history and events |
| Client | MCP Tools |
{
"mcpServers": {
"axme": {
"command": "axme-code",
"args": ["serve"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AXME_TELEMETRY_DISABLED | Configuration value read at startup. | Optional |
| DO_NOT_TRACK | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.