Figma MCP Server vs Intangible

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

Figma MCP Server logoFigma MCP ServerArchitecture & Design · Remote HTTP/SSEThe Figma MCP server brings Figma design context directly into your AI workflow.47FairAuth: not declared
I
IntangibleArchitecture & Design · Remote HTTP/SSE
Build 3D scenes, place cameras and render shots. Previs, storyboards, set design, product and CAD.42FairAuth: not declared

Verdict: choose Figma MCP Server for architecture & design work over a hosted endpoint; choose Intangible for architecture & design over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Figma MCP Server logoChoose Figma MCP Server when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a remote HTTP/SSE transport.
Explore Figma MCP Server

I
Choose Intangible when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a remote HTTP/SSE transport.
Explore Intangible

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFigma MCP Server logoFigma MCP Server
I
Intangible
CategoryArchitecture & DesignArchitecture & Design
Quality signal47/100 · Fair42/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSERemote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2,104—
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Figma MCP Server tools

No tool names declared yet. Check the project README from the listing page.

Intangible tools

No tool names declared yet. Check the project README from the listing page.

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

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "figma-mcp-server": {
      "url": "https://mcp.figma.com/mcp"
    }
  }
}

Intangible

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "intangible": {
      "url": "https://www.intangible.ai/mcp"
    }
  }
}

Frequently asked questions

Figma MCP Server is categorized under Architecture & Design and uses a remote HTTP/SSE transport. Intangible belongs to Architecture & Design and uses a remote HTTP/SSE transport. Pick Figma MCP Server for architecture & design work and Intangible 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.

Figma MCP Server has no declared pricing — check the project's own site. Intangible 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 figma-mcp-server and intangible as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Figma MCP Server has a quality signal of 47/100 (Fair) with 2 views, 0 installs and 2,104 GitHub stars. Intangible has 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.