When you would want it

One set of notes shared by every assistant you use, rather than each one starting from nothing.

Where to find it

All Features → MCP server
Turn on or off
Settings

What you get out of it

Every assistant you run shares one project memory instead of five partial copies.
Notes go both ways: what a terminal agent learned is visible to the built-in one.
Set it up once: the command points at a copy of the server in your home folder, so it keeps working while Agentfly is closed and after it updates - portable, AppImage and Store builds included.

How to use it, step by step

Check you have Node.js 22.13 or newer: run node --version in a terminal. If the command is not found, or the version is older, install the current LTS from nodejs.org. Your agent starts the server with this Node.js, not with Agentfly.
Open Tools and choose Memory, or open Settings and find the MCP server section - it is on by default.
Copy the connection command shown there.
Run it once from your project folder, in a terminal opened after Node.js was installed.
Any MCP-capable tool - Claude Code, Codex, and the rest - now reads and writes the same notes as Agentfly's assistant.
If your agent reports that the adcode server failed to start, run node --version in that same terminal. A missing or older Node.js is the usual cause.

Why this beats the usual way

Each AI tool keeping its own silo means every session starts from zero context. A shared MCP server makes the project itself the memory - one source, every assistant.

Find it in Universal Search

MCP server · The assistant