MCP Vector Memory

MCP数据服务

提供方 wyckit

数据服务 stdio · 本地进程 无需鉴权 社区 / 第三方 Claude
查看接入方式

为AI代理提供跨会话的持久记忆功能,支持自动信息存储、主题检索和知识图谱可视化。

一句话选型结论

按资料字段整理

MCP Vector Memory 属于数据服务类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类数据服务 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 5 仓库热度,无公开仓库时显示未标注
工具数 61 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

数据服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量61暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

AI记忆C#本地部署知识图谱会话持久化智能检索多代理协作

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
docker run -i -v memory-data:/app/data mcp-engram-memory

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Docker,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 61 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
数据库查询

用自然语言查库、取数,不用手写 SQL。

数据同步与清洗

把多来源数据拉到一处做整理。

报表取数

按口径快速拉出统计结果。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 61 个工具,覆盖面较广,能满足多种调用。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在数据服务场景里让模型直接调用外部能力的人。
  • 已经在用 Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Vector Memory当前 61 stdio · 本地进程 本地部署 有 2026-05-17
Memory 9d25f64e 9 未标注 未标注 无 2026-05-17
Getzep MCP 9 stdio · 本地进程 本地部署 有 2026-05-17
anything-llm 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Prisma MCP Server 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Astr Bot 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

数据服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方wyckit上游标注的维护方 wyckit
分类数据服务本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Docker本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

21.9 KB
来自项目仓库与上游目录的原文,未做删改

The governed, local-first cognitive memory kernel for AI agents

Memory physics, not just storage. Most agent memory systems store context. Engram evolves context — topology-driven decay, consolidation, and contradiction detection, all running locally with zero external API.

2.1 improves recall and release reliability. Questions recover relevant sources under noise, historical and compound answers retain the requested evidence, and routing preserves project, environment, tenant and namespace boundaries. Persistence, timers and installation upgrades are hardened without changing MCP tool names or arguments.

  • Tenant-Partitioned Throughout — partitioning runs through storage, graph, clusters, lifecycle, diffusion, synthesis, and visualization. Edges never cross tenants; cross-namespace association within a tenant is preserved.
  • Context Control — graph-Laplacian diffusion decays trivial chats so your context window doesn't choke on noise. Important, well-connected knowledge stays sharp; transient chatter fades.
  • Contradiction Detection — find_contradictions surfaces conflicting goals or architecture decisions on demand, so you can review and retire logic you've already reversed instead of letting the agent keep acting on it.
  • Governed Core — a deterministic Root Constitution, versioned knowledge and provenance, Teacher/Verifier promotion, authorization-first retrieval planning, and citation-aware context manifests are available to embedding hosts.
  • Privacy by default — local ONNX embeddings and local storage. The MCP executable enforces ONNX telemetry suppression before loading the native runtime on Windows, Linux and macOS; see the telemetry policy and validation. Optional remote storage, synthesis and live benchmark services make network calls only when configured. Hosts embedding the Core library must establish their own process policy.

→ See the cold-start scorecard · Get started in 5 minutes · What's new in 2.1

What's New in 2.1

Change What it means
More complete recall Direct and routed searches recover missing answers under noise, retain sources alongside summaries, and cover broad, compound and historical questions.
Evidence-based answers Non-answer text and mismatched project/environment evidence are rejected; superseded claims rank appropriately and unresolved contradictions remain visible.
Reliable persistence and maintenance Merge/snapshot deadlocks and stale timer callbacks are fixed. Deterministic concurrency and simulated maintenance tests supplement bounded real MCP stress.
Safer installation and upgrades The server uses a durable user data directory; the pre-update helper preserves old package-local data before replacement. Client configuration is preserved.
Early telemetry suppression The MCP executable suppresses ONNX telemetry before native initialization on the validated Windows, Linux and macOS platforms.

This documentation targets 2.1.0; package commands require that version in the selected feed.
The three packages ship together. MCP profiles remain 17 / 39 / 63 tools, and the Core/Synthesis
public APIs remain compatible with 2.0.0. New optional recall conflict diagnostics are additive.

Upgrading an existing 2.0.0 tool: stop its servers and follow the
pre-update migration procedure before running a package
update or uninstall. The old package manager removes version-local default data during replacement.
Existing explicit data paths remain supported. Read the 2.1.0 release notes
for compatibility, validation and limits. Hosts upgrading from pre-2.0 Core must still follow the
2.0 API migration.

How It Works

Engram sits between your AI assistant and a local store. Every memory is embedded, indexed for hybrid search, woven into a knowledge graph, and then left to evolve on its own — background workers decay noise, consolidate what matters, and densify the graph while you're away.

The loop, end to end:

  1. Store — remember embeds text with a local ONNX model (bge-micro-v2, 384-dim), detects near-duplicates, and auto-links the new memory to related ones in the graph.
  2. Search — recall runs hybrid retrieval (BM25 keyword + vector similarity, fused with RRF), expands synonyms, and re-ranks through the graph's spectral structure. (Opt-in MMR diversity reranking is available on search_memory and cross_search.)
  3. Route — with the namespace omitted, recall auto-routes across expert namespaces to find knowledge you didn't know where to look for.
  4. Evolve — background services run the physics: spectral decay fades weakly-connected memories (archiving the weakest), sleep consolidation promotes well-connected STM to LTM, and auto-link densifies the graph.

Retrieval itself is a nine-stage pipeline — candidate generation, keyword rescue, fusion, diversity, and spectral re-ranking:

See It in Action

The memory graph consolidating in real time — short-term (amber) memories cluster and promote to long-term (blue) during a sleep cycle.

The built-in D3.js graph viewer lets you explore your own memory graph interactively. Generate a snapshot from any AI assistant, then open the viewer:```
get_graph_snapshot → save the JSON → open visualization/memory-graph.html


**Viewer features:**
- **Force-directed layout** — related memories cluster together, typed edges (elaborates, contradicts, depends_on, …) shown in distinct neon colors
- **Lifecycle colors** — STM nodes amber, LTM nodes blue; cluster summaries marked with a dashed ring
- **Convex-hull cluster overlays** — cluster membership visible at a glance
- **Search & highlight** — type in the search bar to instantly dim non-matching nodes and pulse-highlight matches in gold; `‹ ›` buttons or `Enter / Shift+Enter` to cycle through results
- **Zoom / pan / rotate** — `+` / `−` / `⊡` buttons; scroll to zoom; right-click drag to rotate the whole graph
- **Fractal density overlay** — zooms out reveal a quadtree density map color-coded by lifecycle state
- **Connected-only filter** — hide isolated nodes to focus on the linked knowledge graph
- **Drag-and-drop JSON loading** — drop a snapshot file directly onto the viewer

The snapshot file is not committed (it's personal memory data). Generate a fresh one any time with `get_graph_snapshot`.

## Quickstart

**Existing 2.0.0 installation?** Follow the safe upgrade procedure
before updating: default data in the old version directory must be backed up and migrated first.
The 2.1 server uses a durable user data directory; existing explicit paths are preserved.```powershell
# Windows — clones, builds, and wires up your AI assistant automatically
irm https://raw.githubusercontent.com/wyckit/mcp-engram-memory/main/setup.ps1 | iex
``````bash
# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/wyckit/mcp-engram-memory/main/setup.sh | bash

> The embedding model (bge-micro-v2) ships inside the package — it is fetched from Hugging Face at
> build time, checksum-verified, and bundled, so installing the tool needs no model download and the
> server makes no network call to start.

Other install options (manual clone · Docker · NuGet)

Manual clone```bash
git clone https://github.com/wyckit/mcp-engram-memory.git
cd mcp-engram-memory
dotnet publish src/McpEngramMemory/McpEngramMemory.csproj -c Release -f net8.0 -p:TargetFrameworks=net8.0 -o .engram/server


Add to your MCP client config:```json
{
  "mcpServers": {
    "engram-memory": {
      "command": "dotnet",
      "args": ["/path/to/mcp-engram-memory/.engram/server/McpEngramMemory.dll"],
      "env": { "MEMORY_TOOL_PROFILE": "minimal" }
    }
  }
}

Docker```bash
docker build -t mcp-engram-memory .
docker run -i -v memory-data:/app/data mcp-engram-memory


**NuGet library** (embed the engine in your own .NET app)```bash
dotnet add package McpEngramMemory.Core --version 2.1.0

See examples/ for ready-to-use config files.

At a Glance

Metric Value
Version 2.1.0 (compatible with 2.0 APIs)
MCP tools 63 (profiles: 17 / 39 / 63)
Isolation Tenant-partitioned across storage, graph, clusters, lifecycle, diffusion, synthesis, and snapshots
Retrieval Hybrid BM25 + vector with synonym expansion, cascade retrieval, MMR diversity, auto-PRF
Embedding bge-micro-v2 (384-dim, ONNX, MIT license, runs locally, concurrent inference)
Best recall 0.792 realworld dataset, 0.771 scale dataset (hybrid mode)
Search latency ~2.7 ms production, ~0.04 ms benchmark
Storage JSON (default) or SQLite (WAL mode)
Frameworks net8.0, net9.0, net10.0
Tests Multi-target xUnit suite across net8.0, net9.0, and net10.0
CI/CD GitHub Actions: build + test on push, nightly MSA benchmarks

Tool Profiles

Engram exposes a tunable tool surface. Start on minimal — three headline verbs (remember, recall, reflect) plus admin and multi-agent — and widen only if you need the advanced subsystems. Control it with MEMORY_TOOL_PROFILE:

Profile Tools What's included
minimal 17 Core CRUD + composite + admin + multi-agent — recommended starting point (default)
standard 39 Adds graph (+auto-link), lifecycle (+consolidation), clustering, intelligence, memory-diffusion kernel, spectral retrieval
full 63 Everything including governed knowledge promotion, expert routing, debate, synthesis, benchmarks

MCP Tools (63)

Group Tools Description
Core Memory store_memory, store_batch, search_memory, delete_memory Vector CRUD with namespace isolation, batch import, and lifecycle-aware search
Composite remember, recall (with spectralMode), reflect, get_context_block High-level wrappers with auto-dedup, auto-linking, expert routing, context assembly, and graph-aware spectral re-ranking on recall (default auto)
Knowledge Graph link_memories, unlink_memories, get_neighbors, traverse_graph Directed graph with 7 relation types and multi-hop BFS; similarity-based auto-link densification runs as a 6-hour background sweep
Clustering create_cluster, update_cluster, store_cluster_summary, get_cluster, list_clusters Semantic grouping with auto-computed centroids
Lifecycle promote_memory, memory_feedback, deep_recall, configure_decay State transitions (STM/LTM/archived) and per-namespace decay configuration; spectral decay diffusion and sleep consolidation run automatically as background services
Memory Diffusion compute_diffusion_basis, diffusion_stats, invalidate_diffusion, spectral_recall Graph-Laplacian eigenbasis primitive shared by decay, consolidation, and retrieval; standalone graph-aware retrieval
Intelligence detect_duplicates, find_contradictions, merge_memories, uncollapse_cluster, list_collapse_history Dedup, contradiction detection, merge, collapse reversal
Expert Routing dispatch_task, create_expert, get_domain_tree, link_to_parent HMoE semantic routing with 3-level domain tree
Multi-Agent cross_search, share_namespace, unshare_namespace, list_shared, whoami Namespace sharing, permissions, cross-namespace RRF search
Debate consult_expert_panel, map_debate_graph, resolve_debate Multi-perspective analysis with debate tracking
Synthesis synthesize_memories Map-reduce synthesis via a local SLM served by Ollama. For fully in-process generation, embed McpEngramMemory.Core and add the optional McpEngramMemory.Synthesis.Onnx package
Accretion get_pending_collapses, collapse_cluster, dismiss_collapse DBSCAN cluster detection and two-phase summarization (the density scan runs as a 30-min background sweep)
Governed Learning promote_knowledge Full-profile adapter for the Teacher → deterministic Verifier → Constitution receipt → atomic governed-store promotion path
Admin get_memory, cognitive_stats, engram_status, purge_debates Inspection, system-wide statistics, background-worker health, and stale debate-namespace cleanup
Maintenance rebuild_embeddings, compression_stats Re-embed entries and storage diagnostics
Benchmarks run_benchmark, run_agent_outcome_benchmark, run_live_agent_outcome_benchmark, compare_live_agent_outcome_artifacts, check_for_regression, get_metrics, reset_metrics, run_mrcr_benchmark, compare_mrcr_artifacts IR quality validation, proxy and live memory-condition benchmarking, artifact diffing, CI regression gating, latency/throughput metrics, and MRCR v2 long-context A/B
Visualization get_graph_snapshot Memory-graph JSON snapshot (nodes, typed edges, clusters) for the built-in D3 viewer (visualization/memory-graph.html)

Full tool documentation: MCP Tools Reference

The server uses the ModelContextProtocol 2.2.0 SDK with negotiated protocol handling, a global
request-filter pipeline, and explicit read-only/destructive/idempotent/open-world tool metadata.
SDK package version and negotiated MCP protocol revision are not the same thing.

Architecture

Layer Stability Components
Core Stable Storage, Embeddings, Retrieval, Lifecycle, Graph
Advanced Stable Clustering, Multi-Agent Sharing, Intelligence
Governed Core Maturing Constitution, Knowledge, Provenance, Learning, Planning, Semantic Assets
Orchestration Maturing Expert Routing (HMoE), Debate, Benchmarks

Governed Core vs. MCP tools

The governed substrate lives in McpEngramMemory.Core: immutable Root/overlay Constitutions,
versioned Knowledge and append-only Provenance, quarantined Teacher proposals, deterministic-first
verification, atomic reference promotion, authorization-first retrieval planning, context manifests,
profiles/loadouts, and Skill/Documentation/CodeGraph/Curriculum contracts.

The 63 MCP tools include the full-profile promote_knowledge adapter, which executes the
Teacher → deterministic Verifier → Constitution receipt → atomic governed-store path. Context and
other asset-management tools remain Core APIs for embedded hosts. Every tool call also passes through
the global Constitution pre/post filter. Skill execution is
delegated to a host-provided ISkillSandbox; Engram does not run arbitrary Skill code.

Identity is also host-owned. IPrincipalContext carries tenant and principal claims. The stdio
server bootstraps it from MEMORY_TENANT_ID and AGENT_ID, which are process configuration rather
than authentication. Empty tenant + default agent is explicit legacy-unisolated mode.

Multi-tenancy is complete and, as of 2.0, mandatory at the API boundary. Memory CRUD and search,
the cognitive graph, clusters, lifecycle, collapse history, diffusion/spectral retrieval,
intelligence, maintenance, synthesis, and visualization are all tenant-partitioned: a tenant sees
and mutates only its own data, and graph edges never cross tenants (cross-namespace association
within a tenant is preserved). Core's retrieval and scoping APIs take tenantId as a required
argument, so scope is a decision the compiler makes you state rather than a default you can forget —
"" remains a valid answer, and the legacy partition it names is a real dataset, so state it
deliberately. Legacy empty-tenant deployments are byte-for-byte unchanged. See
Cognitive Constitution and Governed Core and Security.

AI Assistant Setup

Model execution belongs to the host harness, not the Engram server: expert profiles route to persona-backed memory namespaces, while the host model reasons over the retrieved evidence. See Model and Reasoning Routing for canonical task tiers, the current Codex model mapping, reasoning escalation rules, and ready-to-use profiles.

Copy the reference harness for your tool — each includes recall/store/routing patterns:

Tool Harness File MCP Config
Claude Code examples/CLAUDE.md → ~/.claude/CLAUDE.md examples/claude-code.json
GitHub Copilot examples/copilot-instructions.md → .github/ examples/vscode-copilot.json
Google Gemini GEMINI.md → workspace root Gemini CLI config
OpenAI Codex examples/AGENTS.md → project root Codex config

> Claude Code users: Route memory sub-agents to Sonnet (model: "sonnet") and utility sub-agents to Haiku (model: "haiku") to maximize your subscription. See the harness for details.

For step-by-step setup prompts, see AI Assistant Setup.

Cost-Optimized Usage (Claude Code)

Tier Model What runs here
Main thread Opus Coding, architecture, reasoning, decisions
Memory sub-agents Sonnet (model: "sonnet") All engram MCP tool calls: search, store, dispatch, link, merge
Utility sub-agents Haiku (model: "haiku") Codebase exploration, file searches, grep research, simple lookups

Opus thinks, Sonnet remembers, Haiku explores.

Environment Variables

Variable Default Description
MEMORY_TOOL_PROFILE minimal Tool profile: minimal (17), standard (39), full (63)
AGENT_ID default Host-supplied agent identity for namespace sharing. The default is explicit legacy-unisolated compatibility mode, not authentication.
MEMORY_TENANT_ID empty Host-supplied tenant partition. Do not accept this value from model/tool arguments. Empty selects the legacy partition.
MEMORY_STORAGE json Storage backend: json, sqlite, or sqlserver
MEMORY_DATA_PATH User-local app data / engram-memory Durable server data root; see migration instructions
MEMORY_SQLITE_PATH /memory.db SQLite database path (when MEMORY_STORAGE=sqlite); explicit overrides are preserved
MEMORY_SQLSERVER_CONNECTION required SQL Server connection string (when MEMORY_STORAGE=sqlserver)
MEMORY_SQLSERVER_SCHEMA dbo SQL Server schema name (when MEMORY_STORAGE=sqlserver)
MEMORY_MAX_NAMESPACE_SIZE unlimited Max entries per namespace
MEMORY_MAX_TOTAL_COUNT unlimited Max total entries across all namespaces

NuGet / GitHub Packages

The server ships as a dotnet global tool, and the core engine as a library you can embed in your
own .NET applications.

Server (global tool)```bash
dotnet tool install --global McpEngramMemory --version 2.1.0
engram-memory


**Core engine (library)**```bash
# nuget.org
dotnet add package McpEngramMemory.Core --version 2.1.0

# GitHub Packages
dotnet add package McpEngramMemory.Core --version 2.1.0 \
  --source https://nuget.pkg.github.com/wyckit/index.json

Optional: in-process synthesis

synthesize_memories generates through an ITextGenerator. The server ships one implementation —
OllamaClient, talking to a local Ollama daemon. If you want generation fully in-process with no
daemon, add the optional ONNX backend when embedding the library:```bash
dotnet add package McpEngramMemory.Synthesis.Onnx --version 2.1.0
``````csharp
using McpEngramMemory.Core.Services.Synthesis;

ITextGenerator generator = new OnnxGenAiTextGenerator(modelDir); // stage a model first


It lives in its own package because ONNX Runtime GenAI ships native binaries for every platform it
supports — roughly 500 MB. Keeping it separate means neither the `McpEngramMemory` tool nor a plain
`McpEngramMemory.Core` install pays that cost. Stage a model with
`scripts/fetch-synthesis-model.ps1`.

> The `McpEngramMemory` **server** does not support `SYNTHESIS_BACKEND=onnx`; it fails at startup
> with a pointer to this package. In-process synthesis is for hosts embedding the Core library.```csharp
using McpEngramMemory.Core.Models;
using McpEngramMemory.Core.Services;
using McpEngramMemory.Core.Services.Storage;

var persistence = new PersistenceManager();
var embedding = new OnnxEmbeddingService();
var index = new CognitiveIndex(persistence);

// "" is the legacy (single-tenant) partition. Pass a real tenant id to isolate.
const string tenant = "";

// Store
var vector = embedding.Embed("The capital of France is Paris");
var entry = new CognitiveEntry(
    "fact-1", vector, "default", "The capital of France is Paris", "facts", tenantId: tenant);
index.Upsert(entry);

// Search — tenantId is required as of 2.0
var results = index.Search(embedding.Embed("French capital"), "default", tenant, k: 5);

Documentation

Doc Description
First 5 Minutes Store, close, recall — the whole loop
Cheat Sheet One-page quick reference
MCP Tools Reference Full documentation for all 63 tools
Architecture System design, retrieval pipeline, data flow
Cognitive Constitution Governed Core boundary, knowledge/provenance, learning, planning, assets, persistence, and current tenant limits
Services All services with descriptions
Internals Retrieval, quantization, persistence deep dive
Project Structure File tree and module organization
AI Assistant Setup Step-by-step setup prompts for each tool
Sample Prompts Power prompts and usage patterns
Benchmarks IR quality results and mode selection guide
MRCR v2 Benchmark Long-context A/B (full context vs. hybrid retrieval) via Claude CLI subscription
Testing Test coverage breakdown and current CI coverage
2.1.0 Release Notes Recall, reliability, safe upgrades and validation limits
2.0.0 Release Notes What changed in 2.0, why it is major, and how to migrate an embedding host
Tenant Isolation Design Partitioning model, guarantees, and the 2.0 required-tenantId boundary
Changelog Full release history

Build & Test```bash

cd mcp-engram-memory
dotnet build
dotnet test # full suite, including slower MSA benchmark cases
```

Tech Stack

  • .NET 8/9/10, C#
  • ModelContextProtocol 2.2.0
  • FastBertTokenizer 1.0.28
  • Microsoft.ML.OnnxRuntime 1.29.0
  • bge-micro-v2 ONNX (384-dim, MIT license)
  • Microsoft.Data.Sqlite 10.0.11
  • xUnit v3 (tests)

License

MIT

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
MCP Vector Memory 怎么安装?

在客户端按下面的安装命令接入:docker run -i -v memory-data:/app/data mcp-engram-memory。装完在客户端配置里引用同一个包或端点。

MCP Vector Memory 怎么在 Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MCP Vector Memory 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP Vector Memory 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

MCP Vector Memory 支持哪些客户端?

资料标注支持 Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

MCP Vector Memory 能提供哪些能力?

资料显示约 61 个工具;能力标签包括 AI记忆、多代理协作、C#、Claude。具体工具清单以官方文档为准。

MCP Vector Memory 需要什么运行环境?

运行时为 Docker;属于本地进程,需要在本机装好运行环境。

MCP Vector Memory 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。