MCP Local Memory 02349d78

MCP搜索检索

提供方 SoyamDarshan

搜索检索 stdio · 本地进程 无需鉴权 社区 / 第三方 Cursor
查看接入方式

一个基于本地运行的RAG(检索增强生成)服务器,用于在代码编辑器中存储和查询文档,并通过本地LLM(如Ollama)进行检索增强生成。

一句话选型结论

按资料字段整理

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

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

工具与能力

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

能力标签

支持客户端

适用场景

RAGPython本地部署本地LLM文档存储语义搜索向量数据库

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
python -m venv venv

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

  1. 1
    准备运行环境

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
联网搜索取证

让模型查最新资料并给出出处。

资料聚合

把一个主题的网页、文档集中抓回来整理。

情报与竞品检索

按关键词持续检索行业动态和竞品信息。

选择建议

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

值得选的地方

  • 资料标注 5 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Cursor,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

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

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Local Memory 02349d78当前 5 stdio · 本地进程 本地部署 有 2026-05-17
Brave Search 433812ff 2 未标注 未标注 无 2026-05-17
Sequentialthinking 1 SSE · 服务端推送 远程部署 有 2026-05-18
Baidu Netdisk 未标注 未标注 未标注 无 2026-05-17
ragflow 未标注 stdio · 本地进程 本地部署 有 2026-04-11
mindsdb (430e18) 未标注 未标注 未标注 有 2026-05-17

服务器档案

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

详细介绍

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

mcp-local-memory

Local RAG MCP server for code editors: store and query documents in a vector DB (ChromaDB + Ollama embeddings), then answer questions with retrieval-augmented generation via a local LLM (Ollama).

Features

  • store_document — Store text with a title; long content is chunked automatically.
  • query_documents — Semantic search with optional metadata filters and distance threshold.
  • ask_rag — Retrieve relevant chunks and generate an answer using only that context (Ollama).
  • list_documents / delete_document — Inspect and remove stored items.
  • export_documents / import_documents / import_from_file — Export stored chunks (ID, text, metadata) as JSON and import them into another setup (either by passing JSON or reading from a local file).

All embeddings and (optionally) generation run locally via Ollama; no data leaves your machine.

Requirements

  • Python 3.10+
  • Ollama running with nomic-embed-text (embeddings) and a chat model (e.g. llama3)

Setup```bash

python -m venv venv
source venv/bin/activate # or venv\Scripts\activate on Windows
pip install -r requirements.txt


Optional: copy `.env.example` to `.env` and set:

- `OLLAMA_HOST` (default: `http://localhost:11434`)
- `OLLAMA_MODEL` (default: `llama3`)
- `CHROMA_PERSIST_DIR` (default: `./chroma_db`)
- `COLLECTION_NAME` (default: `mcp_docs`)
- `EMBEDDING_MODEL` (default: `nomic-embed-text`); for a custom DB backend, `VECTOR_DB_PROVIDER` (dotted path to your class)

## Run as MCP server (stdio)```bash
python server.py

Using Docker with Cursor

Docker gives you a single, reproducible environment and avoids venv/path issues (e.g. Cursor using the wrong Python). Cursor talks to the MCP server over stdio by starting the container itself.

1. Prerequisites

  • Docker installed and running.
  • Ollama running on your host with nomic-embed-text and a chat model (e.g. llama3).

2. Build the image

From the project root:```bash
docker build -t mcp-local-memory .


If you see **"driver not connecting"**, use the legacy builder: `DOCKER_BUILDKIT=0 docker build -t mcp-local-memory .`

**Use in this project first:** This repo’s `.cursor/mcp.json` is already set to run `mcp-local-memory:latest` with ChromaDB data in `./chroma_db` (project directory). After building the image, restart Cursor and open this project; the MCP server will use the container.

**Configurable when running the container:** Pass env with `-e` in the Docker `args`. Defaults: `OLLAMA_HOST`, `OLLAMA_MODEL` (chat, default `llama3`), `EMBEDDING_MODEL` (embeddings, default `nomic-embed-text`), `CHROMA_PERSIST_DIR`, `COLLECTION_NAME`. Use whatever embedding model your Ollama instance supports (e.g. `nomic-embed-text`, `mxbai-embed-large`).

#### 3. Add the server to Cursor (other projects or global)

Add an MCP server entry so Cursor starts the container and uses it for tools.

**Where to put the config**

- **This project only:** create or edit `.cursor/mcp.json` in this repo.
- **All projects:** edit your user MCP config:
  - **Linux:** `~/.cursor/mcp.json` or `~/.config/cursor/mcp-config.json`
  - **macOS:** `~/.cursor/mcp-config.json`
  - **Windows:** `%APPDATA%\Cursor\mcp-config.json`

**Config (Linux)**

Add this inside the existing `"mcpServers"` object (or create it):```json
"local-rag-memory": {
  "command": "docker",
  "args": [
    "run",
    "--rm",
    "-i",
    "--add-host=host.docker.internal:host-gateway",
    "-e", "OLLAMA_HOST=http://host.docker.internal:11434",
    "-v", "/absolute/path/to/local-rag-data:/app/chroma_db",
    "mcp-local-memory"
  ],
  "env": {}
}

Replace /absolute/path/to/local-rag-data with any path where you want ChromaDB data to persist on your machine. To use a different Ollama embedding model, add e.g. "-e", "EMBEDDING_MODEL=your-model" to args (default is nomic-embed-text). Same for OLLAMA_MODEL (chat model for ask_rag, default llama3).

Config (macOS / Windows with Docker Desktop)

Use the same structure but omit the "--add-host=host.docker.internal:host-gateway" entry from args (Docker Desktop already resolves host.docker.internal):json "local-rag-memory": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "OLLAMA_HOST=http://host.docker.internal:11434", "-v", "/path/on/your/machine/local-rag-data:/app/chroma_db", "mcp-local-memory" ], "env": {} }

On Windows use a path like C:\Users\You\.cursor\local-rag-data; on macOS use e.g. $HOME/.cursor/local-rag-data (expand it to a full path in the JSON).

4. Restart Cursor

Restart Cursor (or Developer: Reload Window) so it picks up the new MCP server.

5. Verify

In Cursor chat, ask: “What MCP tools do you have?” You should see store_document, query_documents, ask_rag, list_documents, and delete_document. You can then say e.g. “Store a note titled Test with content Hello” and “Query for Test” to confirm the server and Ollama are working.

To export data for use in another setup, call export_documents in Cursor chat (optionally with a metadata_filter JSON string). Copy the JSON and import it into another instance by replaying store_document calls, calling import_documents(documents_json=...), or writing a small script that iterates over the exported list and calls db.store_document for each entry. For environments that can't pass arguments, save the JSON to rag_import.json (or the path set in IMPORT_PATH) and call the no-arg import_from_file MCP tool to ingest it.

Troubleshooting

  • “driver not connecting” when running docker build: The Docker daemon isn’t responding. Restart Docker Desktop (or run sudo service docker start if using the engine in WSL). Ensure WSL integration is enabled in Docker Desktop → Settings → Resources → WSL Integration. Try docker context use default and run the build again.
  • “No such file or directory” / container exits: Ensure the image was built: docker build -t mcp-local-memory .
  • Ollama errors in tools: Ollama must be running on the host; the container reaches it at http://host.docker.internal:11434. On Linux, the --add-host=host.docker.internal:host-gateway arg is required.
  • Data not persisting: The -v path must be a directory on your host; create it if needed (e.g. mkdir -p ~/.cursor/local-rag-data).

For non-Docker Cursor setup (venv, UI), see RAG_ANALYSIS.md.

Custom implementations and seeds

The app is built so you can plug in your own data and, if you want, your own backend.

Same config everywhere

All settings and the DB are centralized in config.py (and .env). The MCP server and any script you add use the same store if they use the same env:

  • OLLAMA_HOST, OLLAMA_MODEL, CHROMA_PERSIST_DIR, COLLECTION_NAME, EMBEDDING_MODEL

So custom scripts and the server stay in sync without hardcoding paths or collection names.

Custom seed scripts

You can add your own seed scripts (e.g. my_seed_script.py) that write into the same RAG store the MCP server uses:

  1. Use the shared config and DB:```python
    import uuid
    import config

db = config.get_db()
```

  1. Call store_document with your own (title, content) pairs and optional metadata (e.g. project, type).

  2. Run from the project root (so config and db resolve):bash ./venv/bin/python my_seed_script.py

Define your own list of (title, content) pairs (and optional metadata), then call db.store_document for each. To keep data separate (e.g. one collection per project), set COLLECTION_NAME (and optionally CHROMA_PERSIST_DIR) in .env or in the environment before running your seed or the server.

Custom VectorDB backend

If you want to use a different store (e.g. another vector DB), you can plug it in without changing the MCP server:

  1. Implement the VectorDB interface from db.vector_db: store_document, query_documents, list_documents, delete_document with the same signatures.

  2. Point config at your class via env:bash VECTOR_DB_PROVIDER=my_package.my_db.MyProvider
    Your class will be instantiated with: collection_name, persist_directory, ollama_base_url, embedding_model (same as ChromaProvider). If your backend needs different args, wrap it in a thin adapter that accepts these and maps them.

  3. Run the server (or seeds) as usual; they will use config.get_db() and thus your provider.

This way the MCP server stays the same and users can connect their own implementation freely.

License

MIT

Security

See SECURITY.md for a privacy/sanitization checklist before committing or releasing.

常见问题

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

在客户端按下面的安装命令接入:python -m venv venv。装完在客户端配置里引用同一个包或端点。

MCP Local Memory 02349d78 怎么在 Cursor 里配置?

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

MCP Local Memory 02349d78 收费吗?

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

MCP Local Memory 02349d78 需要 API Key 吗?

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

MCP Local Memory 02349d78 支持哪些客户端?

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

MCP Local Memory 02349d78 能提供哪些能力?

资料显示约 5 个工具;能力标签包括 RAG、本地LLM、Python、Cursor、搜索。具体工具清单以官方文档为准。

MCP Local Memory 02349d78 需要什么运行环境?

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

MCP Local Memory 02349d78 是本地还是远程?

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

热门专题

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

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