MCP Connectors explained | Figma

By Figma

Categories: Design, Product

Summary

MCP connectors eliminate manual context switching by directly pulling project details from tools like Notion into Figma Make, reducing documentation overhead and ensuring technical requirements don't get lost in translation between platforms.

Key Takeaways

  1. Enable connectors via the prompt box in Figma Make by clicking plus, selecting connectors, and authenticating through OAuth—connectors then persist across all future projects in that workspace.
  2. MCP connectors include two tool types: read tools (pull context from external tools) and write tools (push updates back). Read tools auto-enable; write tools default to off for security and require explicit permission grants.
  3. Product managers can @mention connectors or paste tool links directly in prompts to inject live documentation (PRDs, requirements) into prototype generation, eliminating copy-paste workflows and translation errors.
  4. Granular permission control allows case-by-case access grants or ongoing permissions, manageable from connector settings, reducing friction while maintaining security over external tool integrations.
  5. Real-time project detail display in the left sidebar during generation ensures technical requirements stay visible and accurate, preventing context loss that typically occurs when manually converting documentation.

Topics

Transcript Excerpt

Ditch the tedious copy and paste process, and jump straight into building with MCP connectors. MCP connectors let you connect Figma make with a project management, documentation, and productivity tools you already use. Once connected, Figma make can pull project details directly into your prompts and use them to inform the prototypes it generates. It's a shorthand way to achieving clearer, contextual prompts while skipping the mental overhead of converting product documentation into actionable i...