# Reticle

> Reticle is an open-source MCP server for developer tools. Verify a running web app from inside: look, act, observe and assert, without screenshots. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** Web, CLI, self-hosted
- **Website:** https://www.reticle.sh
- **Repository:** https://github.com/reticlehq/reticle/tree/HEAD/server
- **MCP Registry name:** io.github.reticlehq/reticle
- **Categories:** developer tools, browser automation
- **Listing updated:** 2026-11-14

## About

Reticle's server hosts a localhost WebSocket bridge that the app's @reticlehq/browser SDK connects to, then gives a coding agent ten default tools to navigate, look at, act on, observe and assert against the live app. Only act-and-wait and assert return a verdict; the rest move or read.

The site argues that agents often claim done on mock data or a broken neighbouring flow, so Reticle reads network calls, app state and console rather than the screen. Verified flows are recorded and replayed after each change; the site says a four-flow replay costs about 480 tokens against roughly 120,000 for an LLM re-driving them. On its benchmark of 88 seeded bugs, Reticle reports 85 caught against 59 for Playwright.

More tools (screenshots and visual diff, saved flows, baselines, clock control, network mocking, crawl and coverage) are not advertised by default; reach them through reticle_run. The server is Apache-2.0 and starts with npx @reticlehq/server init.

## Features

- **In-app verification:** Reads network, state and console from inside the running app.
- **Verdict tools:** reticle_act_and_wait and reticle_assert return a pass or fail.
- **Remembered flows:** Records a verified flow and re-checks it on each change.
- **Cheap replays:** Re-running recorded flows uses no model in the loop.
- **Hidden extra tools:** Screenshots, mocking and coverage are reachable by name.
- **Failure pointers:** The site says failures name the file and line.

## Good for

- Make a coding agent confirm checkout still works after an edit
- Catch hardcoded mock responses
- Re-run key flows on every commit cheaply
- Check that a card is charged once, not twice

## Install

### Claude Code (Terminal)

```sh
claude mcp add reticle -- npx -y @reticlehq/server
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "reticle": {
      "command": "npx",
      "args": [
        "-y",
        "@reticlehq/server"
      ]
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "reticle": {
      "command": "npx",
      "args": [
        "-y",
        "@reticlehq/server"
      ]
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "reticle": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@reticlehq/server"
      ]
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "reticle": {
      "command": "npx",
      "args": [
        "-y",
        "@reticlehq/server"
      ]
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "reticle": {
      "command": "npx",
      "args": [
        "-y",
        "@reticlehq/server"
      ]
    }
  }
}
```

## Tools

- `reticle_navigate`: Navigates the app.
- `reticle_look`: Reads the current app view.
- `reticle_act`: Acts on the app.
- `reticle_act_and_wait`: Acts and waits, returning a verdict.
- `reticle_observe`: Observes network, state and console.
- `reticle_assert`: Asserts a condition and returns a verdict.
- `reticle_session`: Manages the session.
- `reticle_tools`: Lists additional tools.
- `reticle_run`: Runs a non-advertised tool by name.
- `reticle_verify`: Verifies a flow.

## FAQ

### How do I set it up?

Run npx @reticlehq/server init, then register npx @reticlehq/server mcp with your agent.

### What is the licence?

The server is Apache-2.0.

### Does it need screenshots?

No, though screenshot and visual diff tools exist among the unadvertised ones.

### How is it benchmarked?

The site reports 85 of 88 seeded bugs caught versus 59 for Playwright.

### Is there a hosted option?

The site mentions a platform that tests every preview and PR in a real browser; prices are not published.

### Is Reticle free?

Yes. Reticle is open source, so you can use and self-host it for free.

### How do I add Reticle to Claude Code?

Run this command in your terminal: claude mcp add reticle -- npx -y @reticlehq/server

### What are the best alternatives to Reticle?

The closest alternatives to Reticle are REA, Browser Use, Scrapling MCP Server, Codebase Memory and GitHub.

## Alternatives

- [REA](https://ai-powered.com/mcp/rea): REA is an open-source MCP server for developer tools.
- [Browser Use](https://ai-powered.com/mcp/browser-use): Browser Use is a freemium MCP server for browser automation.
- [Scrapling MCP Server](https://ai-powered.com/mcp/scrapling-mcp-server): Scrapling MCP Server is an open-source MCP server for web search and scraping.
- [Codebase Memory](https://ai-powered.com/mcp/codebase-memory): Codebase Memory is an open-source MCP server for knowledge and memory.
- [GitHub](https://ai-powered.com/mcp/github-2): GitHub is an open-source MCP server for developer tools.
- [Serena MCP: the IDE for your agent](https://ai-powered.com/mcp/serena-mcp-the-ide-for-your-agent): Serena MCP: the IDE for your agent is an open-source MCP server for developer tools.
- [XERJ](https://ai-powered.com/mcp/xerj): XERJ is an open-source MCP server for knowledge and memory.
- [Ouroboros](https://ai-powered.com/mcp/ouroboros): Ouroboros is an open-source MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/reticle
