Tuval Studio MCP
Related Servers
Alternatives to Tuval Studio MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to act as graphic designers by generating images and social-ready visuals, with brand DNA memory, genre-aware styles, 35+ platform presets, self-critique, and version control.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to convert natural-language briefs into structured visual specs, deterministically render typography and layouts, and run constraint-aware visual QA and targeted repair for image generation.15 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to build and edit real HTML/CSS designs on a live canvas through 35 MCP tools, letting them inspect screenshots, computed styles and layout, then export production-ready React or Tailwind code. Humans can refine the same layers visually in a macOS editor.6,734 npmMIT
- AlicenseCqualityBmaintenanceEnables AI agents and users to edit images through natural language, performing layered, non-destructive operations like masks, clipping masks, blend modes, filters, generative fill, image-to-image, background removal and upscaling, either locally or via the user's own API keys. Agents can preview rendered results, measure image properties, review their own work and export finished images through 62 tools shared with the editor's UI.6250 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to collaboratively design and edit web pages on an infinite canvas using real HTML/CSS, with tools for reading, mutating, and exporting documents.387 npm1LGPL 3.0

Canvora MCPofficial
AlicenseAqualityDmaintenanceEnables AI agents to generate on-brand visuals from ideas, URLs, documents, or PDFs in over 100 formats and 150+ languages, with consistent brand kits.1612 npm1MIT
TDQS
Scored across 53 tools
The set is mostly distinct by domain and action, but there is an explicit alias (svg_add/sticker_add) and several overlapping background, asset, and export tools that could cause misselection. Descriptions help, but the sheer number of tools increases ambiguity.
Names are overwhelmingly snake_case with domain prefixes (canvas_, layer_, project_, etc.), which is predictable. Minor deviations exist: layers_get_all breaks the layer_ pattern, elements_search vs element_add_stock mix plural/singular, and sticker_add is an alias.
53 tools far exceeds the 3-15 well-scoped range and even the 25+ 'too many' threshold, representing an extreme mismatch for a single MCP server. Many tools could be consolidated, such as background setters, asset listers, and export variants.
The surface covers a wide range of design operations (canvas, layers, pages, assets, text, shapes, export, history), but has notable gaps: no tool to resize or scale a layer, no way to edit existing text content (only style), and no project load/import. These missing operations will likely cause agent dead ends.