# link

link keeps shared agent memory in local Markdown files and retrieves it by meaning. Use it when you want agents to carry project decisions and preferences across sessions.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 217
- Author: gowtham0992
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/gowtham0992/link
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/mcp/link

## What it does

link turns notes, transcripts, documents, and project context into a local knowledge base. Source material goes into `raw/`; pages backed by those sources live in `wiki/`. Agents can propose preferences, decisions, and facts for review, then retrieve compact context through MCP or the CLI.

Memory stays in Markdown files you can inspect. Nothing becomes durable until you approve it, so automatic session capture does not silently add facts to your memory. For Claude Code, the setup command is `claude mcp add link -- uvx link-mcp`. The project’s quick start also shows `brew install gowtham0992/link/link` followed by `lnk setup`.

## Requirements
- Needs: Python and uv (commands run via uvx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add link -- uvx link-mcp
```
uvx runs the command named after the package; if the README names another one, use uvx --from link-mcp <command>

### Codex

**Platform CLI**
```bash
codex mcp add link -- uvx link-mcp
```
uvx runs the command named after the package; if the README names another one, use uvx --from link-mcp <command>

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "link": {
            "command": "uvx",
            "args": [
                "link-mcp"
            ]
        }
    }
}
```
uvx runs the command named after the package; if the README names another one, use uvx --from link-mcp <command>

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "link": {
            "type": "stdio",
            "command": "uvx",
            "args": [
                "link-mcp"
            ]
        }
    }
}
```
uvx runs the command named after the package; if the README names another one, use uvx --from link-mcp <command>

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add link uvx link-mcp
```
uvx runs the command named after the package; if the README names another one, use uvx --from link-mcp <command>

## When to use it
- carry agent preferences and decisions across sessions
- turn local notes and documents into a knowledge base
- retrieve relevant context by meaning rather than matching keywords
- share project context among local agents

## Example prompts
- Remember that we deploy on Tuesdays and show me the proposed memory for review.
- Find the project structure decision in my memory and give me the relevant context.
- Add the project notes and documents to my local knowledge base.

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [World Monitor](https://affpapa.org/en/nevibecode/mcp/world-monitor.md) — MCP server · ★ 89408
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [Front-End Checklist](https://affpapa.org/en/nevibecode/mcp/front-end-checklist.md) — MCP server · ★ 74559
- [Scrapling MCP Server](https://affpapa.org/en/nevibecode/mcp/scrapling-mcp-server.md) — MCP server · ★ 89433

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md