PlugWiki
Reticle logo

Reticle MCP Server: Setup for Claude, Cursor and Other Apps

CommunityLocal

Lets your coding assistant open your running web app, click through it and report whether a change really works.

Reticle puts a small development-only add-on inside your app. Your assistant can then click, type and read what happened, including requests, state and console errors. It returns a pass, fail or cannot-tell verdict with the file and line to fix.

It runs on your computer with no account. Setting it up also edits your project, so run the dry-run first. It is built for developers who use Claude Code, Cursor or Codex on web apps.

Good for

  • Developers who want their coding assistant to test its own changes
  • Teams who want a saved check that runs in CI
  • Front-end developers using React, Next.js, Vue or Svelte

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install Reticle MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the Reticle MCP server to Claude Code. Run this command:
    
    claude mcp add reticle -- npx -y @reticlehq/server mcp
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js 20.11+, A web app with a dev server, Node.js.

Read-only mode: There is no read-only mode. Do not point it at an app that uses real data.

The README's MCP entry runs the server with the mcp subcommand: npx @reticlehq/server mcp. Without mcp the same package runs a one-off check instead of starting the tools. Run npx @reticlehq/server init in your app first, which adds the dev-only SDK and can register your agents itself. Add --dry-run to preview, or --no-mcp to skip agent files. Configs here are adapted from that entry, so they are generated.

Built from the package data we hold. Not yet tested by us.

Tools

  • Moves the connected browser tab to a URL or reloads it

    Sends the tab that is connected to your dev app to a new address, or reloads it in place. Use it for a real page load, not a link click inside the app.

    Try: “Open the /checkout page of my app.”

    Write · reticle_navigate

  • Clicks, types, selects or drags in your running app

    Performs one action in the page and only promises it was sent, not that it worked. Pair it with a check afterwards.

    Try: “Click the Pay button.”

    Write · reticle_act

  • Does an action and waits for the result in one call

    Performs one action and waits for a named outcome, then returns a verdict. This is the main way to check that a click really did something.

    Try: “Click Save and confirm a POST to /api/save returns 200.”

    Write · reticle_act_and_wait

  • Checks a claim against what the app actually did

    Evaluates a statement such as 'the cart count is 1' against network, state and page. It answers yes, no or cannot tell, with the evidence.

    Try: “Verify the invoice total shows 120.00.”

    Read · reticle_assert

  • Reads the page, one element or your store without changing anything

    Returns the rendered page tree, finds elements, shows one element's source file and line, or reads your app's state store.

    Try: “Show me the cart state in the store.”

    Read · reticle_look

  • Shows the timeline of everything the app just did

    Returns requests, console messages, routing and DOM changes in order for a time window. Use it when you do not yet know what went wrong.

    Try: “What happened in the app after I clicked Pay?”

    Read · reticle_observe

  • Manages sessions, notes and feedback to the agent

    Lists connected browser tabs, and lets the agent narrate, send feedback or review its run.

    Try: “List the tabs Reticle is connected to.”

    Write · reticle_session

  • Replays saved checks or crawls the whole app

    Runs actions such as replaying saved flows, listing coverage, or crawling. The crawl drives every reachable control and really clicks them.

    Try: “Replay all my saved flows.”

    Runs code · reticle_verify

  • Lists every Reticle tool and how to call it

    Returns the full tool list with one-line summaries and the argument rules for the ones you name.

    Try: “What Reticle tools exist beyond the main ten?”

    Read · reticle_tools

  • Calls any other Reticle tool by name

    A hatch to tools that are not shown by default, such as storage reads, a fake clock, network mocking, screenshots and saving flows. It can therefore reach more than the ten listed tools.

    Try: “Mock the /api/orders call to return an error.”

    Write · reticle_run

Read from the source code

Permissions

medium risk · 6 things to watch · 1 advisory

Medium risk

The assistant can click and type in your running app and change files during setup. Use it on a dev copy with test data, and run the setup dry-run first.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It clicks and types in your running app

    The crawl in reticle_verify really clicks every reachable control, which can change data. Point it at a dev database, never production data. github.com

  • Setup edits your project and agent config

    The init step adds dev packages, changes your build config and writes rules into CLAUDE.md and AGENTS.md. Run it with --dry-run first, and use --no-mcp to skip agent files. github.com

  • The Codex installer turns off per-call approval for its tools

    If codex is on your PATH, reticle setup install registers Reticle with codex mcp add and adds default_tools_approval_mode = "approve" under [mcp_servers.reticle] in ~/.codex/config.toml, so Codex stops asking before each Reticle call. Change that line to "prompt" to undo it. github.com

  • It keeps your prompts and sends usage counts

    A prompt hook saves each prompt, redacted, in .reticle/, and a linked project sends it along. Anonymous usage counts are on by default; set RETICLE_TELEMETRY=0 to turn them off. github.com

  • One tool reaches the unlisted tools

    reticle_run can call any registered tool, such as network mocking and flow saving, even though they are not shown by default. npmjs.com

  • The local bridge listens on loopback

    The bridge binds to 127.0.0.1 by default and pairs with a token. The README says it never evaluates arbitrary JavaScript in your page. github.com

Security advisories

Technical details
Turning on read-onlyNo read-only mode is documented. Look, observe and assert only read, but act, navigate and verify change your app.
Talks toYour local dev app and a local bridge on 127.0.0.1:4400. Anonymous usage counts to Reticle (on by default). Reticle's platform only if you link a project
Sign-in and keysNo account needed. A bridge token is stored owner-only in ~/.reticle/. A linked project uses a key stored by the CLI.

Questions

Is it official?

Not in the vendor sense. It is the Reticle project's own server, published by the same team as the Reticle tool, and it is not made by the makers of your app or framework.

Is it free?

The server is open source under Apache-2.0 and checks run on your machine with no account. A linked platform project and the optional Harness are separate.

Do I need an account or API key?

No. Verdicts are made locally. A key is only used if you link a project to the Reticle platform.

Does it send my app's data anywhere?

The README says nothing from your app leaves your machine unless you link a project. It also sends anonymous usage counts by default, which you can turn off.

What does the setup change in my project?

It adds two dev dependencies, edits your build config, writes a dev-only file and appends rules to CLAUDE.md and AGENTS.md. Use the dry-run option to preview, and the README lists every file.

Does it work in production?

It is meant for development builds. The README says production builds leave the SDK out unless you opt in to production mode.

Which assistants can use it?

The README names Claude Code, Cursor, Codex, Windsurf, VS Code and Gemini CLI, and any other client that supports MCP.

How many tools does it have?

Ten are shown by default. More are reachable through one dispatch tool, so the list on this page is partial.

Information

updated Nov 2, 2026

Publisher
Community
Package
@reticlehq/server
Registry
npm
Transport
stdio
Auth
None
Version
3.9.0
License
Apache-2.0
Last commit
Oct 31, 2026
Open issues
187
Listed in
Official MCP registry

WebsiteGitHubnpmOfficial MCP RegistryChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 4
  1. Reticle README · github.com
  2. @reticlehq/server on npm · npmjs.com
  3. npm package metadata · registry.npmjs.org
  4. Reticle README (v3.9.0) · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.