Back to the marketplace · App
Figma Remote (OAuth, Vendor Allowlist Required)
Figma's official remote MCP service uses OAuth but only allows clients listed in the Figma MCP Catalog. Teloa is not on the list yet, so this connector cannot be added until approval.
Not available for adding in Teloa yet.Client allowlist: Figma only allows clients listed in the Figma MCP Catalog; Teloa is not approved yet (apply through the official waitlist), and Teloa refuses to add this connector until then The server's published resource configuration lists mcp:connect as the OAuth scope
Connections
Adding a package does not connect accounts or enable unsupported components. Review the requirements of each fixed resource in Teloa.
- Source
- Teloa official · Original source
- GitHub
- Resource file: catalog/connectors/teloa.mcp-figma.json
Files kept by the marketplace: artifacts/connectors/teloa.mcp-figma/1.0.0/ - License
- LicenseRef-Figma-Terms
License files: LICENSE - Review
- Reviewed by Teloa on 2026-09-26
- Compatibility
- Needs configuration · Teloa >=0.2.0-alpha.6
- Client allowlist: Figma only allows clients listed in the Figma MCP Catalog; Teloa is not approved yet (apply through the official waitlist), and Teloa refuses to add this connector until then
- The server's published resource configuration lists mcp:connect as the OAuth scope
Technical compatibility
Teloa >=0.2.0-alpha.6 · agent engine 0.1.7-rc.1 - Permissions and requirements
- No extra permissions
Uses the network: yes - Data flow
- Connects to the remote service mcp.figma.com. You enter keys or sign-in details inside Teloa; they never pass through this site. You can browse without signing in. Page views are counted with Cloudflare Web Analytics, which uses no cookies and does not record who you are; the install ranking on the market list reads only anonymous aggregate data.
Fixed package · Teloa official catalog