DESIGN COLLABORATION / Figma
Figma Remote MCP
Brings Figma design context into an assistant and supports creating or editing native Figma and FigJam content in supported clients.
“Enabling the remote MCP server”
01 / THE REASONING
Why this made the selection.
- Connects design variables, components and layout context with implementation workflows.
- Current documentation explicitly covers native canvas edits, avoiding an outdated read-only description.
- Figma’s remote-install page says the hosted server reaches Figma files without the desktop app, and that only catalog clients can connect.
- The access page limits what the server can read to content the user can already view or edit, and it rate-limits read tools while saying write tools are exempt.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/ (setup, access and capability sections)
- https://developers.figma.com/docs/figma-mcp-server/rate-limits-access/ (setup, access and capability sections)
- https://developers.figma.com/docs/figma-mcp-server/ (setup, access and capability sections)
- Official MCP Registry publisher entry: endpoint matched against official setup documentation
- https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/
- https://developers.figma.com/docs/figma-mcp-server/rate-limits-access/
- https://developers.figma.com/docs/figma-mcp-server/
- https://registry.modelcontextprotocol.io/v0.1/servers?search=figma&version=latest&limit=100
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- The remote setup uses Figma OAuth and does not require the desktop application.
- Users retain their existing file view/edit permissions; tools can create and change Figma/ FigJam content.
- The remote server is documented as a hosted endpoint that does not need the Figma desktop app, and the introduction says it has the broadest feature set.
- Connection is limited to catalog clients, and each user normally completes an OAuth login. The user can only access Figma content they already have permission to view or edit.
- Rate limits apply to tools that read Figma data. The page says some write tools are exempt. The registry name com.figma.mcp/mcp describes bringing Figma design context into an AI workflow.
- Remote tools can write native frames, components, variables and auto layout as well as read design context.
Not established by this review
- Authentication, service availability and tool execution were not tested.
- The hosted implementation source and licence were not established.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
claude mcp add --transport http figma https://mcp.figma.com/mcp Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- Use a listed client and add https://mcp.figma.com/mcp, then complete OAuth.
- Confirm the Figma account, seat and target file permissions before requesting edits.
- The command above is the guide’s manual Claude Code setup; the guide prefers the Figma plugin. It was not run.
Before you start
- An eligible Figma account/seat, file access and a supported MCP client.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"inputs": [],
"servers": {
"figma": {
"url": "https://mcp.figma.com/mcp",
"type": "http"
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/
Supports: summary, whySelected, bestFor, limitations, review, compatibility, install, access, transports, configExample
https://developers.figma.com/docs/figma-mcp-server/rate-limits-access/
Supports: summary, whySelected, bestFor, limitations, review, compatibility, install, access, transports, configExample
https://developers.figma.com/docs/figma-mcp-server/
Supports: summary, whySelected, bestFor, limitations, review, compatibility, install, access, transports, configExample
https://registry.modelcontextprotocol.io/v0.1/servers?search=figma&version=latest&limit=100
Supports: transports