rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Lets a coding agent see the web UI it just changed: findings as text, motion included.
Skills that teach the AI this kind of work; they work alongside this one
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 7/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 19/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Agent Eyes. Follow https://mcp.popnx.com/i/muhlegger-agent-eyes.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 17, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Agent Eyes for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "agent-eyes": { "command": "npx", "args": [ "-y", "@muhlegger/agent-eyes", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Agent Eyes tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"agent-eyes": {
"command": "npx",
"args": [
"-y",
"@muhlegger/agent-eyes",
"mcp"
]
}
}
}Use Agent Eyes and tell me what you can do for me, then show me one thing✓ If Claude says it is using Agent Eyes or shows a Agent Eyes tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Agent Eyes yet
Agent Eyes runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Agent Eyes
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Agent Eyes for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user agent-eyes -- npx -y @muhlegger/agent-eyes mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Agent Eyes tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user agent-eyes -- npx -y @muhlegger/agent-eyes mcpYou should see Agent Eyes listed as connected
Use Agent Eyes and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Agent Eyes or shows a Agent Eyes tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Agent Eyes for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "agent-eyes": { "command": "npx", "args": [ "-y", "@muhlegger/agent-eyes", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Agent Eyes tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Agent Eyes and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Agent Eyes or shows a Agent Eyes tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Agent Eyes for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "agent-eyes": { "type": "stdio", "command": "npx", "args": [ "-y", "@muhlegger/agent-eyes", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Agent Eyes tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Agent Eyes and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Agent Eyes or shows a Agent Eyes tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user agent-eyes -- npx -y @muhlegger/agent-eyes mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"agent-eyes": {
"command": "npx",
"args": [
"-y",
"@muhlegger/agent-eyes",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"agent-eyes": {
"command": "npx",
"args": [
"-y",
"@muhlegger/agent-eyes",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"agent-eyes": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@muhlegger/agent-eyes",
"mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account muhlegger, which owns the repo
Code last changed 2 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/muhlegger-agent-eyes)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 days ago, and the latest version (0.3.3) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Agent Eyes | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Stop being your agent's eyes.
Your coding agent says "done" about a screen it never saw. Then you open the page, notice the panel that snaps instead of sliding, describe it badly, and wait for another round.
agent-eyes gives the agent that look, motion included. One shell command takes the screenshots (logged in, at every width, after clicks and hovers) and hands back what is wrong as text: an animation that squeezes, flickers, snaps or freezes, content that jumps after load, a page that scrolls sideways on a phone. The agent reads a few lines and opens an image only when it has to.
The tool lines and both frame strips are real output from the bundled demo page, shortened. The chat lines around them are staged.
Português abaixo · Benchmark · MIT · Node 18+ · local, no cloud
Use it from: a shell command · a Claude Code plugin · an MCP server for Cursor, Windsurf and others
Almost every change an agent makes to a web app ends up on a screen, and someone has to look at it. Today that someone is you.
| Your day now | With agent-eyes |
|---|---|
| The agent says "done". You open the page and it isn't. | The agent looks before it says "done", and reads what is wrong. |
| You take a screenshot, paste it, describe the problem ("it kind of jumps"), wait, and repeat. | The agent takes its own screenshots, logged in. The problem comes back as a sentence with numbers: width jumped from 0 to 252 px in a single frame. |
| It walks past things anyone would see: content that jumps after load, a page that scrolls sideways on a phone, an error on the page. | Every run reports them as text, whether or not anyone asked. |
| Animations are invisible to it. A screenshot is a still, and a transition that never runs looks perfect before and after. | The motion is recorded at real speed and measured: shrink-and-return, snap, flicker, freeze. |
| When the agent does look, it writes a throwaway script first. In my sessions that took a median of 1.2 min per look, and one script in five was rewritten before it showed anything. | One command. The login lives in a config file, once. |
| Screenshots pile up in the conversation and are re-read on every later step. | Text first. Each image is listed with its token cost, and identical means there is nothing to open. |
What it does not do is make a design beautiful: taste stays with you. It takes away the rounds you spend on what is broken, so the rounds you do spend are about the design.
AGENTS.md (Codex, Gemini CLI, ...). Only dependency: Playwright. Runs locally, nothing leaves your machine.npm install -g @muhlegger/agent-eyes
agent-eyes install # downloads Chromium once (add --with-deps on a fresh Linux) agent-eyes http://localhost:3000 /settings --widths 1440,390
Or without installing: npx -y @muhlegger/agent-eyes http://localhost:3000 /settings. (The package is @muhlegger/agent-eyes; the unscoped agent-eyes on npm is unrelated.)
Then tell your agent it exists. Pick one:
/plugin install agent-eyes --marketplace muhlegger/agent-eyes
On versions before 2.1.275: /plugin marketplace add muhlegger/agent-eyes, then /plugin install agent-eyes@agent-eyes. The plugin is one skill: Claude reaches for agent-eyes after a visual change instead of writing a Playwright script. Prefer a plain file in one project? mkdir -p .claude/skills/agent-eyes && agent-eyes skill > .claude/skills/agent-eyes/SKILL.md.
{
"mcpServers": { "agent-eyes": { "command": "agent-eyes", "args": ["mcp"] } } }
(Without a global install: "command": "npx", "args": ["-y", "@muhlegger/agent-eyes", "mcp"].)
In .cursor/mcp.json (Cursor), ~/.codeium/windsurf/mcp_config.json (Windsurf) or your client's MCP settings. Three tools: check_ui (the whole check in one call, findings as text), view_image (open one of the images it listed, only when needed) and compare_images. Images are never pushed into the conversation: the agent asks for the ones it wants, knowing what each costs.
agent-eyes skill >> AGENTS.md
| You changed... | agent-eyes tells the agent |
|---|---|
| An animation or transition | it shrank and came back, snapped (a size that jumps in one frame: the transition is written but not running), flickered, disappeared, left its path, or the browser froze (above ~50 ms is felt) |
| A page that loads data | which elements jumped after load, and by how much |
| A layout | horizontal scroll on a phone, at every width you asked for |
| Anything | page errors, console errors, requests that failed (404, 5xx), actions that missed their target |
| A theme | the same screen in dark or light, or with reduced motion (--color-scheme dark, --reduced-motion) |
| A screen, compared with before | identical (nothing to open), or one image with each changed region boxed in red, listed as text |
It is one command, so it goes wherever a command goes.
| When | How | What comes back |
|---|---|---|
| The agent changed a screen | The plugin, the MCP server or the AGENTS.md block: the agent runs it before saying "done" | What is wrong, as text. This is what it was built for. |
| A refactor that should change nothing | -o /tmp/before, refactor, then --compare /tmp/before | identical, or each changed region boxed in red |
| "Does it work on a phone?" | --widths 1440,768,390 | Sideways scroll and cut-off content, per width |
| A gate in a pre-commit hook or in CI | --strict | Exit code 1 when anything is found |
| A trigger in Claude Code | A Stop hook around --strict | The turn cannot end while the screen is broken |
The trigger is a few lines of shell. When the agent touched UI files and tries to finish, the hook looks at the screens you listed. If something is wrong, Claude Code sends the findings back as the agent's next input:
Stop hook feedback:
glitch@1280 motion: 21 distinct frames over 508 ms ! the browser froze for 126 ms while animating (noticeable above ~50 ms) ! width shrank from 280 to 200 px mid-motion and came back (see the frames)
That is real output, shortened, from the bundled demo page with its planted glitch. With the screen clean, the turn ends as usual.
Anthropic's guide to Claude Code puts the problem this way (Give Claude a check to run):
Claude stops when the work looks done. If it has nothing to run that tells it whether the work actually
*is* done, "looks done" is all it has to go on. In practice that makes you the test suite, and every
mistake sits there until you happen to notice it.
The guide lists a browser screenshot among the checks, next to tests and linters. Anthropic's engineers ran into the same thing building apps with long-running agents: "agents reliably skew positive when grading their own work", and apps "often looked impressive but still had real bugs when you actually tried to use them", so they gave the reviewing agent a browser to use the live page before scoring (Harness design for long-running application development, March 2026).
For code, the check is a test. For a screen, the check is looking, and looking is the expensive one:
agent-eyes is that look made cheap: one command, the answer as text, pass or fail with --strict.
Neither source puts a number on how much a check helps. The only numbers on this page are mine, from a small sample, below. agent-eyes is not affiliated with Anthropic.
On a real product, a side panel was meant to slide open. The width transition was written in the CSS, but a later transition: rule on the same element replaced the property list, so the column snapped open in a single frame while its content faded in. The code reads as animated; only watching it shows it isn't. It reached the product owner, who had to describe it ("it kind of jumps, I can't explain it") and wait for another round.
In the benchmark below, the same defect was planted again, and none of the six agent runs (three with v0.1.1, three without) reported it. Since v0.2, agent-eyes says it in one line:
panel@1536 motion: 22 distinct frames over 459 ms
! width jumped from 0 to 252 px in a single frame while other things animated: if it should slide, its transition is not running (often a later "transition:" rule on the same element replaces the property list)
Checked on that exact defect, and on the fixed version of the same screen, which it reports clean. The benchmark numbers below were measured before this detection existed.
A production Next.js app (a few hundred components), on an isolated copy with its own database reset before every run. Three defects planted in a calendar screen; the prompt named the parts that changed and the interactions to check, never a defect. Two interactions had to be reported clean. Claude Code with Opus 5.5 at high effort, 3 runs per side, answer key written before the runs, blind grading checked by hand.
| Without agent-eyes | With agent-eyes (v0.1.1) | |
|---|---|---|
| Defects found | 4 of 9 | 6 of 9 |
| False alarms | 0 | 0 |
| Time (median) | 5.0 min | 3.9 min |
| Cost (median) | $0.97 | $0.75 |
| Throwaway scripts written | 3 | 0 |
On a small demo app whose code the agent can read in full, every arm found every defect, and a plain checklist in the prompt was as good as the tool. The full methodology, both benchmarks, the raw results and how