A
licenseNot graded
qualityC
maintenanceAn MCP server that gives AI agents real browser capabilities including screenshotting, action execution, data extraction, and multi-persona auditing for frontend validation.
75 npm
6
MIT
kiro-frontend-engineer-mcp
Related Servers
Alternatives to kiro-frontend-engineer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP 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.1 npmMIT
- 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
- AlicenseCqualityAmaintenanceAn MCP server that enables AI agents to autonomously test, debug, and analyze web interfaces visually using Playwright, with 30 tools for screenshots, workflows, performance, and visual comparison.3013 npm83ISC
- AlicenseCqualityDmaintenanceA production-grade MCP server providing an autonomous AI agent swarm, persistent semantic memory, browser automation, multi-model reasoning, and 78+ tools for AI-first testing and development.63MIT
- AlicenseCqualityAmaintenanceAn 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.16201 npm51MIT
TDQS
A3.6/5.0
Scored across 4 tools
Disambiguation5/5
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.
Naming Consistency3/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues