Cloud-persistent, semantic-search memory MCP — drop-in for server-memory, backed by ZeroDB.
Enhanced MCP knowledge graph memory server with cloud persistence and semantic search. Drop-in replacement for @modelcontextprotocol/server-memory.
| Feature | server-memory | ainative-memory-mcp |
|---|---|---|
| Storage | Local JSONL file | ZeroDB cloud |
| Persistence | Lost on machine wipe | Survives forever |
| Cross-device | No | Yes (same API key = same graph) |
| Semantic search | No (text match only) | Yes (vector similarity) |
| Setup | Manual file path | Auto-provisions on first run |
| Sharing | Copy files around | Share API key |
{
"mcpServers": {
"memory": {
"command": "npx",
"args": ["-y", "ainative-memory-mcp"],
"env": {
"ZERODB_API_KEY": "ak_your_key"
}
}
}
}
No API key? Just omit it — a free ZeroDB instance is auto-provisioned on first run.
Same config in your .mcp.json:
{
"mcpServers": {
"memory": {
"command": "npx",
"args": ["-y", "ainative-memory-mcp"],
"env": {
"ZERODB_API_KEY": "ak_your_key"
}
}
}
}
npx zerodb-cli init
Or sign up at ainative.studio.
All 9 original server-memory tools plus semantic search:
| Tool | Description |
|---|---|
create_entities | Create new entities with name, type, and observations |
create_relations | Create directed relations between entities |
add_observations | Add observations to existing entities |
delete_entities | Delete entities and their cascading relations |
delete_observations | Remove specific observations from entities |
delete_relations | Delete specific relations |
read_graph | Read the entire knowledge graph |
search_nodes | Search by text match (name, type, observations) |
open_nodes | Fetch specific entities by name with their relations |
| Tool | Description |
|---|---|
search_nodes_semantic | Vector similarity search — find entities by meaning, not just exact text |
The original search_nodes only finds exact text matches. search_nodes_semantic understands meaning:
search_nodes("ML frameworks") -> might find nothing
search_nodes_semantic("ML frameworks") -> finds "PyTorch", "TensorFlow", "JAX"
| Variable | Required | Description |
|---|---|---|
ZERODB_API_KEY | No* | ZeroDB API key (auto-provisions if missing) |
ZERODB_PROJECT_ID | No | ZeroDB project ID |
ZERODB_API_URL | No | API URL (default: https://api.ainative.studio) |
*If no credentials are provided, a free instance is automatically provisioned on first run.
On first run without credentials:
.mcp.json and .env in your projectInstead of writing to a local memory.jsonl file, this server:
kg_entities)kg_relations)@modelcontextprotocol/server-memory with ainative-memory-mcp in your MCP configZERODB_API_KEY to your env (or let it auto-provision)MIT
This package is part of the AINative ecosystem — the AI-native developer platform.
| Feature | ZeroDB | Others |
|---|---|---|
| Vector search | Built-in, free embeddings | Separate service (Pinecone, Qdrant) |
| Agent memory | Cognitive memory with decay + reflection | DIY or Mem0 ($$$) |
| File storage | S3-compatible, included | Separate S3 bucket |
| NoSQL tables | Instant, schema-free | MongoDB Atlas, DynamoDB |
| PostgreSQL | Managed, pgvector pre-installed | Neon, Supabase ($$$) |
| Serverless functions | DB-event triggered | Firebase/Supabase Edge |
| Pricing | Free tier, no credit card | Pay-per-query from day 1 |
npx zerodb-cli init # Auto-configures your IDE
Or sign up at ainative.studio — free tier, no credit card required.
No account needed to start. On first run, this package automatically:
.env, .mcp.json)Your auto-provisioned instance is free for 72 hours. To keep your data permanently, visit the claim URL printed in your terminal.
If a coding agent (Claude Code, Cursor, Windsurf) installs this package:
.claude/CLAUDE.md instructs agents to surface the claim link to you.env or ~/.ainative/config.json for your project ID if you miss itSource-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y ainative-memory-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-ainative-studio-ainative-memory-mcp": {
"command": "npx",
"args": [
"-y",
"ainative-memory-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceainative-memory-mcpnpmio.github.AINative-Studio/ainative-memory-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.