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 "Install 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-mcprun 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: VibeServe
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
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Josephjyinn516/kiro-frontend-engineer-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server