Link gives Codex, Claude, Cursor, Kiro, VS Code, Copilot, Antigravity, and other local agents the same source-backed memory, stored locally as
Link gives Codex, Claude, Cursor, Kiro, VS Code, Copilot, Antigravity, and other local agents the same source-backed memory, stored locally as Markdown. That is what the link mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Link is an open-source memory layer for local AI agents. Raw sources become an inspectable Markdown wiki. Explicit "remember this" requests become reviewable memories. Agents retrieve compact, source-backed context through the CLI, MCP, official skills, or the local viewer without dumping the whole wiki into a chat window.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 9 tools. What each one is for:
status — readiness, schema state, validation, interrupted writes, and saferecall — the one read path for startup briefs, answer-ready query packets,remember — durable local memory only after explicit user approval, withingest — exact next steps for raw files, source safety, stale ingestreview — memory inbox, profile, audit, log, explain, archive, restore,admin — the escape hatch for backup, migrate, validate, graph export, pages,Pain — Link's answerWhat — LinkLayer — What lives therePlenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Link's toolset — status, recall, remember and 6 more — is a fair guide to whether it matches your workflow. It is maintained by gowtham0992; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| status | readiness, schema state, validation, interrupted writes, and safe |
| recall | the one read path for startup briefs, answer-ready query packets, |
| remember | durable local memory only after explicit user approval, with |
| ingest | exact next steps for raw files, source safety, stale ingest |
| review | memory inbox, profile, audit, log, explain, archive, restore, |
| admin | the escape hatch for backup, migrate, validate, graph export, pages, |
| Pain | Link's answer |
| What | Link |
| Layer | What lives there |
```json
{
"mcpServers": {
"link": {
"command": "python3",
"args": ["-m", "link_mcp", "--wiki", "~/link/wiki", "--surface", "slim"]
}
}
}Configuration as documented by the project. Restart the client after saving.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.