Figma Edit MCP vs Codesign
A side-by-side look at the Figma Edit MCP and Codesign MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figma Edit MCP for architecture & design work as a local process; choose Codesign for architecture & design as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Figma Edit MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- You want tools like
page_info, node_info, node_transform.
Choose Codesign when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 59/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 14 | 42 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 45 | Not listed |
| Full listing | View Figma Edit MCP | View Codesign |
Tools & capabilities
Figma Edit MCP tools 45
page_infoList the document's pages; with `pageIds`, return those pages and their top-level childrennode_infoRead one or more nodes — recursive traversal with `properties`, `filter`, and `maxDepth` (the workhorse read; also returns bound variables / explicit modes)node_transformMove and/or resize a node by setting absolute `x` / `y` / `width` / `heightnode_renameRename a nodenode_deleteDelete one or more nodes in a single validated batchnode_cloneDuplicate a node, optionally at a new positionview_navigateNavigate the editor view to a page or node(s)node_groupWrap nodes in a new groupnode_ungroupDissolve a group, promoting its childrennode_flattenFlatten a node and its children into a single vectornode_insert_childReparent a node under a new parent at an optional indexnode_set_auto_layoutConfigure a frame's auto-layout (mode, padding, spacing, alignment, sizing)- +33 more on the listing page
Codesign tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Figma Edit MCP
{
"mcpServers": {
"figma-edit-mcp": {
"command": "npx",
"args": [
"-y",
"--package",
"figma-edit-mcp",
"figma-edit-mcp-socket"
]
}
}
}
Codesign
{
"mcpServers": {
"codesign": {
"command": "npx",
"args": [
"-y",
"@imgly/codesign-mcp@0.5.1"
]
}
}
}
Frequently asked questions
Figma Edit MCP is categorized under Architecture & Design and uses a local stdio subprocess. Codesign belongs to Architecture & Design and uses a local stdio subprocess. Pick Figma Edit MCP for architecture & design work and Codesign for architecture & design.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Figma Edit MCP has no declared pricing — check the project's own site. Codesign is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add figma-edit-mcp and codesign as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Figma Edit MCP has a quality signal of 59/100 (Good) with 4 views, 0 installs and 14 GitHub stars. Codesign has 49/100 (Fair) with 0 views, 0 installs and 42 GitHub stars.