Is this an official Figma MCP server?

No. It is Memtro's MCP server with Memtro's Figma connector behind it: the connector reads Figma through its API with the credentials you connect on Dashboard → Connections, and Figma publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Figma?

Only when you ask, and only what it has been granted: post a comment on a file, or reply to an existing comment; delete a comment you wrote; add or remove your emoji reaction on a comment; attach, rename, repoint or remove a Dev Mode link on a layer. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Documents and wikis

Figma MCP server

Figma in any MCP client, through Memtro: Figma does not publish this server. Memtro's Figma connector reads Figma through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Figma: a team's projects and their files, a file's pages, version history and comment threads with who said what and what is resolved, and the components and styles it publishes, and the Dev Mode links on its layers; can also post, reply to or delete a comment, react to one, and attach, change or remove a Dev Mode link (ticket, PR, docs) on a layer, when you ask.

Reads

figma_meThe Figma account the token belongs to (handle, email) and the connection's default team.
figma_projectsThe projects in a Figma team (id, name, link).
figma_project_filesThe files in a Figma project: key, name, when last modified, branches and link.
figma_fileA Figma file's metadata by key or URL: name, editor type (figma, figjam, slides…), last modified, current version id, your role on it, its pages…
figma_file_versionsA Figma file's version history, newest first: version id, when, who saved it, and the label and description for named versions.
figma_file_commentsThe comment threads on a Figma file: each root comment with its number, author, time, the node it is pinned to, whether it is resolved…
figma_file_componentsThe components and styles a Figma file publishes to its team library: name, description, type (for styles: FILL, TEXT, EFFECT, GRID)…
figma_dev_resourcesThe Dev Mode links (tickets, PRs, docs) attached to layers in a Figma file: id, name, url and the node each is on.

Acts, when you ask

These change something in Figma. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

figma_post_commentPosts a comment on a Figma file, as the token's owner, visible to everyone with access to the file and notifying whoever follows its comments.
figma_delete_commentDeletes a comment from a Figma file.
figma_react_to_commentAdds (or, with remove: true, takes back) the token owner's emoji reaction on a Figma comment, visible to everyone on the file.
figma_create_dev_resourceAttaches a Dev Mode link (a ticket, PR or doc, by name and https URL) to a layer in a Figma file, shown to everyone who inspects that layer.
figma_update_dev_resourceRenames a Dev Mode link on a Figma layer or points it at a different https URL.
figma_delete_dev_resourceRemoves a Dev Mode link from a layer in a Figma file.

Connect it

First connect Figma on Dashboard → Connections, then add Memtro to your client once. The Figma tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Figma connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Which comments on the Checkout redesign file are still unresolved, and who left them?
› What changed in the Design system file this week, and who saved the versions?
› Which files in the Mobile app project were modified since Monday?
› List the colour styles the Design system publishes
› Reply to Ana's comment on the Onboarding file that the copy is approved

Questions

Is this an official Figma MCP server?: No. It is Memtro's MCP server with Memtro's Figma connector behind it: the connector reads Figma through its API with the credentials you connect on Dashboard → Connections, and Figma publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Figma?: Only when you ask, and only what it has been granted: post a comment on a file, or reply to an existing comment; delete a comment you wrote; add or remove your emoji reaction on a comment; attach, rename, repoint or remove a Dev Mode link on a layer. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.