Your codebase never forgets. Persistent, structured memory for AI coding agents.
Your codebase never forgets. Persistent, structured memory for AI coding agents. Exposed over MCP by the repomemory mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
AI agents lose context every session. repomemory fixes that — one command creates a persistent, searchable knowledge base that any AI tool can read, search, and write to.
Everything the assistant can do here goes through one of these:
Cursor — MCP server + rules + 6 slash commandsWindsurf — .windsurfrulesCline — .clinerulesAider — .aider.conf.ymlContinue — .continue/rules/repomemory on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 6 environment variables: ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY, GOOGLE_API_KEY, GROK_API_KEY, XAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty 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. Repomemory's toolset — Cursor, Windsurf, Cline and 2 more — is a fair guide to whether it matches your workflow. It is maintained by danielguru; 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 |
|---|---|
| Cursor | MCP server + rules + 6 slash commands |
| Windsurf | .windsurfrules |
| Cline | .clinerules |
| Aider | .aider.conf.yml |
| Continue | .continue/rules/ |
{
"mcpServers": {
"repomemory": {
"command": "npx",
"args": ["-y", "repomemory"],
"env": {
"ANTHROPIC_API_KEY": "your-value",
"OPENAI_API_KEY": "your-value",
"GEMINI_API_KEY": "your-value",
"GOOGLE_API_KEY": "your-value",
"GROK_API_KEY": "your-value",
"XAI_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| GEMINI_API_KEY | Credential the server authenticates with. | Yes |
| GOOGLE_API_KEY | Credential the server authenticates with. | Yes |
| GROK_API_KEY | Credential the server authenticates with. | Yes |
| XAI_API_KEY | Credential the server authenticates with. | Yes |
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.