return_rp
Related Servers
Alternatives to return_rp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to build and edit a local-first design board of HTML screens, flows, components, design-system pages, and plan tables, then review it in a browser with undo/restore, rendering, and export tools.MIT

Screenbookofficial
AlicenseNot gradedqualityBmaintenanceEnables an AI agent to read and write a product's design screens on a shared, versioned canvas: creating and editing HTML screens and shared parts, taking screenshots, linking flows, posting comments and annotations, and opening or approving proposals. Every drawing is returned with its screenshot so the agent can see what it produced, letting screens persist and evolve across chats instead of starting from zero.1MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to write AI-generated designs into design-tool canvases (MasterGo, Penpot) as native editable layers, and to read canvas selections back out as HTML + Tailwind, design tokens, and SVG assets. Runs locally with progressive tool disclosure and structurally truncated results so large design files stay within an agent's context budget.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceConnects AI agents to Flato's native editable canvas for design, enabling creation, inspection, revision, export, and visual QA of projects.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to draw on a self-hosted canvas by creating and editing frames, text, shapes, images, and SVGs with auto-layout, then inspecting, exporting, and sharing the results. Also supports live viewing of agent edits, pinned comments, screenshots, and revision history so people and agents can collaborate on boards.747 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to create interactive prototypes, annotate UI elements, generate PRDs, and track which annotations and documents need updating after changes.222MIT
TDQS
Scored across 87 tools
The 87-tool surface contains several near-duplicate paths: rename_widget vs name_widget, edit_text vs set_widget_text vs set_widget_richtext, axure_open vs studio_open_project, verify vs rp_read vs diagnose_prototype, and sync_prototype vs studio_sync_native. Descriptions are detailed, but the overlap across native, RP/1, Studio, and CLI-style workflows makes misselection likely.
All tools use snake_case, avoiding camelCase chaos, but verb order is mixed: create_/set_/add_/remove_/clone_ coexist with noun-first axure_open, jobs_list, rp_read and bare verify/locate/inspect. The large studio_* prefix group is internally consistent, but the overall convention is only partly predictable.
Eighty-seven tools far exceeds a well-scoped surface, even for a complex Axure automation domain. The count is an extreme mismatch with the typical 3-15 range and creates many parallel entry points for similar tasks.
Coverage is broad: creation, editing, interactions, panels, masters, verification, export, sync, image import, design review, and GUI roundtrip are all represented. However direct lifecycle operations for pages, masters, global variables, and custom styles are missing or only indirect, leaving notable gaps despite the huge surface.