Ainative Memory Mcp

io.github.AINative-Studio由 GitHub 帳號 AINative-Studio 發布v1.0.1更新於 Oct 24, 2026

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

發布方自己的服務:Memory.fit

已驗證STDIO僅桌面資料庫知識與記憶

概覽

AI 產生的概覽

一個本機 MCP 記憶伺服器,把知識圖譜存放在 ZeroDB 雲端,並在標準 server-memory 工具之上加入向量語意搜尋。

可以做什麼
建立、讀取和刪除知識圖譜中的實體、觀察項目與有向關係,刪除實體時會連帶刪除關係,並可依名稱取得實體及其關係。以文字比對或向量相似度搜尋節點,依語意而非精確文字找到實體。一次讀取整份圖譜。資料存放在 ZeroDB 雲端資料表,並為每個實體產生嵌入向量,因此同一把金鑰可在任何裝置存取同一份圖譜。
適用情境
適合希望助理跨工作階段、跨裝置保留持久記憶,且願意以雲端儲存加語意檢索取代本機 JSONL 檔案的情境。它可直接替換參考實作 server-memory。
執行需求
以 stdio 方式在本機執行,通常透過 npx 啟動,需要 Node.js。選用環境變數 ZERODB_API_KEY、ZERODB_PROJECT_ID 與 ZERODB_API_URL;未提供金鑰時,首次執行會自動開通一個免費 ZeroDB 執行個體,並把憑證寫入專案的 .env 與 .mcp.json。需要能連線至 ZeroDB API 的網路。
安裝前請注意
所有記憶內容都會傳送並儲存在第三方雲端服務,而非本機。自動開通會把憑證寫入專案檔案並印出認領連結;免費執行個體僅保留 72 小時,除非完成認領。持有同一把 API 金鑰的任何人都能讀取和修改同一份圖譜,應把金鑰視為機密。刪除類工具會移除實體、觀察項目與關係,刪除實體還會一併刪除其關係。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Ainative Memory Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

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

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

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

Get an API Key

bash
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 nothingsearch_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

bash
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

來源:README.md,提交 0244800

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v1.0.1最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Memory 整合