kiro-frontend-engineer-mcp
Provides tools for fetching and resolving pull request review comments on GitHub.
Allows fetching CI failure logs from GitHub Actions for automated self-healing.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@kiro-frontend-engineer-mcp run design audit on https://example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
kiro-frontend-engineer-mcp
A Model Context Protocol (MCP) server implementing a 7-stage agentic frontend workflow:
Design Audit — Web design inspection checklist (accessibility, layout stability, edge cases)
Component Blueprint — AI-driven component generation with full interactive states
Best Practices — React/Next.js guidelines applied before code generation
Browser Validation — Real browser run via kane-cli
E2E Testing — Playwright test execution with pass/fail capture
CI Self-Healing — Auto-fetch GitHub Actions failures and generate fixes
PR Review Loop — Auto-resolve PR review comments
Quick Start — Add to Your Project
Option 1: Kiro (recommended)
Add this to your project's .kiro/settings/mcp.json:
{
"mcpServers": {
"frontend-engineer": {
"command": "node",
"args": ["<path-to-this-repo>/dist/index.js"]
}
}
}Option 2: npx (after publishing to npm)
{
"mcpServers": {
"frontend-engineer": {
"command": "npx",
"args": ["-y", "kiro-frontend-engineer-mcp"]
}
}
}Option 3: Clone and build locally
git clone https://github.com/<your-username>/kiro-frontend-engineer-mcp.git
cd kiro-frontend-engineer-mcp
npm install
npm run buildThen point your MCP config to the built output:
{
"mcpServers": {
"frontend-engineer": {
"command": "node",
"args": ["./kiro-frontend-engineer-mcp/dist/index.js"]
}
}
}Related MCP server: jt-mcp-server
What It Provides
Resources (context the agent reads)
URI | Description |
| WCAG AA checklist, layout stability, responsive breakpoints |
| Server/Client components, TypeScript patterns, performance |
Prompts (agent personas)
Name | Description |
| Generates production-ready component blueprints from layout specs |
Tools (agent actions)
Name | Description |
| Visual browser validation via kane-cli |
| Run Playwright E2E tests |
| Fetch CI failure logs for self-healing |
| Fetch and resolve PR review comments |
Orchestration Flow
The agent should chain calls in this order:
Read web-design-guidelines → Call ui-ux-pro-max prompt → Read react-best-practices
→ Generate code → run_kane_cli → execute_playwright_test
→ (if CI fails) github_fetch_ci_logs → fix → push
→ (if PR comments) github_address_review_comments → resolve → pushPrerequisites
Node.js ≥ 18
ghCLI (for CI logs and PR comment tools) —gh auth loginPlaywright installed in your project (for E2E tool)
kane-cli (optional, for browser validation tool)
License
MIT
Available Tools
4 toolsexecute_playwright_testA
Run local Playwright E2E test suites on generated components. Captures terminal logs, test pass/fail results, and error screenshots.
Inputs: testPath (required), headed.
github_address_review_commentsC
Fetch open PR review comments from GitHub to feed back into agent context for automated resolution.
Inputs: owner (required), repo (required), pullNumber (required).
github_fetch_ci_logsA
Fetch CI build/lint failure logs from GitHub Actions. Used for self-healing: agent reads failures and generates fixes.
Inputs: owner (required), repo (required), runId (required).
run_kane_cliB
Orchestrate a real browser run via kane-cli. Accepts a target URL and optional interaction sequences (click, type, scroll) to visually validate rendered components.
Inputs: url (required), interactions.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: local testing, PR review comments, CI logs, and visual browser validation. There is no overlap, so an agent can easily distinguish them.
Three tools follow a verb_noun pattern (execute_, github_fetch_, run_), but 'github_address_review_comments' breaks the pattern—it reads as a noun phrase with 'address' as a verb ambiguous. This inconsistency reduces predictability.
With 4 tools, the server is tightly scoped to core frontend engineering feedback loops: local tests, review comments, CI logs, and visual validation. No tool feels redundant or missing.
The set covers the primary stages of a frontend CI/CD workflow (test, review, CI, visual). A minor gap is the absence of a tool to directly apply generated fixes, but the agent can use existing tools iteratively.
Related MCP Connectors
MCP server for Mint — AI-powered QA that runs your app in a real browser on every PR.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseCqualityAmaintenanceA production-grade MCP server that turns natural language intent into fully-architected, accessible, production-ready UI code through a 7-step agentic pipeline.201Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that equips AI agents with dev workflow tools including GitHub project management, conventional commits, visual regression testing, Jira/Confluence integration, and a persistent memory knowledge graph.11 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents real browser capabilities including screenshotting, action execution, data extraction, and multi-persona auditing for frontend validation.63 npm6MIT
- AlicenseCqualityBmaintenanceAn MCP server implementing Spec-Driven Development workflows for AI-agent CLIs and IDEs like Claude Code and Cursor, enabling spec-first development with automated workflow guidance and quality checks.17112 npm54MIT