AOCI CODE MCP Server認証済み注目

AOCI-CODE gives coding agents a persistent, Git-versioned map of the whole codebase, written by the agent and kept aligned with the code.

What is AOCI-CODE?

AOCI-CODE is a local MCP server and CLI, written in Go, that keeps a persistent, Git-versioned index of a codebase for coding agents such as Claude Code, Codex, Cursor, and OpenCode. The agent writes one line per file: what it is responsible for, which files must be read with it, what callers depend on, and the constraints that can't be inferred from the code. Agents read the whole index before a task instead of re-reading the repository every time.

How to use AOCI-CODE?

1. Download the release for your platform from https://github.com/aoci-spec/aoci-code/releases and verify it.
2. Run aoci init and aoci scan in your project. init writes the MCP configuration for Claude Code, Codex, and OpenCode; for Cursor, paste the configuration from the Config tab.
3. Restart the agent and ask it to build the AOCI index. The first build takes about an hour per 200,000 lines of code and resumes if interrupted.

Key features of AOCI-CODE

• Model-written entries from real source. Each entry is written by the model after reading the code. AOCI-CODE never assembles entries from file names, paths, ASTs, or templates.
• Whole-index delivery with a check. The index is delivered in full at session start and after context compaction, in chunks when it is large, and a sampled challenge confirms the agent actually received it.
• Drift detection and incremental maintenance. A source-hash baseline flags entries whose code changed, and the MCP server issues the entries to update when the agent finishes a task.
• Governed writes. Updates are committed as complete batches with locks, compare-and-swap, and atomic writes, with recovery evidence kept after a failure.
• Database cognition. Optional table-level entries for PostgreSQL, MySQL 5.7.6+, and openGauss 6.0.5, built from catalog metadata only. Business data is never read.
• Local only. The only connections it opens are to a database you declare and its own loopback status page. Nothing is uploaded.

Use cases of AOCI-CODE

• Taking over an existing codebase of up to about 500,000 lines, with the agent reporting how well it knows each area before it starts.
• Long-running development, where context compaction or a new session would otherwise lose the agent's picture of the system.
• Handing a project between people, agents, or conversations without rebuilding that understanding from scratch.

Tools

• aoci_rules: returns the session runtime contract for the current AOCI version.
• aoci_overview: delivers the complete index, in chunks when it is large, and checks receipt with a sampled challenge.
• aoci_header: returns the tag dictionary, FRAS rules, and calibration examples.
• aoci_search: searches entries by keyword or tag.
• aoci_get_entries: reads specific entries by path, directory, or object reference.
• aoci_maintain: after code changes settle, returns the next batch of entries that need updating.
• aoci_update_entry: submits a complete batch of model-written entries through an atomic, recoverable write.
• aoci_remove_entry: removes an entry whose source object no longer exists.
• aoci_report: records a follow-up note when evidence is insufficient to write an entry, Legacy layout only.