Figma Make can connect to external tools via the Model Context Protocol (MCP), allowing you to work with documents, tasks, and data from other apps as context for your app or prototype.
For example, you might connect Figma Make to Notion to import a product requirements document (PRD) directly into Figma’s chat and ask Make to use it as the source for building a prototype. If the PRD changes, simply run the connector again to refresh the context and update the prototype. You can also write content back to Notion—like generating a list of acceptance criteria—by enabling the write tools in the connector’s settings.
What’s the difference between MCP in Figma Make and the Figma MCP server?
When you connect external tools in Figma Make, it acts as an MCP client. The client calls tools hosted on an MCP server—for example, the Notion or Asana connectors—to read or write data from that source. Based on your prompt, Figma AI decides which connector and tools to use.
By contrast, the Figma MCP server includes a list of tools that makes your file data available to other MCP clients.
What connectors are available
Figma currently supports a limited set of connectors. These MCP servers have been vetted by our team to ensure they meet Figma’s security and privacy standards.
Notion
- Access Notion pages and databases directly from Figma Make to bring context, specs, and notes into your design flow.
- Create and update Notion docs, so your design documentation stays organized and always in sync.
Asana
- Access Asana tasks and projects from Figma Make to track progress and team priorities in real time.
- Create and manage Asana tasks, so you can keep projects aligned from concept to completion.
Linear
- Access Linear issues, projects, and documents from Figma Make to generate prototypes with relevant context.
- Create and manage Linear issues and projects, so you can turn your prototypes into planned work.
GitHub
- Access GitHub repositories, issues, and pull requests to keep design work tied to your codebase.
- Create and summarize GitHub issues and PRs from within Figma, so design changes translate directly into development action.
Atlassian
- Access Confluence pages and documentation from Figma Make to use specs and shared decisions as context for your design.
- Create and edit Confluence pages right from your workspace, so every update stays connected to the design work it supports.
- Access Jira issues and epics from Figma Make to connect designs to your engineering workflows.
- Create and transition Jira tasks without context switching, so teams can move seamlessly from design exploration to development execution
- Access Compass components, services, and scorecards from Figma Make to understand how your designs connect to your engineering ecosystem.
- Create and update Compass components without leaving Figma, so every prototype stays linked to the systems that bring it to life.
monday.com
- Access monday.com boards and items from Figma Make to stay aligned with team planning and priorities.
- Create and manage updates, so your work stays visible and connected across every team.
Note: Interested in connecting your product to Figma Make? We’re currently collecting expressions of interest for new partnerships. If that sounds like you, please share a few details about your product and use case with us.
Add a connector
Each person needs to add and authenticate to the connectors they’d like to use.
To add a connector, you’ll first need to authenticate. For example, when adding Notion, you’ll select your workspace and approve access permissions.
- From the chat box, click Add context and select Add connector.
- Browse the list of available connectors.
- Click Add next to the connector you want to use.
- Follow the prompts to authenticate through the external tool’s OAuth flow.
- Once connected, click Add context to confirm the connector appears in the list.
Note: If you don’t have the option to Add connector, an admin may have disabled this feature for your organization.
Use a connector in chat
When a connector and its tools are enabled for the current chat, you can call it naturally within the flow of conversation.
- Confirm the connector is enabled in your current conversation. From the chat box, click Add context and select your connector. In the settings window, make sure the relevant read and write tools are enabled.
- Type a prompt that references the connector. For example, paste an Asana link and write “Use the specs in this Asana project to create a first-draft prototype”.
- If your prompt requires a connector, Figma AI will show which connector and tool it plans to call and ask for consent. Click Run to proceed. You can manage individual tools and their permissions from the connector settings.
If the source content changes, just run the connector again to pull in the latest context.
Manage connector settings
Some connectors include multiple MCP tools. These tools perform different functions within the connector, such as fetching data, sending updates, or managing content.
You can control which tools are available in Figma; for example, you may want to allow a tool that fetches content, but disable tools that send content back to the external source.
Note: Tools that can write to external sources are disabled by default. You’ll need to manually enable them before you can send content back to the connected service.
You can also control each tool’s permissions within a connector. The available options are:
|
Setting |
How it works |
When to use it |
|---|---|---|
|
Ask to run |
Figma always asks your permission before running the tool |
You want control every time Figma AI runs a tool in the conversation |
|
Always run |
Figma runs the tool when needed without asking for permission |
You trust the external source and the available data |
|
Never run |
Figma won’t attempt to run the tool |
Use this setting for tools you don’t need; it can help speed up Figma AI by giving it a smaller set of tools to choose from |
Caution: Be wary of prompt injections from external sources when pulling in context.
You can also temporarily disable connectors to ensure they aren’t used in the current conversation.
- From the chat box, click Add context and select the connector you want to manage.
- Enable or disable the read or write tools, or set permissions for individual tools within that connector.
Tip: Only enable the relevant connectors—and their tools—to help Figma AI work faster.
Remove a connector
Removing a connector stops Figma from reading or writing data through it. It doesn’t delete any data in the external tool, and you can reconnect later by adding and authenticating it again.
- From the chat box, click Add context and select the connector you want to remove.
- In the connector window, click Remove.