Archcore MCP

Ask your coding agent to keep decisions, rules, and specs versioned in.archcore/— for example, "Record this decision as an ADR."

- Search project context— Find applicable ADRs, rules, and specs before editing code usingsearch_documents.
- Record decisions as ADRs— Capture a technical decision as a structured document withcreate_document.
- Browse and read documents— List and open any context document in.archcore/vialist_documentsandget_document.
- Update existing context— Keep rules and specs current by editing documents in place withupdate_document.
- Link related documents— Connect docs withadd_relation/remove_relationusing types likeimplementsordepends_on.
- Bootstrap empty repos— Let the agent initialize.archcore/itself withinit_projectwhen starting fresh.

Archcore CLI — Git-Native Context for AI Coding Agents

Archcore is a git-native context layer for AI coding agents.

The CLI keeps specs, architecture decisions, rules, plans, and project knowledge in.archcore/, versioned with your code, and serves the relevant context to coding agents through MCP and session hooks.

It ships as a CLI and a local stdio MCP server, so any MCP-compatible coding agent can read and write your project context through standard tools. Use it for persistent project context across Claude Code, Cursor, Codex CLI, GitHub Copilot, Gemini CLI, OpenCode, Roo Code, and Cline.

That context came from.archcore/— typed Markdown documents versioned in Git, served to any agent through MCP tools and session hooks.

Every session starts from zero. The agent:

- guesses your architecture and breaks your conventions
- duplicates logic that already exists
- re-litigates decisions your team already made
- needs the same context re-explained in every chat

Your decisions, rules, and conventions live in Git as structured context. The agent:

- loads the applicable decisions and rules at session start
- puts code where your architecture says it belongs
- respects the ADRs, specs, and rules already in the repo
- records new decisions as durable context — reviewable in PRs, portable across agents

The agent stops guessing and starts following the system.

curl -fsSL https://archcore.ai/install.sh | bash # macOS / Linux cd your-project && archcore init

archcore initscaffolds.archcore/, detects your coding agents, and wires up hooks and MCP for them.

"We're using PostgreSQL for primary storage. Record this decision."

Done — there is now a structured ADR in.archcore/that every future session, in any agent, will see.

OnWindows:irm https://archcore.ai/install.ps1 | iex. For WSL,go install, and building from source, seeInstall methodsbelow or thefull install guide.

archcore mcp install --agent cursor # write MCP config for a specific agent archcore hooks install # install session-start hooks for detected agents claude mcp add --transport stdio archcore -- archcore mcp # or add the server manually

.archcore/ ├── settings.json ├── auth/ │ ├── jwt-strategy.adr.md │ └── auth-redesign.prd.md ├── backend/ │ └── error-wrapping.rule.md ├── incidents/ │ └── connection-pool-exhaustion.cpat.md └── notifications/ └── notifications-implementation.plan.md

The structure is free-form — organize by domain, feature, or team. A document's type lives in its filename (slug.type.md): 19 types across three layers — knowledge (ADRs, rules, specs, guides), vision (PRDs, plans, ideas, requirements tracks), and experience (incident patterns, recurring tasks). This repo's own.archcore/is a working example.

--- title: "Use PostgreSQL for Primary Storage" status: draft tags: [database, infrastructure] --- ## Context ...

Valid statuses:draft,accepted,rejected. Tags are optional and free-form.

10 tools:init_project,list_documents,get_document,search_documents,create_document,update_document,remove_document,add_relation,remove_relation,list_relations. The server also works in an empty repo — agents can bootstrap.archcore/themselves viainit_project.

Documents link with directed relations:related(general association),implements(source implements what target specifies),extends(source builds upon target),depends_on(source requires target). Managed by the agent through MCP tools.

archcore mcpserves documents from the current directory over stdio. Pass--project /path/to/repo(or setARCHCORE_PROJECT_ROOT) when the server is launched from a directory that isn't your workspace — for example, by an editor integration.

archcore updatechecks GitHub Releases, downloads the newer version, verifies the SHA-256 checksum, and atomically replaces the binary. It then updates the Archcore plugin on each host that already has it installed, and prints the command to run for a host whose CLI it cannot reach.

archcore pluginmanages that plugin directly on Claude Code, Cursor, Codex CLI, and GitHub Copilot.archcore initinstalls it for the hosts you select there.

From v0.8.0 the CLI also updates itself with nobody watching.archcore mcp— the server your agent starts — runs the same check in the background, at most once every 24 hours per machine, and replaces the binary only with a release published by this project, after running the downloaded binary once to prove it starts. The running process is never restarted or interrupted; a new version takes effect the next time the binary launches. Builds you compile yourself, forks, and CI runners never self-update.

No variable and no.archcore/settings.jsonkey disables this. If a machine must not update itself, install the binary into a directory its user cannot write — a root-owned location — and every attempt stops before it downloads anything.

A release build sends one event per update attempt: the versions it moved between, your OS and CPU architecture, whether the run looked like CI, whether you typed the command or the background check ran it, and which step failed when one did. It never sends an error message, a path, a user name, a hostname, or anything about your repository. SetDO_NOT_TRACK=1orARCHCORE_TELEMETRY_OPTOUT=1to send nothing at all. Both variables govern analytics only — neither stops the CLI from updating itself. Full detail:archcore.ai/privacy.

curl -fsSL https://archcore.ai/install.sh | bash

irm https://archcore.ai/install.ps1 | iex

InstallWSL, then run the macOS/Linux script inside it.

go install github.com/archcore-ai/cli@latest

git clone https://github.com/archcore-ai/cli.git cd cli go build -o archcore .

For environment variables (ARCHCORE_VERSION,ARCHCORE_INSTALL_DIR,GITHUB_TOKEN) and PATH troubleshooting, see thefull install guide.

archcore config # show all settings archcore config get <key> # get a specific value archcore config set <key> <value> # set a value

- Archcore Plugin— using Claude Code or Cursor? The plugin pairs with the CLI: same engine, plus skills, intent commands, and guardrails. One product, two entry points — the CLI on its own covers every other agent.
- docs.archcore.ai— full documentation.
- .archcore/in this repo— a living example: the CLI is built with its own context layer.

go build -o archcore . # build go test ./... # run all tests

- Documentation:docs.archcore.ai
- Website:archcore.ai
- Plugin (Claude Code, Cursor):github.com/archcore-ai/plugin
- Issues:github.com/archcore-ai/cli/issues
- License:Apache 2.0

GeneXus 18 MCP server for Claude, Cursor, and AI agents — read, edit, analyze KB objects (transactions, web panels, procedures, SDTs) over the Model Context Protocol.