Direct answer: Figma's remote MCP server can provide structured design context such as components, variables, layout, and selected file information to supported clients. Finta lists the official endpoint in Aurora's catalog, but the page should publish only after Figma accepts Aurora as a supported client and a controlled file receipt proves the exact pitch-deck or investor-asset workflow.
This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. Figma remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.
Current connection note: Figma's endpoint matches the catalog, but Figma restricts its hosted remote server to approved clients. The page states that Finta client eligibility and OAuth success still require confirmation.
How the Figma connection works
| Connection detail | Current Finta guidance |
|---|---|
| Classification | Catalog MCP |
| Configured endpoint | https://mcp.figma.com/mcp |
| Authentication and transport | Provider OAuth through Aurora; Streamable HTTP |
| Source of truth | Figma remains authoritative for provider records, permissions, and action results. |
| Human control | Review external communication, record changes, financial actions, publishing, deletion, and other consequential work before execution. |
What you can use it for
- Retrieve provider-supported design context, component structure, variables, layout, and asset information for a selected Figma file or node.
- Review pitch-deck visual consistency against the file's actual components and design variables.
- Prepare structured recommendations for investor-facing slides or fundraising assets without claiming production-ready output.
- Use provider-supported write-back features only when available, verified, and explicitly approved.
These uses summarize the current provider documentation and Finta catalog purpose. The exact tool inventory varies by provider version, plan, workspace, user permissions, region, and authorization scopes.
Relationship intelligence workflows for Figma
Pitch deck design-system audit
Outcome: A source-linked review of typography, spacing, components, color variables, and repeated slide patterns in a named deck file.
- Select the authoritative pitch-deck file and the specific frames or components in scope.
- Retrieve the available design context and compare repeated patterns or variable usage.
- Prepare prioritized recommendations tied to exact Figma nodes, not generic design advice.
Human decision: The deck owner approves the recommended visual changes and any write-back.
Investor-facing asset handoff
Outcome: A clear review package for a pitch graphic, data-room visual, or campaign asset with source node and brand context.
- Identify the intended audience, asset, source frame, and export or handoff requirement.
- Retrieve the provider-supported context needed to explain components, variables, and layout.
- Prepare a handoff checklist that distinguishes design edits from factual or legal content review.
Human decision: Design and business owners approve the visual, claims, and final export or publication.
How to connect Figma to Aurora
- Select Figma in Aurora and attempt the provider-hosted OAuth flow against https://mcp.figma.com/mcp.
- Confirm that Aurora is accepted under Figma's current supported-client policy before promising availability.
- Authorize a controlled Figma account with access only to a test file or team appropriate for verification.
- Retrieve design context for one known frame or component and compare it with Figma.
- Keep write-back disabled until provider beta status, permissions, and a reversible test are reviewed.
Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.
Permissions and approval boundary
Figma access depends on the connected user's files and team permissions. Aurora may retrieve context and prepare recommendations, but a human must choose the file and nodes, protect unreleased designs, validate factual slide content, and approve every design write, export, or publication.
Limitations to understand
- Figma states that remote connections are limited to clients in its MCP Catalog, so Aurora eligibility must be proven.
- Some write-to-canvas or related features are beta and can change.
- Provider usage limits and plan requirements may apply, with paid usage expected for some MCP access.
- Figma warns that generated output is not automatically production-ready, and design context does not validate fundraising claims.
Verification checklist
- Confirm the live catalog endpoint and oauth_dynamic auth.
- Prove that Figma's OAuth flow accepts Aurora as a supported client.
- Connect a controlled test file and discover the live tool set.
- Retrieve one known frame or component and compare variables and layout with Figma.
- Confirm no unreleased design or customer information appears in public evidence.
- Test write-back only if available, reversible, and explicitly approved, then verify the changed node in Figma.
Verification status: On 2026-08-22, Finta confirmed that this connector appears in the enabled production Aurora catalog and reviewed the configured endpoint, authentication type, and first-party sources listed below. This is not a claim that every provider tool or an authenticated end-to-end action has been tested for every account.
Official provider sources
- Figma official MCP documentation (developers.figma.com)
- Figma official MCP documentation 2 (developers.figma.com)