kiro-frontend-engineer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| execute_playwright_testA | Run local Playwright E2E test suites on generated components. Captures terminal logs, test pass/fail results, and error screenshots. |
| github_fetch_ci_logsA | Fetch CI build/lint failure logs from GitHub Actions. Used for self-healing: agent reads failures and generates fixes. |
| github_address_review_commentsC | Fetch open PR review comments from GitHub to feed back into agent context for automated resolution. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ui-ux-pro-max | System prompt that instructs the LLM to analyze a layout spec/image and generate rich, fully dynamic, non-generic frontend component blueprints |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| React & Next.js Best Practices | Structured guidelines on Server/Client components, state isolation, and TypeScript patterns |
| Web Design Inspection Checklist | Product-grade QA checklist for accessibility, layout shifting, edge-case text truncation |
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.