About Phyll
Phyll adds browser-based UX review tools to Codex, Claude Code, and other MCP-capable agents. The agent tests core tasks and reports usability obstacles, while the fixes preserve the app's design.
Key features
- 01Browser-based review of core app tasks
- 02Screenshots and page probes at laptop and phone sizes
- 03Source scan for AI tells
- 04Review report saved with a link
- 05Setup for named agents or other MCP clients
Use cases
- 01Review an app's main user flows
- 02Find usability obstacles such as dead buttons
- 03Scan source code for AI tells
MCP support
Phyll runs as an MCP connector for agents, providing browser-control, review, scan, account, and upgrade tools. Its setup command registers the connector for supported agents or prints configuration for another MCP-compatible agent.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
18Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| url | string | Yes | Address where the app runs and answers, such as http://localhost:3000. Start the app first if it is not running. |
| jobs | array | No | The two or three things the end user comes to do, as the person named them, such as Book a haircut. Leave it out when the person did not say. |
| name | string | No | Name of the product, for the report's project on agentphyll.com. When left out, it comes from .phyll/config.json, then from the folder's name. |
| user | string | No | Who uses the app, in the person's words, such as barbershop customers booking on a phone. Leave it out when the person did not say. |
| language | string | No | Language of the report as a code, such as en or pt-BR. Use the language the person writes in. When left out, it comes from the project's .phyll/config.json, then from this computer's language. |
| project_dir | string | No | Path to the project folder, when it is not the folder the agent runs in. A relative path starts from that folder. |
Details
From the project READMEphyll
UX review for apps built with AI, inside the agent you already use.
Phyll plugs into Codex, Claude Code or any agent that speaks MCP. Your agent opens your app the way a first-time user would, walks the core jobs in a real browser, and writes a report of what gets in the way: forms that ask for more than the job needs, sign-up walls, dead buttons, text too faint to read. The fixes keep your design.
The AI work runs in your agent, on your own plan. This package adds the browser, the page probe, the source scanner and the link to Phyll's engine, which sends the review method, checks the report and keeps it with a link.
Start
npx phyll signup [email protected]
npx phyll setup codex # or claude, cursor, windsurf, gemini
Then ask your agent: "review my app at http://localhost:3000".
setup registers the connector in Codex's config.toml, with claude mcp add, or in the mcpServers of Cursor's ~/.cursor/mcp.json, Windsurf's ~/.codeium/windsurf/mcp_config.json or Gemini CLI's ~/.gemini/settings.json, keeping everything else in the file. It also installs the Chromium build the connector uses. For any other agent that takes MCP servers, npx phyll setup other prints the entry to paste. You need Node 20 or newer.
Your reports, keys and plan are also on the site: npx phyll account opens your account there, already signed in. If you lose the key, sign in at agentphyll.com/login with your email and create a new one.
Commands
| Command | What it does |
|---|---|
signup <email> | Create a free account, with 5 full reviews. The key is saved in ~/.phyll |
login <key> | Use an account you already have on this computer |
setup <agent> | Connect Phyll to codex, claude, cursor, windsurf or gemini and install the browser; setup other prints the settings for any other agent |
status | Your plan and the reviews left |
account | Open your account on agentphyll.com, already signed in: reports, usage, keys and plan |
pro | Subscribe to Phyll Pro, R$ 9 a month, with unlimited reviews |
billing | Change the card or cancel Phyll Pro |
scan [folder] | Scan the source for AI tells, with no account and no AI. --format json for scripts, --format badge for a README badge |
mcp | Run the connector for your agent; setup registers it for you |
logout | Forget the key on this computer |
The tools your agent gets
start_review scans the project, creates the report folder and returns the method. capture saves a screenshot and the page probe of each route at laptop and phone size. open, snapshot, click, fill, select, check, press, back, screenshot, probe and resize drive the browser, which stays on your app. guide returns a part of the method, finish_review sends the report to the engine and writes report.md, and scan, account and upgrade do what their names say.
What leaves your computer
Your source code, your screenshots and your agent's conversation stay on your computer. When a review starts, the connector sends the app's address, the project name and a summary of the scan: which tells it found, how many times, and the paths of routes and forms. When it ends, it sends the report your agent wrote, which the engine keeps so the link works.
More
The scanner, the plugin and four example apps are in the repository. MIT license.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.