Repiscope MCP server
{
"mcpServers": {
"3xpr1ment-repiscope": {
"command": "uvx",
"args": [
"repiscope"
]
}
}
}{
"mcpServers": {
"3xpr1ment-repiscope": {
"command": "uvx",
"args": [
"repiscope"
]
}
}
}{
"mcpServers": {
"3xpr1ment-repiscope": {
"command": "uvx",
"args": [
"repiscope"
]
}
}
}{
"servers": {
"3xpr1ment-repiscope": {
"command": "uvx",
"args": [
"repiscope"
]
}
}
}{
"mcpServers": {
"3xpr1ment-repiscope": {
"command": "uvx",
"args": [
"repiscope"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall uvx repiscopeversion 0.2.2
What it does
Repiscope is a read-only MCP server that lets your coding agent explore sibling repositories in a project folder without any ability to modify them. It exposes project overviews, file contents, and search across repos through tools that structurally cannot write to any repository.
- An agent working in one project queries another project's API structure to understand how to call it.
- An agent exploring a codebase asks Repiscope to search across all sibling repos for examples of a pattern or configuration.
- An agent gathers current state and recent changes across all projects to help you prioritize which to work on next.
Tools this server exposes
| Tool | Does |
|---|---|
| list_projects | Returns all sibling repositories with one-line descriptions. |
| project_overview | Returns full overview of a project including purpose, stack, structure, and recent commits, cached and refreshed on git hash change. |
| search | Searches for text across files in specified or all projects, returning matching files and lines. |
| read_file | Returns full contents of a specified file in a project, with size limits applied. |
| store_summary | Allows an agent to cache a summary of a project for future reference by other agents. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.
This server has not seen a commit in 3 mo. It may still work, but nobody is currently fixing it — check the alternatives before you build on it.