What is Reticle?
Reticle is a proxy + UI for debugging MCP integrations:
inspect raw JSON-RPC messages (requests / notifications / responses)
correlate request ↔ response instantly
profile latency and token estimates
capture server stderr and crashes
record sessions and export logs
Supported transports: stdio, Streamable HTTP, WebSocket, HTTP/SSE.
Quick start
1) Install
2) Wrap your MCP server (stdio)
Replace your MCP server command with mcp-reticle run --name <name> -- <command...>.
Example (Claude Desktop-style config):
3) Launch the UI
Optional: log-only mode (no UI)
Optional: proxy an HTTP-based MCP server
Installation
If you prefer building from source:
Documentation
All guides and deep dives are in the GitHub Wiki:
CLI overview
Command | Purpose |
| Wrap stdio MCP servers and inspect traffic |
| Reverse proxy HTTP/SSE/WebSocket transports |
| Launch the desktop UI |
| Headless telemetry hub |
Full details: CLI reference
Security & privacy
Reticle can capture tool inputs/outputs and server stderr. Treat recordings and exports as sensitive artifacts.
Recommended reading: Security & privacy
Contributing
Repo guidelines:
CONTRIBUTING.mdDev setup and commands: Development guide
License
MIT — see LICENSE.