Axure Prototype MCP
Related Servers
Alternatives to Axure Prototype MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA read-only MCP server that extracts actual Figma prototype flows, transitions, and per-screen interactions so agents can see navigational behavior rather than infer it. It reports explicit source and destination IDs with warnings for unresolved or ambiguous destinations, without guessing or writing back to Figma.3MIT
- AlicenseAqualityDmaintenanceEnables MCP clients to read design structure, take screenshots, create nodes, and edit UI directly on Figma canvas via a bridge between MCP and Figma Desktop.10329 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Codex and other MCP clients to read a selected Figma frame from an open Chrome tab, exposing decoded design structure and layout data through read-only MCP tools.MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to inspect live browser runtime evidence, such as blocking elements and interaction surfaces, and to independently verify whether a code fix resolved the issue.9 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to control a canvas-based macOS browser for web development, allowing agents to open and interact with live pages, capture screenshots, measure elements, and manage local project workflows.5 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect live web and responsive UIs across mobile and desktop sessions, returning measured text findings on contrast ratios, touch-target sizes, overflow, and theme drift instead of screenshot guesses. It also lets a human and the agent share one live panel, so the agent can navigate, tap, and type while reading the user's pinned notes and frames.109 npmMIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct concern: session setup (axure_use_prototype), navigation (axure_list_pages), structure/layout (axure_get_page_map), pixels (axure_get_visual), and behavior (axure_get_interactions). The get_page_map vs get_visual vs get_interactions trio could superficially overlap, but the descriptions sharply differentiate geometry, imagery, and interaction evidence.
All five tools use the same axure_ prefix and snake_case verb_noun pattern (use_prototype, list_pages, get_page_map, get_visual, get_interactions). The convention is predictable throughout with no camelCase or stylistic deviations.
Five tools is well-scoped for a read-only prototype reader: one setup tool plus four complementary inspection views. No tool feels redundant and none is missing for the core purpose.
Navigation, structure, visual capture, and interaction reporting cover the read-only analysis lifecycle thoroughly, including scoping and image-optional modes. Minor gaps: no cross-page text/widget search and no explicit way to revert to the configured AXURE_URL within a session (though it expires at session end).