Skip to main content
Glama
imgly

CoDesign

Official
by imgly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to CoDesign

  • Figma MCP Server

    Knightwxch
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables Cursor to access Figma design data via MCP, allowing it to fetch simplified layout and styling information to accurately implement designs from Figma files.
    3,063 npm
    MIT

  • design-mcp

    augustinezuka
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for design decisions during a build, providing live UI/animation library docs (via llms.txt) and a curated knowledge base of UX laws and UI conventions. It enables agents to look up real component APIs and apply design best practices, running locally via stdio or hosted on Vercel.
    0
    MIT
  • Figma MCP Server by figma

    Figma MCP Serverofficial

    figma
    F
    license
    Not graded
    quality
    B
    maintenance
    Provides Figma design context to AI agents, enabling code generation, design system integration, and canvas manipulation through MCP.
    2,101
    -

Related Servers

  • Maket

    ng-galien
    A
    license
    A
    quality
    A
    maintenance
    Local-first visual design workspace for AI assistants. Compose wireframes and branded multi-page HTML/CSS documents with live preview, annotations, brand and asset libraries, typed data collections, layout validation, PDF export, and draft-only Gmail handoff.
    16
    5 npm
    20
    MIT

  • canvy

    GIFO14
    A
    license
    Not graded
    quality
    B
    maintenance
    Provides 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.
    7 npm
    MIT

  • Tuval Studio MCP

    ariferol01
    A
    license
    C
    quality
    B
    maintenance
    Enables AI agents to autonomously create and edit graphic designs, multi-page PDF catalogs, brochures, social media assets, and slide decks on a local browser canvas. It provides vision-in-the-loop feedback, layout audits, and export capabilities for print-ready or web-ready outputs.
    53
    52 npm
    MIT

  • OpenPaper MCP Server

    arshit09
    A
    license
    Not graded
    quality
    C
    maintenance
    Lets 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.
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 19 tools

Disambiguation5/5

Each tool targets a distinct concern: revision lifecycle, asset management, auth, skills, export, or diagnostics. The asset_search/asset_add/asset_generate trio is clearly separated by operation (find/add/generate), and list/history/changes/inspect are differentiated by scope. No two tools appear to overlap in a way that would cause misselection.

Naming Consistency3/5

Bare verbs (edit, export, preview, import, list, view) coexist with prefixed names (asset_search, asset_add, asset_generate) and noun-only names (skill, history, checklist, scorecard, diagnostics). While the core verbs are recognizable and readable, there is no single predictable pattern across the set.

Tool Count3/5

At 19 tools, the server sits in the 16-25 range that feels heavy. However, the broad scope (design editing, assets, auth, skills, diagnostics, quality gates) justifies most of them, so it is borderline rather than bloated.

Completeness4/5

The design lifecycle is well covered: create (edit, import), read (inspect, preview, history, list), update (edit, rename), and export, plus asset management and quality gates. The main gap is the absence of delete/remove operations for designs or assets, and asset management lacks update/delete, but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources