Reticle is a low-overhead proxy + UI for inspecting and profiling MCP JSON-RPC traffic between MCP clients and MCP servers.

• Getting started: Getting-Started
• CLI reference: CLI
• Client setup: Client-Configuration
• Troubleshooting: Troubleshooting

1. Wrap your MCP server with mcp-reticle run
2. Launch the UI with mcp-reticle ui
3. Inspect requests/responses, stderr, latency, and token estimates

See: Getting-Started

Use mcp-reticle proxy to reverse-proxy an upstream MCP server and inspect traffic.

See: CLI

Reticle sits between:

• MCP client (Claude Desktop, Cursor/Cline, custom agents)
• MCP server (your tools)

It intercepts JSON-RPC messages, correlates request/response, and streams telemetry to the UI.

See: Architecture

Reticle can capture tool inputs/outputs and server stderr. Treat logs and exports as sensitive artifacts.

See: Security

• Dev environment and commands: Development
• Repo contribution guidelines: see CONTRIBUTING.md in the main repo.