Create and use custom MCP connectors in the Figma agent and Figma Make

Custom connectors allow you to connect the Figma agent and Figma Make to any remote Model Context Protocol (MCP) server. This lets you use data from external apps as context for your app or prototype. You can connect to public MCP servers or to your own private internal servers.

For example:

• Use a company’s official MCP server that isn’t on Figma’s list of verified partner servers
• Use an open source MCP server when a company hasn’t released an official one
• Connect to a private documentation or design systems server

Create a custom connector

A custom connector is visible only to its creator. On Organization and Enterprise plans, admins can publish custom connectors to the organization.

1. In the prompt box in a chat, click Add context. Hover over Connectors, then select Manage.
2. Navigate to the Created by you tab and click Create.
3. Enter a Name. The Icon, Tagline, and Description fields are optional.
4. Enter the MCP server URL, then click Create. If you leave Advanced settings empty, Figma attempts to authenticate using the server’s supported method. If needed, click Advanced settings and enter the relevant details to customize authentication.
5. Click Connect on the connector to authenticate.
6. Review the available Read and Write tools and enable the ones you want to use.
7. Test your connector by using it in a chat.

Use a custom connector in chat

You can use custom connectors you’ve created, or—on the Organization and Enterprise plans—connectors that have been published to your organization by an admin.

When a connector and its tools are enabled for the current chat, you can call it naturally within the conversation.

1. To explicitly reference a connector, type @ in the chat to see a list of connected connectors. Select the one you want to use and it will appear as a pill above your message. This ensures the agent only uses the specified connectors for the current task.
2. You can also enter a prompt that references the connector. For example, paste an Asana link and write "Use the specs in this project to create a first-draft prototype".
3. If your prompt requires a connector, the agent shows which connector and tool it plans to call and asks 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 a custom connector

Edit a custom connector’s details

1. From the chat box, click Add context. Hover over Connectors, then select Manage.
2. Navigate to the Created by you tab and click More on the connector.
3. Click Edit.
4. Update the name, icon, tagline, description, or custom headers, then save your changes.

Edit a custom connector’s tools

Some connectors include multiple MCP tools that perform different actions, such as fetching data, sending updates, or managing content.

You can control which tools are available in Figma. For example, you might enable tools that fetch content while disabling tools that write back to the external source.

Each tool supports the following permission settings:

1. From the chat box, click Add context. Hover over Connectors, then select Manage.
2. Navigate to the Created by you tab and click Manage on the connector.
3. Enable or disable the Read or Write tools, or set permissions for individual tools within that connector.

Disconnect a custom connector

Disconnecting a connector stops Figma from reading or writing data through it. It doesn’t delete the connector or any data in the external tool, and you can reconnect later by re-authenticating.

1. From the chat box, click Add context. Hover over Connectors, then select Manage.
2. Navigate to the Created by you tab and click Manage on the connector.
3. At the bottom of the modal, click Disconnect.

Delete a custom connector

Deleting a connector disconnects it and removes it from the Personal tab. You won’t be able to reconnect to the MCP server without creating the connector again.

1. From the chat box, click Add context. Hover over Connectors, then select Manage.
2. Navigate to the Created by you tab and click More on the connector.
3. Click Delete and confirm your choice.

Supported authentication methods

Custom MCP connectors support the following authentication methods. The best option depends on how your server manages access and permissions.

OAuth 2.0 (default)

If the MCP server supports OAuth, the agent uses the server's declared OAuth flow by default.

• You authorize access through a standard OAuth flow after creating the connector
• Permissions are determined by the provider's default OAuth behavior

Best for: Quick setup where default OAuth permissions are sufficient.

Note: When registering your OAuth app, enter https://www.figma.com/oauth/mcp/callback as the callback URL.

OAuth with client credentials

Uses OAuth with a client ID and client secret from your own OAuth app.

• You authorize access by providing credentials from the service you're connecting to
• You typically control scopes, permissions, and access rules

Best for: Working with sensitive data sources where access needs to be controlled.

Note: When registering your OAuth app, enter https://www.figma.com/oauth/mcp/callback as the callback URL.

Custom request headers

Uses static headers sent with every request to authorize.

• You provide API keys or personal access tokens when creating the connector
• No OAuth flow is required; credentials are attached directly to requests

Best for: Servers that don't support OAuth, including internal services, or machine-to-machine authentication.

Note: When an organization admin publishes a custom connector that uses custom request headers, the headers are published with it. Individual users won't need to provide their own credentials.

No authentication

Some MCP servers don't require authentication.

• Requests are sent without credentials
• Access control, if any, is handled entirely by the server

Security best practices

When creating custom connectors, we recommend following a few security best practices:

• Only connect to MCP servers you own or trust completely. Wherever possible, use official servers and check the list of verified partner connectors.
• Understand which tools are available and what data the server can read or write
• Prefer OAuth authentication over embedding credentials in URLs
• Never share OAuth client secrets in public repositories or documentation

Troubleshooting