MCP.Market

Locus MCP server

by EDKarlsson·io.github.EDKarlsson/locus·v0.6.2

Hierarchical markdown memory palace for AI agents — structured palace navigation via MCP tools.

A94/100grade A
What users say
No reviews yet
Be the first
Safety scan
A94/100

full report

Adoption
Growing

0 stars39 downloads/wk

Reviews

Write one

Nobody has reviewed Locus yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Locus tools (4, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • memory_list

    List the palace index or the files within a room.

  • memory_read

    Read a file from the palace.

  • memory_search

    Full-text search across the palace (or a sub-path).

  • memory_writewrite action

    Write content to a file within the palace.

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

no findings
  • Code scan19 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 19 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 94/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Locus compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
94/100
higher than 96% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
25%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
39
more than 30% of 12,191 servers with a package

What its tools let an agent do: 3 read · 1 change

Install Locus in Claude Code, Cursor or VS Code

claude mcp add locus -- uvx locus-mcp
Add to Cursor

What the publisher says

From the Locus repository's README, as published. We do not edit it. Read it on GitHub

Locus

<!-- mcp-name: io.github.Nano-Nimbus/locus -->

Hierarchical markdown-based memory system for autonomous AI agents. Each directory is a room (locus) in the palace, containing specific knowledge navigated on demand. Named for the atomic unit of the Method of Loci.

Core idea: Keep context windows small. Load only the room you need, not the whole palace.

How it works

palace/
  INDEX.md                    ← always read first (~50 lines max)
  global/
    toolchain/
      toolchain.md            ← canonical facts about tools
  projects/
    my-project/
      my-project.md           ← room overview + key files
      technical-gotchas.md    ← specialty: issues & resolutions
      sessions/
        2026-03-02.md         ← append-only session log

An agent reads INDEX.md, navigates to the relevant room, and reads only that room. Session logs accumulate until consolidation merges them into canonical files.

See the wiki for full documentation.

Quick start

# Install
pip install locus-mcp
# or: uvx locus-mcp --palace ~/.locus  (no install needed)

# Create a palace from the packaged example
locus init ~/.locus
# Edit ~/.locus/INDEX.md to describe your palace

# Run the MCP server
locus-mcp --palace ~/.locus
# or: LOCUS_PALACE=~/.locus locus-mcp

Installation

MCP server (recommended for MCP-capable clients)

pip install locus-mcp

Or run without installing using uvx:

uvx locus-mcp --palace ~/.locus

Agent skills

The skill files are the one part of Locus written for a specific runtime. The palace convention, the MCP server, and the recall / lint / index CLIs are runtime-neutral and work from anything that can read a file or speak MCP. The skills in skills/claude/ are written and maintained for Claude Code, and that is the only set shipped here. They are plain markdown with YAML frontmatter, so another runtime is welcome to adapt them. Per-runtime copies used to live in skills/codex/ and skills/gemini/; they were removed because keeping three variants honest cost more than it returned.

Install them from a clone:

git clone https://github.com/Nano-Nimbus/locus.git
cd locus
make install-skills            # copies skills/claude/* to ~/.claude/skills/
make install-skills-dry        # print what would be copied, write nothing

CLAUDESKILLSDIR overrides the destination.

Agent SDK (Python)

pip install locus-mcp
locus --palace ~/.locus --task "What toolchain conventions are set?"

MCP Server

The locus-mcp command exposes five tools over the Model Context Protocol.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Locus: common questions

Is Locus MCP server safe?
Yes, by our scan: it is graded A (94/100). Read the Locus safety report
How do I install Locus?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Locus need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Locus maintained?
The last commit was 57 days ago (2026-09-08). The latest release is v0.6.2.
How does Locus compare with other MCP servers?
safety score 94/100 (higher than 96% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.