Skip to content
Figma logo

Figma MCP server

Collaborative interface design tool

Figma is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
4
Works with
Any MCP client
Auth
OAuth 2.0
License
MIT, open source
Updated
September 2026

About the Figma MCP server

Connect Figma once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Figma and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Figma tools your AI can run

Once connected, your assistant can call any of these Figma actions by asking in plain language.

  • Get File

    Get file

    1 field

  • Get File Comments

    Get file comments

    1 field

  • Post File Comment

    Post file comment

    2 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

Figma events your agent can watch

These start a run the moment something happens in Figma, so work gets picked up on its own.

  • New Comment (Figma Professional plan only)

    Triggers when a new comment is posted

    1 field

Give your assistant Figma

Connect Figma once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Figma MCP, answered.

No. That is the point of it. One Activepieces server exposes Figma alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Figma in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 4 tools, including Get File, Get File Comments, Post File Comment, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.