A
licenseNot graded
qualityC
maintenanceA local conversational writing canvas that provides an MCP interface for agents like Codex or Claude Code to collaboratively read, write, and manage pages and assets in real-time.
92
MIT
mcp-visual-design-studio
by borystam
Related Servers
Alternatives to mcp-visual-design-studio
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceSelf-hosted productivity suite with document, slide, and spreadsheet editors, all accessible via a single MCP endpoint for agent-native interaction.1-
- AlicenseNot gradedqualityAmaintenanceMCP server for Nyxdoc, a document system where humans and external agents collaborate on documents with version history, agent to-dos, and workspace permissions.MIT
- AlicenseNot gradedqualityBmaintenanceCreate, edit, inspect, and publish collaborative HTML documents from AI agents through the HTML Docs MCP server.4 npm3MIT
- AlicenseAqualityCmaintenanceEnables collaborative document authoring and composition with project-based organization, transforming Markdown and LaTeX content into professional PDFs with conflict-free multi-agent editing capabilities.620MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first visual workspace and MCP server for canvases built by people and agents, with a polished editor, extensions, and SQLite persistence.1,013 npmMIT
TDQS
B3.4/5.0
Scored across 29 tools
Disambiguation4/5
Tools are mostly separated by resource and lifecycle stage (design system vs document vs comment vs history), so an agent can usually pick the right one. A few pairs could be confused at a glance—asset_import vs design_system_asset_import and preview_render vs document_export—but their descriptions clarify the different targets and purposes.
Naming Consistency5/5
Almost all tool names follow a consistent resource_action snake_case pattern (design_system_read, document_create, snapshot_restore). The few plural/singular choices like comments_read vs comment_add mirror the standard list/singular pattern and do not create inconsistency.
Tool Count3/5
29 tools is noticeably heavy and exceeds the usual well-scoped range, but the server covers a broad design-studio workflow: design systems, documents, comments, history, exports, brands, and assets. Most tools have a distinct purpose, yet the overall surface feels dense and could benefit from consolidation.
Completeness4/5
The core lifecycle is well covered: design systems can be previewed/saved/applied/exported, documents can be created/read/edited/exported/duplicated, and history/snapshots/comments are handled. Minor gaps remain—there is no document delete, comment resolve/update, or asset list/delete, and the setup-export prerequisite is referenced but not exposed as a tool.
Maintenance
ActivityMaintained
ResponsivenessNo issues