Front-End Checklist MCP
Front-End Checklist reviews frontend code and public pages against 386 rules for accessibility, SEO, performance and security.
- 74,722 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- Code and page addresses go to the hosted server unless the local CLI is used.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/front-end-checklistDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Code and page addresses go to the hosted server unless the local CLI is used.
This is third-party code. Review the repository files before installing.
What it does
Front-End Checklist turns a popular web development checklist into an agent tool. Through the MCP server an agent searches rules by keyword, category or priority, reviews pasted HTML, CSS, JavaScript, React and Next.js code, and audits a public `https://` address. The same rules ship as skills: a global audit skill plus focused skills for one topic, such as `https`. The `frontendchecklist` CLI adds `review`, `audit`, `search` and `rule` commands. It works offline and prints JSON when its output is piped.
Who it is for. Frontend developers and reviewers who want an agent to check code against a shared rule list before a commit or release.
Good fit when
- Before a pull request, a React component is checked for accessibility and speed.
- Before a site launch, the agent walks the SEO, security and image checklists.
- A public client or competitor page is audited by its address.
- A review disputes a rule and the agent pulls its wording with a fix example.
Not a fit when
- You need to check a staging site behind login: the audit covers public `https://` pages only.
- You want an automatic linter that rewrites files rather than reports findings.
- The project is not a web interface, for example a backend or a mobile app.
Example request
Use the Front-End Checklist MCP to review this React component and report the highest-confidence findings first.MCP
- Transport
- http, stdio
- Authentication
- not required
Limitations
The hosted MCP server receives code and addresses from requests, so private code is better checked with the local CLI or the stdio server from the repository. Findings show a broken rule but do not replace manual review or screen reader testing. Some clients discover MCP tools lazily, so name the server in the prompt. Rules are in English: 386 across 11 categories. Skills from `npx skills add` and the hosted server update independently, so rule numbers in answers may differ.
How to disable. Remove the `https://mcp.frontendchecklist.io` entry from the client MCP settings and delete skills installed through `npx skills`. Remove the global CLI with your package manager.
FAQ
Which MCP tools come first?
For pasted code start with `review_code`. `search_rules` finds rules, `get_workflow` and `get_checklist_rules` drive launch audits, and `audit_url` checks a public address.
How do I install the skills?
Run `npx skills add frontendchecklist/skills`. A single topic installs separately: `npx skills add frontendchecklist/skills --skill https`.
Is a key or sign-up required?
No, the public server needs no authorization. The repository is MIT licensed and a local stdio server lives in `packages/mcp`.
Can it check a page behind login?
No. `audit_url` accepts public `https://` pages only. For private code use the local CLI or paste fragments into `review_code`.
How do I use the CLI without installing?
Run `npx -y @frontendchecklist/cli review <paths>`. The CLI works offline and prints JSON when its output is piped.
Discussion
No questions or reviews yet.
Related
MCP serversAn accessibility scanner for agents and CI: renders a page in Chromium with axe-core or lints React, Vue and Angular source.
A 147-rule design check that finds AI-interface tells, fixes the mechanical ones and hands the rest to an agent skill
A set of skills for web quality audits: performance, Core Web Vitals, accessibility, SEO and best practices from Lighthouse
A skill reviews a UI against 112 Checklist Design checklists or gives honest design critique: hierarchy, type, accessibility.
Connects an agent to a running Next.js 16+ dev server: errors, routes, logs and docs for your installed version
An MCP server and skill for interfaces: 31 design systems for shadcn/ui, UI and UX principles and accessibility review for agent-written code
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Front-End Checklist (this card) | no | not required | 74,722 | |
| Web Quality Skills | no | 3,079 | ships web quality skills; Front-End Checklist rests on a numbered base of 386 rules served through MCP and a CLI | |
| Frontend Design (Ilm-Alan) | no | 167 | teaches expressive interface design; here finished code is checked against rules |
README in short
The README combines the rules website, a hosted MCP server, skills and the checklist itself, 386 items with priorities from critical to low.