Brilliant MCP
OfficialRelated Servers
Alternatives to Brilliant MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI coding agents to read and write to a local-first HTML/CSS design canvas, bridging visual design and code generation.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to read and write Figma designs through a local WebSocket relay, turning Figma selections into framework-aware code and building/editing designs directly on the canvas. Provides 112 MCP tools for bidirectional design-code workflows with support for any MCP client.MIT
- AlicenseNot gradedqualityDmaintenanceA MCP server that bridges web canvas with local Codex/Claude, exposing 23 tools for reading, creating, modifying, connecting, and generating canvas content via local HTTP bridge and stdio MCP.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceOpen-source multiplayer design canvas (alternative to Paper.design) with a built-in MCP server. Agents create and stream HTML artboards live next to human collaborators, review them via screenshots, comment on elements, search icons/images/logos and follow shared design guidelines.65 npm2,046AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceProvides an editable, locally persisted design canvas inside the Codex desktop app, letting an agent create and modify frames, text, vectors, groups, and layouts through MCP tools. Humans can review, drag, pan, zoom, and undo alongside the agent, with edits autosaved to disk and exportable as images, SVG, design JSX, or .fig backups.5 npmMIT
- AlicenseNot gradedqualityBmaintenanceLets AI agents design alongside you on a live canvas by reading, writing, styling and inspecting real HTML/CSS designs, capturing pixel-accurate screenshots, exporting assets and PDFs, and managing design tokens, comments and files. It exposes the same 37 tool names, parameters and response shapes as Paper, so existing agent prompts and workflows run against a local canvas over Streamable HTTP or stdio.1MIT
TDQS
Scored across 25 tools
The active tools mostly target distinct operations, but five retired aliases (read_objects_result, objects_result, create_modify_elements, create_html, lookup) still appear alongside the tools they redirect to. There is also potential overlap between edit and execute_commands, and multiple export/capture/render image tools require careful reading to distinguish.
Names are consistently snake_case, but verb conventions are mixed: single verbs (read, edit, export, wait, init), verb_noun patterns, noun_result names, and compound verbs like create_modify_elements. The names remain readable, but the set does not follow one predictable pattern.
At 25 tools the surface is heavy, and the count is inflated by five retired tools that do not earn their place. The remaining active tools span a broad design-editor domain, so the count is not extreme, but it is borderline for the scope.
The set covers the core design lifecycle well: session init, project listing/binding, document read/edit, selection, export, knowledge loading, image generation/processing, and UI capture. Minor gaps remain around project creation/deletion/publishing and explicit document lifecycle management.