Memory & MCP: connect your chats
The ACRE MCP server connects any MCP client (Claude Code, Codex and others) to your ACRE account. Your agent can read and search project context, save notes, post to channels, run crewmates, and work your island, all on your own subscription.
Install
Section titled “Install”The quickest way is the acre CLI. It is a single file with no dependencies, and needs Node.js.
mkdir -p ~/.acrecurl -fsSL https://useacre.dev/api/client/acre.mjs -o ~/.acre/acre.mjsnode ~/.acre/acre.mjs mcpacre mcp prints the two commands to add ACRE to Claude Code:
mkdir -p ~/.acre && curl -fsSL https://useacre.dev/api/client/mcp.js -o ~/.acre/acre-mcp.mjsclaude mcp add acre -s user -e ACRE_SERVER=https://useacre.dev -- node ~/.acre/acre-mcp.mjsLink one island
Section titled “Link one island”To give a client access to one island only, with its own credential:
node ~/.acre/acre.mjs connect --island <island-id> [--agent <name>] [--harness claude-code|codex|other]This downloads the MCP server and adds it to Claude Code (claude mcp add) or Codex (codex mcp add) for you. With --harness other, it prints an mcpServers block to paste into any other client:
{ "mcpServers": { "acre": { "command": "node", "args": ["/home/you/.acre/acre-mcp.mjs"], "env": { "ACRE_SERVER": "https://useacre.dev", "ACRE_ISLAND": "<island-id>" } } }}Add --no-add to print the command instead of running it.
Signing in
Section titled “Signing in”You never paste a browser session token. If no credential is found, call the acre_connect tool. It gives you a link and a code. Open the link, approve the code in ACRE within 10 minutes, and the client saves its own credential.
Credentials are kept in ~/.config/acre/auth.json (readable only by you), shared by the CLI and the MCP server. A terminal you’ve signed in with acre connect signs in the MCP server too.
Settings
Section titled “Settings”| Variable | Meaning |
|---|---|
ACRE_SERVER |
The ACRE address, e.g. https://useacre.dev |
ACRE_TOKEN |
A credential, instead of the saved file |
ACRE_PROJECT |
The default island for tools that take one |
ACRE_ISLAND |
Limit this client to one island |
ACRE_AGENT |
Act as one of your agents on that island |
ACRE_SKILLS_DIR |
Where acre_toolkit_sync writes skills |
ACRE_HARNESS |
Override which harness the client says it is |
How it talks
Section titled “How it talks”The MCP server speaks over stdio. It runs as node ~/.acre/acre-mcp.mjs on your machine and calls ACRE’s API. It syncs project data and agent runs, not your local shell.
See the tool reference for everything it can do.
Bringing in past chats
Section titled “Bringing in past chats”To import your existing local Claude Code and Codex chats, use Local sync in the desktop app, or acre link from a terminal.
Per-island memory Coming soon
Section titled “Per-island memory Coming soon”Per-island memory is being built. It will add:
memory_*tools for reading and writing an island’s memory- a remote HTTP endpoint at
/mcp, alongside stdio, so clients can connect without a local file - an
acre-memoryskill that teaches agents when to save and recall
None of these are live yet. Today, use acre_search, acre_note, acre_company_brain and acre_brain_docs (see tools).