Figma Dev Mode MCP Server
Figma's hosted MCP (mcp.figma.com/mcp) is the remote twin of the desktop Dev Mode MCP server โ it streams design context, variables and component mappings to agents after OAuth.
- Provider
- Figma โ
- Categories
- ๐จ Design & UI/UX
ไธญๆ็ฎไป
Figma ๅฎๆน่ฟ็จ MCP ๆๅกๅจใAI ไปฃ็ๅฏ่ทๅ่ฎพ่ฎกไธไธๆใๅ้ๅฎไนใCode Connect ๆ ๅฐๅๆชๅพใ
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"figma": {
"url": "https://mcp.figma.com/mcp"
}
}
}claude mcp add --transport http figma https://mcp.figma.com/mcp
Or add to .vscode/mcp.json:
{
"servers": {
"figma": {
"type": "http",
"url": "https://mcp.figma.com/mcp"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://mcp.figma.com/mcp - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"figma": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.figma.com/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"figma": {
"serverUrl": "https://mcp.figma.com/mcp"
}
}
}๐งฐ Tools exposed by Figma Dev Mode MCP (4)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| get_design_context | ๐ข Read | Generate structured design context (layout, styles, components) for a Figma selection or link. | fileKey*: stringnodeId: string |
| get_variable_defs | ๐ข Read | Get variable and style definitions used in a Figma file or selection. | fileKey*: stringnodeId: string |
| get_code_connect_map | ๐ข Read | Get the Code Connect mapping between Figma components and code components. | fileKey*: stringnodeId: string |
| get_screenshot | ๐ข Read | Render a screenshot of a Figma node for visual reference. | fileKey*: stringnodeId: string |
๐ OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- โ Supported
- PKCE S256
- โ Supported
- Scopes
file_read- Protected resource metadata
- https://mcp.figma.com/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ Guide
Figma Dev Mode MCP โ Remote MCP Server
Figma's remote MCP brings the Dev Mode MCP toolset โ design context extraction, variable definitions, Code Connect mappings and screenshots โ to web-based agents that can't talk to the local desktop server. Access is scoped by Figma OAuth, so agents see the files and selections your account can see.
Endpoint & Transport
- Endpoint URL:
https://mcp.figma.com/mcp - Transport: Streamable HTTP
Authentication
Figma Dev Mode MCP uses OAuth 2.1 โ the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ PKCE and Dynamic Client Registration, so no manual client setup is needed โ and simply open a browser consent screen.
Available Tools (4)
| Tool | Safety | Description |
|---|---|---|
get_design_context |
read | Generate structured design context (layout, styles, components) for a Figma selection or link. |
get_variable_defs |
read | Get variable and style definitions used in a Figma file or selection. |
get_code_connect_map |
read | Get the Code Connect mapping between Figma components and code components. |
get_screenshot |
read | Render a screenshot of a Figma node for visual reference. |
Connect in 30 Seconds
Claude Code โ one command:
claude mcp add --transport http figma https://mcp.figma.com/mcp
Cursor โ add to ~/.cursor/mcp.json:
{ "mcpServers": { "figma": { "url": "https://mcp.figma.com/mcp" } } }
VS Code โ add to .vscode/mcp.json:
{ "servers": { "figma": { "type": "http", "url": "https://mcp.figma.com/mcp" } } }
Claude Desktop & stdio clients โ bridge with mcp-remote:
{ "mcpServers": { "figma": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.figma.com/mcp"] } } }
On first connect your client opens a browser OAuth consent screen โ approve it and tools become available immediately.
Troubleshooting
- 401 Unauthorized on connect โ that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely. - Requires a Figma account; Dev Mode seat requirements follow Figma's plan rules.
- If your agent runs locally, the desktop Dev Mode MCP server (http://127.0.0.1:3845/mcp) is an alternative without OAuth.
๐ How to Connect
- Copy the Figma Dev Mode MCP endpoint URLThe remote endpoint is https://mcp.figma.com/mcp.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http figma https://mcp.figma.com/mcp. Cursor: add"figma": { "url": "https://mcp.figma.com/mcp" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Figma consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://mcp.figma.com/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Figma Dev Mode MCP's 4 tools respond.
โ FAQ
What is the Figma Dev Mode MCP remote MCP endpoint?
The primary endpoint is https://mcp.figma.com/mcp. It is an official first-party server operated by Figma, speaking the Streamable HTTP transport.
How do I authenticate with Figma Dev Mode MCP?
Figma Dev Mode MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.
I'm getting a 401 Unauthorized from Figma Dev Mode MCP โ what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with Figma Dev Mode MCP?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http figma https://mcp.figma.com/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, and Claude Desktop via the `mcp-remote` bridge.
What tools does Figma Dev Mode MCP expose?
4 tools are cataloged in this directory โ including `get_design_context`, `get_variable_defs`, `get_code_connect_map` and more. Use our online inspector to fetch the live tool list straight from the endpoint.