Chinese-first, brain-inspired long-term memory as an MCP server.
Give any MCP client — Claude Desktop / Claude Code / Cursor / Cline / Cherry Studio / Coze — the ability to remember and understand your user across sessions.
This repo is a thin bridge: it translates MCP tool calls into REST calls to the Zhiji backend (hosted at ai-know.me). The bridge stores nothing; all memory lives in the Zhiji service you connect to.
Why not just another vector-memory MCP?
Mem0 / Zep / LangMem expose add / search / delete over a vector store. 知己 exposes brain-inspired primitives:
Workspace assembly — one call returns profile + relevant memories + confirmed facts + behavioral inferences, budget-trimmed for the client context window.
Prospective reminders, multimodal ingest (audio / OCR / doc), and a self-evolving reward loop driven by user feedback.
All Chinese-optimized (trigram tokenizer + bge-large-zh); English is supported too. Memory is stored in the Zhiji backend you connect to — self-host it, or use the hosted ai-know.me service; either way it's your Zhiji instance, not a generic memory-SaaS middleman.
Tools, resources & prompts
9 tools, grouped by role. Every user-scoped tool takes userEmail (or falls back to MB_USER_EMAIL); only the notable extra params are listed.
Read — understand the user
Tool
What it does
Notable params
zhiji_workspace_assemble
Flagship. One call returns everything needed to understand this user for a query — relevant memories + profile + confirmed facts + behavioral inferences (plus counterfactual & cross-domain hints). Drop straight into any LLM's context.
query; maxResults ≤20 (def 6). Slow "what-if" queries can take 10–15s.
zhiji_memory_search
Lighter, recall-only: the 11-stage hybrid pipeline (trigram FTS + semantic + time-decay), returns scored snippets with sources.
query; maxResults ≤50 (def 8)
zhiji_profile_get
7-layer / 37-dim user profile as an inject-ready natural-language summary.
—
zhiji_facts_get
Structured atomic facts (subject attribution, confidence, conflict status) — for exact names/dates/counts, not narrative.
—
zhiji_prospective_due
Due/upcoming intentions (todos, promises, plans) within a time window — for proactively nudging the user.
hours ≤720 (def 24)
Write — feed memory
Tool
What it does
Notable params
zhiji_memory_ingest
Write a conversation turn to long-term memory; async embedding + profile/fact extraction + importance scoring follow. Text only.
conversationId; messages[{ author: "user"|"bot", text }]
zhiji_ingest_file
Multimodal ingest — audio / image / PDF / Word / Excel / video → Whisper transcribe / Tesseract OCR / doc parse → memory. Audio & video also get acoustic-emotion analysis.
one of path | url | base64; filename; isUserVoice
Ops — improve & diagnose
Tool
What it does
Notable params
zhiji_feedback
Thumbs up/down on the last recall/answer → feeds the self-evolution reward and reinforces (or penalizes) the Q-value of recently retrieved memories. The "gets better the more you use it" loop.
rating: "up"|"down"; weak? → ±0.5
zhiji_status
Health & memory scale (files / chunks / FTS availability). Call first to verify connectivity.
—
2 resources — zhiji://schema/dimensions (authoritative 7-layer / 37-dim profile schema) · zhiji://server/status (live service status).
1 prompt — personal-context: weaves profile + memories + facts into a ready-to-prepend system prompt for a given query.
Experimental capabilities (sleep consolidation / dream replay / emergence) are not exposed until their groundedness passes ablation.
Typical flow
zhiji_status → verify connectivity
zhiji_memory_ingest → feed a conversation (or zhiji_ingest_file for audio/docs)
zhiji_workspace_assemble → in a *new* session, recall + understand the user
zhiji_feedback → thumbs up/down, closing the self-evolution loop
The MCP layer stores nothing; it translates MCP tool calls into REST calls to the Zhiji backend. Shared core zhiji-mcp-core.mjs backs both entry points:
File
Role
zhiji-mcp-core.mjs
Tool/resource/prompt definitions (single source of truth)
zhiji-mcp-server.mjs
stdio entry (npm start)
zhiji-mcp-http.mjs
Streamable HTTP entry (npm run http)
Isolation & auth
All data is hard-isolated by userEmail. The bridge treats userEmail as a namespace, not a credential.
The hosted public endpoint requires an agent Key — requests without Bearer mb-… get 401; the backend binds each Key to its userEmail and rejects cross-user access.
Never hand a key-less, userEmail-swappable bridge to end users — front it with your own backend that injects the correct userEmail. See MCP-USAGE.md §8.
Environment
Var
Default
Notes
MB_BASE_URL
http://localhost:3001
Zhiji backend address; for the hosted service use https://ai-know.me
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
सवाल
Memory कैसे इंस्टॉल करें?
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए http कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
क्या Memory के लिए API key चाहिए?
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Memory कौन सा ट्रांसपोर्ट इस्तेमाल करता है?
Memory तक HTTP से पहुँचा जाता है।
Memory की पिछली जाँच कब हुई थी?
पिछली जाँच 2026-11-10 को हुई। Chinese-first brain-inspired memory MCP — hybrid recall, 7-layer user profile, workspace assembly.