LabscoMCP early access ↗
AxmeAIMCP SERVER · OFFICIAL PROJECT

AXME Code

Give a coding agent a knowledge base that survives between sessions — decisions, memories, a codebase map and a handoff from last time.

by AxmeAI ↗Agent Memory✓ Official

LABSCO SUMMARY

Decisions carry enforcement levels, which is what turns a note into a rule.

A memory the agent may ignore is worth much less than a decision it must satisfy before reporting completion — that distinction is the design here. The safety hooks only exist where the harness supports them: in other clients you get the same knowledge base and no automatic enforcement, which the project states plainly.

What it is

A persistent memory and safety layer for coding agents. It builds a knowledge base from your project, serves it over MCP so any client can read and write it, and — in Claude Code — installs hooks that block dangerous commands before they execute.

What you get

  • axme_context — the full project context at session start: stack, decisions, patterns, glossary and the previous session's handoff
  • axme_oracle — the project map: structure, tech stack, coding patterns and glossary
  • axme_decisions and axme_save_decision — architectural decisions with enforcement levels, read and written
  • axme_memories and axme_save_memory — durable notes about the project
  • axme_safety and axme_update_safety — the safety rules, and changes to them
  • axme_backlog, axme_backlog_add, axme_backlog_update — a backlog the agent maintains
  • axme_ask_question, axme_answer_question, axme_list_open_questions — the agent raises a question instead of guessing, and you answer it later
  • axme_begin_close and axme_finalize_close — structured session handoff so the next session starts where this one stopped
  • axme_status, axme_worklog, axme_workspace — current state, what was done, and multi-repo workspace handling
  • Pre-execution hooks that intercept dangerous commands at the harness level, in Claude Code

Requirements

Node.js 20 or newer on PATH. Install as a Claude Code plugin from the community marketplace, as a Cursor extension, or as a standalone binary with the published install script; then run the setup command in each project. Setup scans the project, builds the knowledge base, installs the safety hooks and writes the MCP entry. The tools work in any MCP client; the hooks and the background auditor are Claude Code specific.

Setup effort

Follow the published steps — curl -fsSL https://raw.githubusercontent.com/AxmeAI/axme-code/main/install.sh | bash