Skip to main content
Figma is a design and prototyping platform. This page shows you how to connect it as an MCP server in Corunner so your agents can access design context and retrieve product specs.

Connect with Figma

Open the MCP Servers tab in the Corunner web app.

​
Server details

​
Connect Figma

1

Sign in to Corunner

Sign in to Corunner at app.corunner.ai.
2

Open Integrations

Open Integrations in the left sidebar.
3

Select the MCP Servers tab

Select the MCP Servers tab.
4

Find the Figma card

Find the Figma card in the grid.
5

Turn on the Connect toggle

Turn on the Connect toggle. The Connect Figma modal opens.
6

Verify the Server name

Verify the prefilled Server name (Figma by default; rename if you run multiple instances).
7

Verify the Server URL

Verify the prefilled Server URL. Value: https://mcp.figma.com/mcp. Because Corunner manages the endpoint, the field shows a “Managed by Corunner” hint and is read-only.
8

Click Test URL

Click Test URL to confirm the endpoint format is valid and the server responds.
9

Select the authentication method

Select the authentication method (prefilled Bearer token). The modal button reads “Bearer token”. Paste your Figma personal access token into the token input.
10

Click Advanced (Optional)

Expand the Advanced (Optional) panel. It contains two fields: Custom headers (extra HTTP headers Corunner sends to the server, one key/value pair per row) and Usage guidance (a free-text instruction that tells agents when and how to use this server). Corunner appends the guidance to every tool description sent to the agent, so it directly influences when the agent picks Figma over another source.
11

Enter Usage guidance

In the Usage guidance field (placeholder: Tell agents when and how to use this server…), describe when this server should be used, which files or projects to prefer, what needs human approval, and what must not be accessed. Keep it short and imperative. Max 2000 characters. See the next section for a copyable example.
12

Click Connect

Click Connect.
13

(OAuth only — skip for Figma)

If OAuth is used, Corunner redirects the current tab to the provider’s authorization page. (Skip step for Figma.)
14

(OAuth only — skip for Figma)

Review and approve the requested permissions in the provider consent screen.
15

(OAuth only — skip for Figma)

After approval, return to Corunner automatically.
16

Confirm the green Connected badge

Confirm a green Connected badge and an enabled Connected toggle on the Figma card.

​
Configure Usage Guidance

Usage guidance tells Corunner agents when and how to use this server. It is optional but recommended. A good guidance block answers six questions:
  1. When should agents use this server?
  2. What should they retrieve?
  3. Which resources are permitted?
  4. Which resources require approval or should not be accessed?
  5. What must not be accessed?
  6. How should findings be presented?
Never enter secrets in the Usage guidance field. It is plain text guidance, not a credentials store.
Here is a copyable example for Figma:

​
Verify the Connection

After a successful connection, the Figma card shows:
  • A green Connected status pill on the name row.
  • A Connected to <workspace> meta line with relative time (for example, “Connected to Acme 2 hours ago”).
  • A Connected toggle that is enabled.
  • A <N> capabilities button that expands into the capability list.

​
Capabilities

Figma exposes the following capabilities:
  • read files
  • read frames
  • read comments

​
Check Connection Health

Click the Test connection icon (Wi-Fi glyph, next to the Connected toggle) on the Figma card. This runs a live probe:
  • Green check: the endpoint is reachable and credentials are valid.
  • Red warning: the probe failed.
If the probe fails, open Edit configuration to refresh your Figma personal access token or verify the Server URL.

​
Edit Configuration

Click the Edit configuration icon (settings glyph) on the Figma card to update the connection. Editable fields include:
  • Server name
  • Server URL (read-only because Corunner manages this endpoint)
  • Authentication method and credentials
  • Custom headers (under Advanced)
  • Usage guidance
Creating, editing, disconnecting, and observation consent changes are admin-only actions. Members see status and capabilities, but not the toggle or icon actions.
Click the Observation consent icon (brain glyph) on the Figma card. Observation is separate from tool connection: it controls whether Corunner passively reads resources into organizational memory, while capabilities are unaffected even if observation is disabled. Scopes have:
  • Mode: Disabled / Shadow / Active
  • Sensitivity: Standard / Restricted / Excluded
Excluded scopes cannot be enabled.
The precise effect on Memory & Learnings for advanced modes should be confirmed with the Corunner product team if you plan to depend on it in policy.
Observation consent changes are admin-only.

​
Disable or Disconnect

Disconnecting deletes stored credentials for this connection. If you also want to eliminate provider-side tokens entirely, revoke the token from your Figma account settings.

Connect with Figma

Ready to go? Open the MCP Servers tab and turn on the Figma Connect toggle.

Integrations Overview

Browse all available Corunner integrations.

Memory & Learnings

Learn how Corunner builds organizational memory.

Governance

Review policies for access, observation, and consent.