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.
@3xpr1ment
基本情報
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.
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"repiscope": {
"command": "repiscope",
"args": [
"--root",
"~/your/projects/folder"
]
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
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.
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].
.env* are filtered out--root and --exclude flagsWidening 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.
Python ≥ 3.11. Developed and tested on macOS; Linux should behave identically, Windows symlink semantics are untested.
Overview caches live in `~/.cache/repiscope`, never inside your repositories. The `store_summary` tool writes only to Repiscope's own cache.
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.
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).
Console, Backend and CLI to manage Capgo Instant update and Native build for Capacitor apps Build and upload to app store your mobile app

MCP server for managing Gologin browser profiles, proxies, fingerprints and cloud browser sessions through AI conversations
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.

OrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.
コメント