Frontend Review MCP
Related Servers
Alternatives to Frontend Review MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityNot gradedmaintenanceAn MCP server that visually reviews UI edit requests by comparing screenshots before and after edits, ensuring changes satisfy user requests.18 npm31-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that measures how faithfully one UI reproduces another, returning a score and actionable findings for improvement.1MIT

mcp-reviewofficial
AlicenseAqualityAmaintenanceAn MCP server for in-loop design review of web previews. It enables agents to submit a preview URL, receive structured findings with suggested fixes, and recheck after applying changes, while never editing code itself.51MIT- FlicenseAqualityNot gradedmaintenanceAn MCP server that enables users to review and refine AI outputs through a local web UI, returning feedback as free tool call results to save on GitHub Copilot premium requests. It allows for multiple rounds of iterative improvements within a single request session.130-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides agentic vision capabilities for visual regression testing by capturing and comparing screenshots using Gemini Flash. It enables users to detect UI changes and conduct conversational investigations to distinguish between intended and unintended visual modifications.-
- AlicenseAqualityDmaintenanceAn MCP server that enables automated quality control for generated images, evaluating them against reference images and rules to return structured scores and issues.2MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool 'reviewEdit' has a single, clearly defined purpose focused on visual review of UI edits.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'reviewEdit' follows a clear verb_noun pattern, and there are no other tools to compare it against for inconsistency.
A single tool is generally too few for a server's purpose, as it limits functionality and can feel thin. For a 'Frontend Review MCP', one might expect additional tools for tasks like listing reviews, managing requests, or handling different types of edits, making this count inappropriate for the apparent scope.
The tool set is severely incomplete for a frontend review domain. While 'reviewEdit' handles the core review action, there are obvious gaps such as tools for creating, listing, updating, or deleting review requests, which would be essential for a complete workflow and could cause agent failures due to missing operations.