Figma

Catalog name figma. A remote MCP server for your Figma files.

What it’s for

Give an agent a picture of a design and it guesses: it approximates the spacing, picks the colour by eye, and writes a component the design system already has. With this connector it reads the frame instead, including the components that frame uses and the design tokens behind its values.

It can also write to the canvas, so an agent can put a screen back into Figma. That changes a file your team shares, with the rights of the account you sign in with, which is the same arrangement as every other connector here.

Add it

At init, or to an existing workbench:

monoceros init acme --with-mcp-servers=figma

monoceros add-mcp-server acme figma

Then apply:

monoceros apply acme

Signing in

There is no key to fill. The yml entry is one line and you sign in once from inside the container:

mcpServers:
  - name: figma

The per-agent step is in Servers that sign in.

Where it runs

Remote (http), at https://mcp.figma.com/mcp, which is Figma’s hosted server and works on every seat and plan.

Figma also ships a second server that runs inside the Figma desktop app on 127.0.0.1:3845. That one is not usable from a workbench: your container has no route to your host’s loopback, deliberately. The hosted server needs no desktop app and is the wider of the two anyway.

Verify it

monoceros check acme

MCP servers
  figma → Claude Code
      signs in interactively; authenticate once inside the container

That line means the server is registered with every agent and waiting for a sign-in. Once you have signed in, give the agent a Figma frame link and ask which components it uses.

Remove it

monoceros remove-mcp-server acme figma