CodemagicMcp vs Figma — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
CodemagicMcp vs Figma
In-depth architectural comparison of the CodemagicMcp and Figma MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
CodemagicMcp
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Figma
Developer Tools · Local stdio
Quality: 39/100 (Fair) | Auth: No auth required
Verdict Summary: Choose CodemagicMcp if you need specialized Developer Tools tools running via a local process. Choose Figma if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose CodemagicMcp when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
CodemagicMcp is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Figma belongs to Developer Tools using local stdio subprocess. Select CodemagicMcp when you need capabilities focused on developer tools and Figma when you require tools for developer tools.
Get a step-by-step status summary of a build (filterable by status)
get_step_logs
Get raw logs inline or create/update a managed temp file for a specific build step
get_step_log_artifact
Check whether a managed local step-log artifact still exists for a specific build step
list_build_artifacts
List all artifacts produced by a build
get_artifact_url
Get the download URL for a build artifact
+7 more tools listed on main page
Figma Tools (5)
get_me
Get the signed-in Figma user: id, email, handle, and avatar image URL. Use to identify whose Figma account is connected.
get_file
Get a compact summary of a Figma design file by its file key: name, last modified time, version, editor type, role, thumbnail URL, and the list of top-level pages (id, name, type, child count). Use to understand the structure of a Figma design file without fetching the full node tree.
list_comments
List comments on a Figma design file. Returns each comment's id, message, author handle, created time, and resolved time. Use to review feedback and discussion on a design.
get_file_nodes
Get specific nodes from a Figma design file by their node ids. Returns a compact map of node id to { name, type }. Use to inspect particular frames, components, or layers within a design file.
get_file_images
Render images of specific nodes in a Figma design file. Returns a map of node id to a rendered image URL. Use to get visual previews (PNG, SVG, or JPG) of frames, components, or layers from a design.