Figma Context MCP vs OpenFab

A side-by-side look at the Figma Context MCP and OpenFab MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Figma Context MCP logoFigma Context MCPArchitecture & Design · Local subprocess (stdio)Provide coding agents direct access to Figma data to help them one-shot design implementation.71GreatAuth: api key requiredOpenFab logoOpenFabIndustrial & IoT · Remote HTTP/SSEExperimental sandbox: custom-manufacturing quotes, lead time, DFM. Not a real supplier.51GoodAuth: not declared

Verdict: choose Figma Context MCP for architecture & design work as a local process; choose OpenFab for industrial & iot over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Figma Context MCP logoChoose Figma Context MCP when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: FIGMA_API_KEY, PORT.
  • You want tools like get_figma_data, download_figma_images.
Explore Figma Context MCP

OpenFab logoChoose OpenFab when

  • You need dedicated capabilities in the Industrial & IoT domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like discover_capabilities, request_quote, refine_quote.
Explore OpenFab

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFigma Context MCP logoFigma Context MCPOpenFab logoOpenFab
CategoryArchitecture & DesignIndustrial & IoT
Quality signal71/100 · Great51/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthAPI key requiredNot declared
PricingFreeNot declared
Required env varsFIGMA_API_KEYPORTNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars16,0680
Directory activity 10 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools27

Tools & capabilities

Figma Context MCP tools 2

  • get_figma_dataGet comprehensive Figma file data including layout, content, visuals, and component information
  • download_figma_imagesDownload SVG and PNG images used in a Figma file based on the IDs of image or icon nodes. Images will be saved relative to the server's image directory: /home/user

OpenFab tools 7

  • discover_capabilitiesList supported manufacturing processes, materials, and the fields an estimate accepts.
  • request_quoteGet an instant cost estimate for a custom manufactured part. Returns unit price, total, lead time, and assumptions. Indicative and non-binding.
  • refine_quoteRefine a previous estimate (change quantity, material, tolerance, finish) by passing its quote_token.
  • get_lead_timeEstimated production lead time in days, by process and quantity.
  • dfm_feedbackRule-based design-for-manufacturability feedback for a part specification.
  • estimate_bomEstimate costs for a multi-part bill of materials in one call. Each part: {process, quantity, material?, bounding_box_mm?, tolerance_mm?, finish?}. Returns per-line estimates, a BOM total, and the longest lead time. Indicative and non-binding. Max 50 lines.
  • compare_processesCompare cost and lead time for one part across manufacturing processes. Provide 2-8 process names and a quantity; returns per-process estimates sorted by total cost, plus a lowest-cost / shortest-lead-time note. Indicative and non-binding.

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 Context MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "glips-figma-context-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "figma-developer-mcp"
      ],
      "env": {
        "FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE",
        "PORT": "YOUR_PORT_HERE"
      }
    }
  }
}

OpenFab

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "openfab": {
      "url": "https://openfab-22100483453.us-central1.run.app/mcp/"
    }
  }
}

Frequently asked questions

Figma Context MCP is categorized under Architecture & Design and uses a local stdio subprocess. OpenFab belongs to Industrial & IoT and uses a remote HTTP/SSE transport. Pick Figma Context MCP for architecture & design work and OpenFab for industrial & iot.

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 Context MCP is listed as free. Auth: api key required. OpenFab has no declared pricing — check the project's own site. 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 glips-figma-context-mcp and openfab as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Figma Context MCP has a quality signal of 71/100 (Great) with 10 views, 0 installs and 16,068 GitHub stars. OpenFab has 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars.