Read-only local-first MCP server for private Markdown, PDF, and Tika-backed search on Windows.
Read-only local-first MCP server for private Markdown, PDF, and Tika-backed search on Windows. That is what the omniclip rag mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Caelune builds searchable indexes from knowledge you already keep on your own computer. It combines exact-text retrieval, structural signals, semantic vector search, optional reranking, and source-aware context assembly.
The server publishes 8 tools. What each one is for:
Local — first storage** — indexes, configuration, models, logs, and Runtime payloads stay under the active local data rootEvent — driven live watch** — reacts to real file changes, waits for the configurable quiet period, and performs incremental updates in disposable workerResource — aware execution** — Auto mode prefers a usable NVIDIA CUDA path and falls back safely when Windows Commit, physical memory, or GPU memory isRead — only MCP access** — MCP clients can inspect readiness and search, but cannot build indexes, delete data, or change configurationThird — party AI clients and anything you paste into them remain subject to their own privacy policiesWIN-EXE — Normal Windows desktop use: configure, build, watch, search, and review resultsMCP-...-win64.zip — Manual stdio setup for an MCP clientTopic — GuideSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. OmniClip RAG's toolset — Local, Event, Resource and 5 more — is a fair guide to whether it matches your workflow. It is maintained by EllisMorrow; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Local | first storage** — indexes, configuration, models, logs, and Runtime payloads stay under the active local data root. |
| Event | driven live watch** — reacts to real file changes, waits for the configurable quiet period, and performs incremental updates in disposable worker processes. |
| Resource | aware execution** — Auto mode prefers a usable NVIDIA CUDA path and falls back safely when Windows Commit, physical memory, or GPU memory is insufficient. |
| Read | only MCP access** — MCP clients can inspect readiness and search, but cannot build indexes, delete data, or change configuration. |
| Third | party AI clients and anything you paste into them remain subject to their own privacy policies. |
| WIN-EXE | Normal Windows desktop use: configure, build, watch, search, and review results |
| MCP-...-win64.zip | Manual stdio setup for an MCP client |
| Topic | Guide |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.