What is the key difference between Figma Use and MetaDock?

Figma Use belongs to the Developer Tools category with local stdio execution, while MetaDock belongs to the Developer Tools category with cloud HTTP/SSE execution.

How do I install Figma Use or MetaDock in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Figma Use and MetaDock free or paid?

Figma Use operates under a Free / Open Source model (No auth required). MetaDock operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Figma Use lists 6 tools with 1 views and 590 GitHub stars. MetaDock lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Figma Use and MetaDock together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Figma Use or MetaDock in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Figma Use and MetaDock free to use, or do they require API keys?

Figma Use is listed under a Free / Open Source model with No auth required . MetaDock operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Figma Use and MetaDock at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both dannote-figma-use and metadock as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Figma Use has a Quality Score of 52 /100 ( Good ) with 1 views, 0 installs, and 590 GitHub stars. MetaDock holds a Quality Score of 30 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Figma Use vs MetaDock

In-depth architectural comparison of the Figma Use and MetaDock 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

Figma Use

Developer Tools · Local stdio

Quality: 52/100 (Good) | Auth: No auth required

MetaDock

Developer Tools · Remote HTTP/SSE

Quality: 30/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Figma Use if you need specialized Developer Tools tools running via a local process. Choose MetaDock if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Figma Use 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).
You have access to required keys: FIGMA_USE_REMOTE_DEBUGGING_PORT.
Primary tools included: Imperative CLI commands for Figma object creation and styling, Declarative JSX rendering of Figma layouts and components, Support for 80+ design operations including auto-layout and variables.

Explore Figma Use Details

Choose MetaDock when:

You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore MetaDock Details

Feature & Specification Comparison

Specification	Figma Use dannote Developer Tools	M MetaDock Developer Tools
Summary	Full Figma control: create shapes, text, components, set styles, auto-layout, variables, export. 80+ tools.	Control the MetaDock desktop workspace over MCP: browsers, layouts, bookmarks, downloads, and more.
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Figma Use Tools (6)

Imperative CLI commands for Figma object creation and styling

Declarative JSX rendering of Figma layouts and components

Support for 80+ design operations including auto-layout and variables

Icon insertion from Iconify without manual downloads

Export Figma nodes to JSX and Storybook stories

Component and variant definition with typed props

MetaDock Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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).

Figma Use Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "dannote-figma-use": {
      "command": "npx",
      "args": [
        "-y",
        "figma-use"
      ],
      "env": {
        "FIGMA_USE_REMOTE_DEBUGGING_PORT": "YOUR_FIGMA_USE_REMOTE_DEBUGGING_PORT_HERE"
      }
    }
  }
}

MetaDock Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "metadock": {
      "url": "https://metadock.app/mcp"
    }
  }
}

Frequently Asked Questions

Figma Use is categorized under Developer Tools and uses a local stdio subprocess. In contrast, MetaDock belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Figma Use when you need capabilities focused on developer tools and MetaDock when you require tools for developer tools.

More alternatives to Figma Use More alternatives to MetaDock Developer Tools category hub