Icon Composer MCP vs Figwright

In-depth architectural comparison of the Icon Composer MCP and Figwright 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.

Which MCP Server Should You Choose?

Choose Icon Composer MCP when:

• You need dedicated capabilities in the Architecture & Design domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: create_icon, add_layer_to_icon, remove_layer.

Explore Icon Composer MCP Details

Choose Figwright when:

• You need dedicated capabilities in the Architecture & Design domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Read, Write, Grounding.

Explore Figwright Details

Feature & Specification Comparison

Specification	Icon Composer MCP ethbak Architecture & Design	Figwright awdr74100 Architecture & Design
Summary
Category & Scope	Architecture & Design	Architecture & Design

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "ethbak-icon-composer-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "icon-composer-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "awdr74100-figwright": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

Related MCP Server Comparisons