by soth-ai
Reticle intercepts, visualizes, and profiles JSON-RPC traffic between your LLM and MCP servers in real-time, with zero latency overhead. Stop debugging blind. Start seeing everything.
# Add to your Claude Code skills
git clone https://github.com/soth-ai/mcp-reticleNo comments yet. Be the first to share your thoughts!
Reticle is a proxy + UI for debugging MCP integrations:
Supported transports: stdio, Streamable HTTP, WebSocket, HTTP/SSE.
# npm
npm install -g mcp-reticle
# pip
pip install mcp-reticle
# Homebrew
brew install labterminal/mcp-reticle/mcp-reticle
Replace your MCP server command with mcp-reticle run --name <name> -- <command...>.
Example (Claude Desktop-style config):
{
"mcpServers": {
"filesystem": {
"command": "mcp-reticle",
"args": ["run", "--name", "filesystem", "--", "npx", "-y", "@modelcontextprotocol/server-filesystem", "/Users/me/work"]
}
}
}
mcp-reticle ui
mcp-reticle run --log -- npx -y @modelcontextprotocol/server-memory
mcp-reticle proxy --name api --upstream http://localhost:8080 --listen 3001
If you prefer building from source:
git clone https://github.com/labterminal/mcp-reticle.git
cd mcp-reticle
just build
All guides and deep dives are in the GitHub Wiki:
| Command | Purpose |
|---|---|
| mcp-reticle run | Wrap stdio MCP servers and inspect traffic |
| mcp-reticle proxy | Reverse proxy HTTP/SSE/WebSocket transports |
| mcp-reticle ui | Launch the desktop UI |
| mcp-reticle daemon | Headless telemetry hub |
Full details: CLI reference
Reticle can capture tool inputs/outputs and server stderr. Treat recordings and exports as sensitive artifacts.
Recommended reading: Security & privacy
CONTRIBUTING.mdMIT — see LICENSE.