Skip to main content

Locus

Your files, your machine, the MCP clients you already use.

Locus indexes folders you choose on your own computer and gives MCP clients that can start a local server (tested: Claude Desktop, Claude Code and Cursor) a semantic search tool over them. Every result carries the file path, so the assistant can cite its sources.

The package is locusfiles; the command it installs is locus.

Install

You need Python 3.11 or newer. Install with pipx or uv, which put locus in its own environment. These commands work once locusfiles is published on PyPI (first upload planned for 2026-10-01):

# On-device embeddings, no account (downloads PyTorch, about 1-2 GB):
pipx install "locusfiles[local]"
# or
uv tool install --python 3.12 "locusfiles[local]"

# A Locus plan (managed embeddings, remote connection), no PyTorch:
pipx install "locusfiles[relay]"

Other extras: voyage or openai to embed with your own provider key.

macOS and Linux are tested. Windows is not yet verified.

export LOCUS_EMBEDDER=local            # or managed (with LOCUS_API_KEY), voyage, openai
locus doctor                           # checks Python, packages, settings and the embedder
locus index ~/Documents/notes --prune  # parse, chunk, embed and index a folder
locus query "what did I decide about pricing" -k 5

Then connect your AI assistant: it runs locus serve (MCP over stdio). Setup steps for each client are on the Locus website's Connect page (/docs/connect).

What leaves your computer

  • Local: Indexing and embeddings run on your computer. When your AI assistant searches, the matching excerpts go to that assistant, as they would if you pasted them in.
  • Your own key: Chunk text goes straight from your computer to the embedding provider you chose, under your own account.
  • Managed: On managed plans, chunk text passes through Locus's relay to Voyage AI to be embedded. We don't store it; we keep only usage counts.
  • Remote: When you reach your computer from another device or a web AI app, your question and the matching excerpts travel through Locus's relay (Vercel and Supabase) to and from your computer. They are encrypted in transit and we don't store them.
  • In every mode: Your raw files are never uploaded to Locus.

Indexes live in ~/.locus (set LOCUS_DATA_DIR to move them). Settings are environment variables, or a .env file in the directory you run locus from or one of its parents.

Metadata

Release files for locusfiles 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for locusfiles 0.1.0
File Size Uploaded
locusfiles-0.1.0.tar.gz 87.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for locusfiles 0.1.0
File Interpreter ABI Platform
locusfiles-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 191.1 kB

Release files / locusfiles-0.1.0.tar.gz

Download URL locusfiles-0.1.0.tar.gz
Size 87.9 kB
Tags Source
SHA-256 checksum
How to use checksums
0f67b570125736d52672365a5b9c0b21dffc7dfffe62224b21598195c82ed0f2
BLAKE2b-256 checksum
How to use checksums
a2c60e5d035ee3e0f309674c98cd3eede775b7b576b41033bc92a5fc5f6130f8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.

Transparency log

Release files / locusfiles-0.1.0-py3-none-any.whl

Download URL locusfiles-0.1.0-py3-none-any.whl
Size 103.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b2fa16cb585f9ac510679ded9ad46e87e720217f01a43227e7e7659d61ec4d38
BLAKE2b-256 checksum
How to use checksums
64d7a722f996473a81b583bc91263b975a3ce740e69d8d2d9e3b9a956b575af2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.3

2 release files

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page