CI Control Bridge vs Figma Context MCP

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

CI Control Bridge logoCI Control BridgeHome Automation · Local subprocess (stdio)Control monitor brightness, contrast, power and input via DDC/CI with MCP and MQTT support.55GoodAuth: api key requiredFigma 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 required

Verdict: choose CI Control Bridge for home automation work as a local process; choose Figma Context MCP 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?

CI Control Bridge logoChoose CI Control Bridge when

  • You need dedicated capabilities in the Home Automation domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: DDC_API_KEY, MQTT_ENABLED, MQTT_HOST.
  • You want tools like get_vcp_code, set_vcp_code, get_brightness.
Explore CI Control Bridge

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCI Control Bridge logoCI Control BridgeFigma Context MCP logoFigma Context MCP
CategoryHome AutomationArchitecture & Design
Quality signal55/100 · Good71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredAPI key required
PricingFreeFree
Required env varsDDC_API_KEYMQTT_ENABLEDMQTT_HOSTFIGMA_API_KEYPORT
Verified ownerCommunity listingCommunity listing
GitHub stars516,068
Directory activity 4 views 0 installs 0 upvotes 10 views 0 installs 0 upvotes
Tools52

Tools & capabilities

CI Control Bridge tools 5

  • get_vcp_codeRead a specific VCP code value
  • set_vcp_codeWrite a value to a VCP code
  • get_brightnessGet monitor brightness (0-100)
  • set_brightnessSet monitor brightness (0-100)
  • refresh_monitorsRe-scan monitors and VCP 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

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.

CI Control Bridge

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ddc-ci-control-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "ddc-ci-control-bridge"
      ],
      "env": {
        "DDC_API_KEY": "YOUR_DDC_API_KEY_HERE",
        "MQTT_ENABLED": "YOUR_MQTT_ENABLED_HERE",
        "MQTT_HOST": "YOUR_MQTT_HOST_HERE"
      }
    }
  }
}

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"
      }
    }
  }
}

Frequently asked questions

CI Control Bridge is categorized under Home Automation and uses a local stdio subprocess. Figma Context MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick CI Control Bridge for home automation work and Figma Context MCP 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.

CI Control Bridge is listed as free. Auth: api key required. Figma Context MCP is listed as free. Auth: api key required. 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 ddc-ci-control-bridge and glips-figma-context-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, CI Control Bridge has a quality signal of 55/100 (Good) with 4 views, 0 installs and 5 GitHub stars. Figma Context MCP has 71/100 (Great) with 10 views, 0 installs and 16,068 GitHub stars.