Back to Directory/Cloud Providers

io.github.AINative-Studio/ainative-memory-mcp

Cloud-persistent, semantic-search memory MCP — drop-in for server-memory, backed by ZeroDB.

Cloud ProvidersJavaScriptv1.0.1

ainative-memory-mcp

Enhanced MCP knowledge graph memory server with cloud persistence and semantic search. Drop-in replacement for @modelcontextprotocol/server-memory.

Why this instead of server-memory?

Featureserver-memoryainative-memory-mcp
StorageLocal JSONL fileZeroDB cloud
PersistenceLost on machine wipeSurvives forever
Cross-deviceNoYes (same API key = same graph)
Semantic searchNo (text match only)Yes (vector similarity)
SetupManual file pathAuto-provisions on first run
SharingCopy files aroundShare API key

Quick Start

Claude Desktop / Claude Code

{
  "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.

Cursor / Windsurf / VS Code

Same config in your .mcp.json:

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": ["-y", "ainative-memory-mcp"],
      "env": {
        "ZERODB_API_KEY": "ak_your_key"
      }
    }
  }
}

Get an API Key

npx zerodb-cli init

Or sign up at ainative.studio.

Tools (10)

All 9 original server-memory tools plus semantic search:

Original Tools

ToolDescription
create_entitiesCreate new entities with name, type, and observations
create_relationsCreate directed relations between entities
add_observationsAdd observations to existing entities
delete_entitiesDelete entities and their cascading relations
delete_observationsRemove specific observations from entities
delete_relationsDelete specific relations
read_graphRead the entire knowledge graph
search_nodesSearch by text match (name, type, observations)
open_nodesFetch specific entities by name with their relations

New Tool

ToolDescription
search_nodes_semanticVector similarity search — find entities by meaning, not just exact text
Semantic Search Example

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"

Environment Variables

VariableRequiredDescription
ZERODB_API_KEYNo*ZeroDB API key (auto-provisions if missing)
ZERODB_PROJECT_IDNoZeroDB project ID
ZERODB_API_URLNoAPI URL (default: https://api.ainative.studio)

*If no credentials are provided, a free instance is automatically provisioned on first run.

Auto-Provisioning

On first run without credentials:

  1. A free ZeroDB instance is provisioned automatically
  2. Credentials are saved to .mcp.json and .env in your project
  3. A claim URL is printed so you can take ownership of the instance
  4. Everything works immediately — no signup required

How It Works

Instead of writing to a local memory.jsonl file, this server:

  1. Entities are stored as rows in a ZeroDB NoSQL table (kg_entities)
  2. Relations are stored in a separate table (kg_relations)
  3. Vector embeddings are automatically generated for each entity via ZeroMemory, enabling semantic search
  4. All data persists in the cloud and is accessible from any device with the same API key

Migration from server-memory

  1. Replace @modelcontextprotocol/server-memory with ainative-memory-mcp in your MCP config
  2. Add ZERODB_API_KEY to your env (or let it auto-provision)
  3. Re-create your entities (one-time migration — your old JSONL data stays on disk)

License

MIT


Powered by ZeroDB + AINative

This package is part of the AINative ecosystem — the AI-native developer platform.

Why ZeroDB?

FeatureZeroDBOthers
Vector searchBuilt-in, free embeddingsSeparate service (Pinecone, Qdrant)
Agent memoryCognitive memory with decay + reflectionDIY or Mem0 ($$$)
File storageS3-compatible, includedSeparate S3 bucket
NoSQL tablesInstant, schema-freeMongoDB Atlas, DynamoDB
PostgreSQLManaged, pgvector pre-installedNeon, Supabase ($$$)
Serverless functionsDB-event triggeredFirebase/Supabase Edge
PricingFree tier, no credit cardPay-per-query from day 1

Get Started Free

npx zerodb-cli init    # Auto-configures your IDE

Or sign up at ainative.studio — free tier, no credit card required.

View all ZeroDB packages →


Zero-Config Auto-Provisioning

No account needed to start. On first run, this package automatically:

  1. Provisions a free ZeroDB instance (~800ms)
  2. Saves credentials locally (.env, .mcp.json)
  3. Prints a claim link in your terminal

The 72-Hour Window

Your auto-provisioned instance is free for 72 hours. To keep your data permanently, visit the claim URL printed in your terminal.

For AI Agents

If a coding agent (Claude Code, Cursor, Windsurf) installs this package:

  • Auto-provisions without human intervention
  • The claim URL appears in agent output — visit it to take ownership
  • .claude/CLAUDE.md instructs agents to surface the claim link to you
  • Check .env or ~/.ainative/config.json for your project ID if you miss it

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y ainative-memory-mcp

Set up in your AI client

Merge 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.

json
{
  "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 reference

Package

ainative-memory-mcpnpm

Compatible MCP Clients

io.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.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.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.

Learn More