mcp-reticle
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.
Documentation
RETICLE
The Wireshark for the Model Context Protocol (MCP)
See what your agent sees.
Reticle intercepts, visualizes, and profiles MCP JSON-RPC traffic in real time — designed for microsecond-level overhead.
·
·
·
·
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
# npm
npm install -g mcp-reticle
# pip
pip install mcp-reticle
# Homebrew
brew install labterminal/mcp-reticle/mcp-reticle2) Wrap your MCP server (stdio)
Replace your MCP server command with `mcp-reticle run --name -- `.
Example (Claude Desktop-style config):
{
"mcpServers": {
"filesystem": {
"command": "mcp-reticle",
"args": ["run", "--name", "filesystem", "--", "npx", "-y", "@modelcontextprotocol/server-filesystem", "/Users/me/work"]
}
}
}3) Launch the UI
mcp-reticle uiOptional: log-only mode (no UI)
mcp-reticle run --log -- npx -y @modelcontextprotocol/server-memoryOptional: proxy an HTTP-based MCP server
mcp-reticle proxy --name api --upstream http://localhost:8080 --listen 3001Installation
If you prefer building from source:
git clone https://github.com/labterminal/mcp-reticle.git
cd mcp-reticle
just buildDocumentation
All guides and deep dives are in the GitHub Wiki:
- Getting started
- CLI reference
- Client configuration
- Troubleshooting
- Architecture
- Security & privacy
- Development
- Exports
CLI overview
| 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
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.md`
- Dev setup and commands: Development guide
License
MIT — see `LICENSE`.
Frequently asked questions
What is mcp-reticle?
mcp-reticle is 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.
How do I install mcp-reticle?
Open the GitHub repository and follow its README. Most MCP servers are added to your client's MCP config, then called by your agent.
Is mcp-reticle open source?
Yes — it is hosted on GitHub at https://github.com/soth-ai/mcp-reticle and has 118 stars.
Related MCP tools
The go-to web for your AI coding agent — local-first search, fetch, crawl & research over MCP. No API keys, no cloud, $0/query. Public beta.
An AI Gateway, registry, and proxy that sits in front of any MCP, A2A, or REST/gRPC APIs, exposing a unified endpoint with centralized discovery, guardrails and management. Optimizes Agent & Tool calling, and supports plugins.
ToolHive makes deploying MCP servers easy, secure and fun Go-based implementation. Trusted by 1300+ developers. Trusted by 1300+ developers.
A desktop MCP client designed as a tool unitary utility integration, accelerating AI adoption through the Model Context Protocol (MCP) and enabling cross-vendor LLM API orchestration.
Official remote MCP server for Atlassian. Securely connect Jira, Confluence, Jira Service Management, Bitbucket, and Compass to Claude, ChatGPT, Cursor, VS Code, and other AI tools using OAuth 2.1 or API tokens.
Code research platform for AI agents; find, understand, and prove context across your code and all of GitHub, in a fraction of the tokens. One toolset, MCP or CLI
Run your own MCP server? See who uses it and what to fix.
Measure it with TrackMCP