[VEKTOR Memory] (https://vektormemory.com) - Local-first persistent memory for AI agents. SQLite-vec, 4-layer associative graph, 8ms recall, 34
[VEKTOR Memory] (https://vektormemory.com) - Local-first persistent memory for AI agents. SQLite-vec, 4-layer associative graph, 8ms recall, 34 tools. No cloud. The vektor slipstream mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.
vek-sync is a zero-dependency CLI that keeps your MCP (Model Context Protocol) server configurations in sync across every AI editor — Claude Desktop, Cursor, VS Code, Windsurf, Claude Code, Cline, Roo Code, Gemini CLI, GitHub Copilot, Continue, and Codex. No account. No cloud. Just a single .mcp.json file and one command.
@vektormemory/vek-sync on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: 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.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
{
"mcpServers": {
"github-com-vektor-memory": {
"command": "npx",
"args": ["-y", "@vektormemory/vek-sync"],
"env": {
"API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| 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.