mcpField
C
cortex

cortex

Local
github.com/VBlackJackMemory & Knowledge1Updated 1w ago

About cortex

Cortex is a local MCP server for semantic search across a document knowledge base, for people using Claude, Codex, Gemini, and other MCP clients. It indexes content locally and supports multilingual retrieval in French and English.

Key features

  1. 01Local document indexing
  2. 02French and English semantic search
  3. 03Optional hybrid and reranked retrieval
  4. 04Incremental synchronization
  5. 05MCP tools for search, sync, and freshness

Use cases

  1. 01Find relevant passages in local documents
  2. 02Search a knowledge base from an MCP client
  3. 03Refresh an index after documents change
  4. 04Check source and index freshness

MCP support

Cortex exposes search, synchronization, section listing, and freshness tools to MCP clients. Content is indexed locally; requested chunks may be passed to the connected model according to the client's policy.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"vblackjack-cortex": {
"command": "uvx",
"args": [
"cortex-local-rag"
],
"env": {
"CORTEX_KB_PATH": "<CORTEX_KB_PATH>"
}
}
}
}
Run commanduvx cortex-local-rag
Environment variables to set
CORTEX_KB_PATHAbsolute path to the local knowledge base Cortex indexes and serves.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypicortex-local-rag2026.1021.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Cortex - RAG MCP for a knowledge base

English | Français

Cortex is an MCP (Model Context Protocol) server that exposes semantic search over a local knowledge base. It lets Claude, Codex and Gemini find the right passage in your documents without wasting their context window. Search is semantic (by meaning, not keyword), in French and in English. Cortex processes and indexes the knowledge base locally without sending its content; the MCP client may still pass requested chunks to its model under its own policy. The optional Confluence writer only downloads explicitly allowlisted spaces; the generated Markdown, vector index, and lexical index remain local.

Starting with 2026.0906.01, Companion offers a guided home screen, operation history and Confluence setup from one page or space link. Connection and measured scope confirmation stay in the flow; successful collection is followed by indexing. Use the combined installer to keep Cortex and Companion compatible.

Since 2026.0909.02, Confluence updates preserve the served generation when subtree enumeration fails and apply changed target/classification settings on retry. Search uses multilingual vector retrieval by default; CLI and MCP callers can explicitly select hybrid or reranked search. The first successful collection after upgrading regenerates older publication revisions, and the following sync removes obsolete index entries.

Guided document updates (2026.0909.00)

Companion brings local documents and Confluence together in My sources, with one Update my documents action. Search previews are resizable, large page trees render visible rows, and cancelling review preparation keeps the draft. Readiness now follows the saved document folder and configuration, including after restart. Run one document update after upgrading to establish this evidence for older indexes. See the release notes.

Measured scope without enumerating the space (2026.0907.00)

Adding a Confluence source measures its page, subtree and whole-space scopes with one indexed count each instead of reading the space page by page. On a 5916-page space that measurement took 3 min 19 s, past the timeout of every graphical caller, so Companion showed nothing at all. It now answers in about a second, and the emitted contract is unchanged.

Two whole-space numbers shift by one as a result: the resolved page is no longer folded into the space total, and a space with no visible page reports zero rather than one. A deployment whose search endpoint returns no total cannot measure a scope and reports that as a permanent failure instead of a retryable one. See the contracts.

Paired Companion 2026.0907.00 restores the contrast of the scope window, whose options were drawn in the system text colour, and stops reporting a timeout as a connection failure or advising a delay increase that silently reverts.

Source management in Companion (2026.0906.02)

The workflow includes search, remote page trees, impact review, evidence-based readiness, save-and-update, last-removal undo and recovery actions. See the contracts.

Paired version 2026.0906.02 provides visible My sources cards, a prefilled selection editor, confirmed page/space removal and browser links to originals. Removal only changes Cortex tracking; search reflects it after successful collection and indexing.

Removing the final source explicitly writes spaces = [] in a schema v2 or v3 configuration. This intentional empty allowlist permits an empty publication with tombstones for prior documents. An absent spaces key remains incomplete configuration and collection is refused. Connection and credential validation and publication safeguards still apply. Both updated components are required; this capability is absent from the installed 2026.0906.01 release.

Installation

Windows, no Python (recommended)

The simplest path: one installer for Cortex, Cortex Companion, the windowless Confluence converter, and the offline models. No separate Python or .NET runtime is required.

  1. Download Cortex-Setup.exe and SHA256SUMS from the latest release.
  2. Before running the unsigned installer, calculate its digest with Get-FileHash .\Cortex-Setup.exe -Algorithm SHA256 in PowerShell and verify that it exactly matches the Cortex-Setup.exe line in SHA256SUMS.
  3. Double-click only after that check. If SmartScreen still warns, select More info, then Run anyway.
  4. Choose the folder that holds your documents, keep Index everything in this folder, and finish. Cortex Companion opens when installation completes. Indexing only starts when you request synchronization in Companion.
  5. In Companion, open Settings and verify the knowledge-base folder. The Cortex executable installed with Companion is detected automatically.
  6. Drop your documents in that folder, open Local database, then select Synchronize local documents.
  7. Restart your AI application: Cortex shows up there as an MCP server.

Companion then lets you synchronize, schedule, diagnose, and configure Cortex without a terminal. Details, silent mode and reinstall: Windows install.

Standalone archives (Windows x64, macOS Apple Silicon, Linux x64)

Every release also ships one ZIP archive per platform. It unpacks to a cortex/ folder holding the cortex or cortex.exe executable (MCP server + CLI, no Python), its runtime, and the licenses for every embedded dependency; keep the folder whole. See Standalone distribution.

From PyPI (Python, advanced)
py -m pip install --upgrade cortex-local-rag
cortex setup

This path installs the CLI and MCP server, but not Cortex Companion. The model is downloaded on first use if its cache is empty.

From source (development)
:: From the folder where you cloned Cortex
install.bat

install.bat and sync.bat are the development path for a source checkout, not a supported end-user installation: install.bat installs the unlocked dependencies from requirements.txt, and sync.bat indexes the folder section by section without the Confluence documents. To use Cortex, install Cortex-Setup.exe or a standalone archive instead. Details: Setup.

How it works

Documents folder (.md, .pdf)       Optional Confluence writer (REST)
      |                                      |
      |                              current Markdown generation
      +------------------+-------------------+
                         |
                         v
  cortex sync           <- Split, hash, vectorize, update FTS5
                         |
                         v
  %LOCALAPPDATA%\Cortex\  <- ChromaDB + lexical.db
      |
      v
  cortex serve          <- MCP server (FastMCP)
      |
      v
  MCP clients           <- Claude / Codex / Gemini / Antigravity / LM Studio / Cursor / Windsurf / VS Code

The embedding model is the multilingual ONNX paraphrase-multilingual-MiniLM-L12-v2. The Windows installer bundles it; a source installation or standalone binary downloads it when the local cache is empty.

Two indexing modes

  • Whole folder (default): anything you place in the chosen folder, at the root or in any subfolder, becomes searchable. Nothing to configure.
  • Sections (advanced): limits indexing to named subfolders you can search separately (defaults knowledge, projects, notes).

These modes govern the user-selected document folder. Generated ingestion documents are indexed separately from the current published generation with source_kind=doc and section sources.

Details: Configuration.

The cortex command

The installed package exposes a single command:

SubcommandPurpose
cortex setupConfig + index + client registration in one go (--kb-path, --yes, --no-index, --reset).
cortex serveRuns the MCP server (used by clients).
cortex syncIncremental index synchronization.
cortex searchSearches the index from the console (debugging aid).
cortex ingestionShows source health and whether catch-up is due.
cortex confluenceStores the PAT interactively or runs the allowlisted writer.
cortex configReads or changes configuration through an atomic JSON contract, notably for Companion.
cortex daemonRuns, inspects or stops the shared per-user server used when [server] mode = "shared" (opt-in).
cortex bundleDescribes or verifies an encrypted portable archive.
cortex doctorInstallation diagnostics (read-only).
cortex register / cortex unregisterAdds or removes Cortex from MCP clients.
cortex initCreates the single per-user configuration.
cortex checkVerifies the installation.

cortex --help describes every subcommand and cortex <command> --help describes its options. A prompt-free installation scripts as:

cortex setup --yes --kb-path "D:\Documents\Knowledge"

Exposed MCP tools

ToolDescription
cortex_searchMultilingual vector search by default; optional retrieval_mode (vector, hybrid, rerank). Parameters: query, section, top_k (1-10), source/author filters, and occurred/updated date ranges.
cortex_syncTriggers an incremental sync of the selected folder and, on a full sync, the current published document generation.
cortex_list_sectionsLists included sections and "out of policy" folders.
cortex_freshnessRead-only vault and ingestion freshness summary. Parameters: section (optional), include_entries (false by default).

Documentation

Prerequisites

PathRequirements
Windows installerNo separate Python or .NET runtime. At least ~500 MB of space (applications, model + index).
Standalone archiveNo Python. ~500 MB of space (model + index).
From sourcePython 3.11 to 3.13. ~500 MB of space.
ClientClaude Desktop/Code, Codex, Gemini, Antigravity, LM Studio, Cursor, Windsurf or VS Code (MCP support).

License

Apache 2.0. See LICENSE.

Retrieval validation

See the validation guide for the desktop JSON search contract, the isolated FR/EN relevance corpus, performance measurements and exact paired-commit checks.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.