Figma Design System (BYOK)

Figma Design System (BYOK) — connector documentation

• MCP endpoint: https://byok-figma-design-system.connectorbay.com/mcp
• REST API: POST https://byok-figma-design-system.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-figma-design-system.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Figma Design System personal access token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-figma-design-system.connectorbay.com/health · Tool schemas: https://byok-figma-design-system.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-figma-design-system · agent@connectorbay.com

What Figma Design System (BYOK) is for

Figma Design System (BYOK) lets an AI assistant read your own Figma Design System data through the Figma Design System API with a key you supply (personal access token). Read-only: 10 tools (list_team_components, list_team_component_sets, list_team_styles, get_component, get_component_set, get_style, list_file_component_sets, get_local_variables, get_published_variables, list_dev_resources). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.figma.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Figma Design System. Figma Design System and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which components has Figma team 1234567890 published?"
• "Which component sets has Figma team 1234567890 published?"
• "Which styles has Figma team 1234567890 published?"
• "What is published component k1a2b3c4 in Figma?"
• "What is published component set k1a2b3c4 in Figma?"
• "What is published style k1a2b3c4 in Figma?"

What it does

• list_team_components: List the published components in a team library (needs the library_content:read scope) with key, name, description, source file and node, and update time. Paged by cursor.
• list_team_component_sets: List the published component sets (variant groups) in a team library with key, name, description, source file and update time. Paged by cursor.
• list_team_styles: List the published styles in a team library (type FILL, TEXT, EFFECT or GRID) with key, name, description, source file and update time. Paged by cursor.
• get_component: Get one published component by its key: name, description, source file, node id, dates and the frame it sits in.
• get_component_set: Get one published component set by its key: name, description, source file, node id and dates.
• get_style: Get one published style by its key: type, name, description, source file, node id and dates.
• list_file_component_sets: List the published component sets of one library file (a main file, not a branch) with key, name, description and node id.
• get_local_variables: Get the variables and variable collections defined in a file (modes, names, types, values per mode) plus remote variables it uses. Enterprise plan; needs the file_variables:read scope. Large files give large answers.
• get_published_variables: Get the variables and collections a library file has published, with keys and names (modes are not included; use get_local_variables for mode values). Enterprise plan; needs the file_variables:read scope.
• list_dev_resources: List the dev resources (links to code, docs or tickets attached to design nodes) in a file, optionally only for some node ids. Needs the file_dev_resources:read scope.

BYOK key

You bring your own Figma Design System personal access token (https://www.figma.com/settings). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.figma.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developers.figma.com/docs/rest-api/ (the API this connector calls, with a BYOK key)

Live from the Figma Design System API (api.figma.com) with a BYOK key; documentation: https://developers.figma.com/docs/rest-api/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Figma Design System. Figma Design System and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Figma Design System account.

Built for: Worldwide. Languages: English.

Figma Design System (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Figma Design System (BYOK) is. Figma Design System (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Figma Design System data: Read your published Figma team libraries (components, component sets, styles), variables and dev resources with your own personal access token. You bring your own Figma Design System personal access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Figma Design System call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.figma.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Figma Design System rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Figma Design System receives. The request we make on your behalf, including the key and the arguments, under Figma Design System's own terms and privacy policy. Figma Design System acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Figma Design System gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Figma Design System data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Figma Design System (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Figma Design System at any time to end all access.

Children. Figma Design System (BYOK) is a general-audience service operated by the adult using the assistant, under Figma Design System's own age rules.

Changes. We will post changes here with a new effective date.

Figma Design System (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Figma Design System (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Figma Design System (BYOK) provides: Read your published Figma team libraries (components, component sets, styles), variables and dev resources with your own personal access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Figma Design System credentials and only access data you are allowed to access. Figma Design System's terms apply to your use of Figma Design System; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Figma Design System. Figma Design System and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Figma Design System returns, lightly trimmed; it may be incomplete, delayed or changed by Figma Design System. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Figma Design System account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Figma Design System's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Figma Design System may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Figma Design System key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Figma Design System takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-figma-design-system

Figma Design System (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-figma-design-system.connectorbay.com/mcp
• REST API: https://byok-figma-design-system.connectorbay.com/openapi.json
• Live status: https://byok-figma-design-system.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Figma Design System (BYOK) never asks for them.