MCP.so
Sign In
R

Repiscope

@3xpr1ment

Repository

About Repiscope

Read-only MCP server that lets your coding agent see the sibling repositories next to the one it's working in overview, search, read, zero write tools. Security by architecture: path traversal, symlink escapes and secret files are blocked, proven by tests.

#read-only#security#repositories#code-context#claude-code

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "repiscope": {
      "command": "repiscope",
      "args": [
        "--root",
        "~/your/projects/folder"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Repiscope?

Repiscope is a read-only MCP server that gives coding agents (Claude Code, Cursor, or any MCP client) awareness of sibling repositories next to the one they work in — without ever letting the agent modify them. It is built so that safe behaviour is the only behaviour possible: the server exposes zero write tools, structurally preventing any modification to your repos.

How to use Repiscope?

Install via pip install repiscope, then add it to your MCP client with --root pointing to the folder containing your repos (not a repo itself). Optionally hide repos with --exclude repo-a --exclude repo-b. For Claude Desktop there is also a one-click .mcpb bundle (built from mcpb/build.sh). Works with any MCP client; from source, clone the repo and run pip install -e .[dev].

Key features of Repiscope

  • Zero repo-write tools – the agent cannot modify your repositories
  • Secrets invisible – files containing keys, certs, .env* are filtered out
  • Symlinks can't smuggle – files outside the project are invisible
  • You define the perimeter via --root and --exclude flags
  • Lazy cache refresh – overviews rebuilt only when a repo's commit changes
  • Borrowed intelligence – no built-in LLM; calls the agent to write summaries

Use cases of Repiscope

  • A coding agent in project A needs to understand project B's API without writing to B
  • A personal assistant decides where your time goes by seeing real state of every project
  • Any scenario where an agent needs structured, read-only sight of sibling repos while its sandbox stays tight

FAQ from Repiscope

What does Repiscope do that widening the sandbox doesn't?

Widening the sandbox would grant write access too. Repiscope gives the agent structured, read-only sight of every sibling repo through one MCP server, and the sandbox stays tight.

What are the runtime requirements?

Python ≥ 3.11. Developed and tested on macOS; Linux should behave identically, Windows symlink semantics are untested.

Where is data cached and stored?

Overview caches live in ~/.cache/repiscope, never inside your repositories. The store_summary tool writes only to Repiscope's own cache.

What are the known limits of the tools?

Search is a case-insensitive substring match with capped results, no index, no regex. The secret filter works at file level – a password pasted inside an ordinary text file is not scrubbed. There is no manual refresh tool; caches refresh lazily on the next commit.

Does Repiscope require authentication or network access?

No. Repiscope has no LLM of its own, no API key, no model calls, and zero ongoing cost. It runs locally via your MCP client (e.g., STDIO transport).

Frequently asked questions

What does Repiscope do that widening the sandbox doesn't?

Widening the sandbox would grant write access too. Repiscope gives the agent structured, read-only sight of every sibling repo through one MCP server, and the sandbox stays tight.

What are the runtime requirements?

Python ≥ 3.11. Developed and tested on macOS; Linux should behave identically, Windows symlink semantics are untested.

Where is data cached and stored?

Overview caches live in `~/.cache/repiscope`, never inside your repositories. The `store_summary` tool writes only to Repiscope's own cache.

What are the known limits of the tools?

Search is a case-insensitive substring match with capped results, no index, no regex. The secret filter works at file level – a password pasted inside an ordinary text file is not scrubbed. There is no manual refresh tool; caches refresh lazily on the next commit.

Does Repiscope require authentication or network access?

No. Repiscope has no LLM of its own, no API key, no model calls, and zero ongoing cost. It runs locally via your MCP client (e.g., STDIO transport).

Comments

Basic information

License

MIT

Transports

stdio

Author

3xpr1ment

Submitted by

Kostis B

More MCP servers

patent-literature-search-mcp

patsnap

A professional tool for searching Patsnap’s global patent and literature databases using natural language, semantic, or keyword queries. It supports precise filtering and retrieves bibliographic data in Markdown format.

1
F

fhirHydrant

faulkj

Open-source Node.js FHIR MCP server with SMART Backend Services, metadata-aware search/CRUD tools, compact responses, FHIRPath filtering, safe pagination, audit events, and terminology lookup.

14

CoinLobster

CoinLobster

The only MCP server with live whale trades across 15 exchanges plus on-chain DEX flow. Smart Money Radar, real liquidations and outcome-scored signals. No API key required.

3

Medplum

medplum

Medplum is a healthcare platform that helps you quickly develop high-quality compliant applications.

2.5K

Termany

thinkany-ai

Agent-Native Terminal

174