OmniClip RAG MCP Server

Read-only local-first MCP server for private Markdown, PDF, and Tika-backed search on Windows.

Local serverstdioPython

What is the OmniClip RAG MCP server?

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.

The short version

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.

  • Local-first storage — — indexes, configuration, models, logs, and Runtime payloads stay under the active local data root
  • Markdown and Logseq awareness — — understands Markdown content plus common Logseq properties, block references, and embeds
  • Hybrid retrieval — — combines SQLite FTS5, structure-aware scoring, LanceDB vector search, BAAI/bge-m3, and optional BAAI/bge-reranker-v2-m3
  • PDF and Tika extensions — — maintains separate extension indexes and returns unified results with explicit source labels. The Tika catalog exposes 1,290 format entries; real compatibility still depends on the source file and parser
  • Event-driven live watch — — reacts to real file changes, waits for the configurable quiet period, and performs incremental updates in disposable worker processes
  • Visible query stages — — preparing, lexical recall, semantic recall, fusion, reranking, finalization, and context packing remain visible in the Query Console

The tools it exposes

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 root
  • Event — driven live watch** — reacts to real file changes, waits for the configurable quiet period, and performs incremental updates in disposable worker
  • Resource — aware execution** — Auto mode prefers a usable NVIDIA CUDA path and falls back safely when Windows Commit, physical memory, or GPU memory is
  • 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

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

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.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Localfirst storage** — indexes, configuration, models, logs, and Runtime payloads stay under the active local data root.
Eventdriven live watch** — reacts to real file changes, waits for the configurable quiet period, and performs incremental updates in disposable worker processes.
Resourceaware execution** — Auto mode prefers a usable NVIDIA CUDA path and falls back safely when Windows Commit, physical memory, or GPU memory is insufficient.
Readonly MCP access** — MCP clients can inspect readiness and search, but cannot build indexes, delete data, or change configuration.
Thirdparty AI clients and anything you paste into them remain subject to their own privacy policies.
WIN-EXENormal Windows desktop use: configure, build, watch, search, and review results
MCP-...-win64.zipManual stdio setup for an MCP client
TopicGuide

Example prompts to try

  • Use OmniClip RAG to Local.
  • Use OmniClip RAG to Event.
  • Use OmniClip RAG to Resource.

Frequently asked questions

It connects OmniClip RAG to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (Local, Event, Resource, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with OmniClip RAG directly.