Connecting Figma to Cursor Cloud Agents

Mahanth Prudhvi P

Wanted to share a workflow we've built out at our org and get input from anyone who's tackled the next piece — bringing Figma design context into the same pipeline.

What's working (Part 1): Jira → Cursor → GitHub

We've set up a two-stage Cloud Agent workflow triggered entirely from Jira status changes and ticket assignment:

• Stage A (Spec): Ticket moves to a "Prepare SpecFile" status and gets assigned to Cursor → Cloud Agent checks out a branch, generates a spec.md via Spec Kit, and comments the user stories/requirements back on the ticket.
• Stage B (Code): Ticket moves to "Generate Code" → Cloud Agent runs plan/tasks/implement/converge, opens a PR against our repo, and links it back to the ticket.
• Both stages also support a revision loop — tagging , without regenerating from scratch.

What we're exploring now (Part 2): bringing in Figma

The next piece is wiring design requirements into the same pipeline — ideally, a ticket carrying a Figma file/frame link that Cursor's Cloud Agent can pull design context from (components, variables, styling) before or during spec/plan generation, rather than someone manually translating the design into text requirements.

My specific questions:

• Has anyone connected Figma to a Cloud Agent (Cursor or otherwise) successfully for full design-context retrieval?
• Do we need a Figma Enterprise plan for this, or does a lower tier cover what's needed?
• Does the Cloud Agent need to authenticate as a specific individual's Figma account, or can we configure a shared/service account (or some other routing) so the connection isn't tied to one person's personal login?

Thanks!

Mahanth

Germán Morales

Hi Mahanth Prudhvi P,

Nice setup. I haven't run this exact pipeline myself, but going through Figma's and Cursor's docs, all the pieces you need are supported. Taking your three questions in order:

1. Figma with a Cloud Agent: Figma's remote MCP server (mcp.figma.com/mcp) lists Cursor as a supported client, and Cursor Cloud Agents support HTTP MCP servers with OAuth. You can add it as a personal server from the MCP dropdown in cursor.com/agents, or as a team server under Dashboard > Plugins & MCPs. One tip for the tickets: link to the specific frame rather than the whole file, since the server uses the node ID in the link to know which object to return.
2. Plan: Enterprise isn't required. The remote server works on every plan, but the seat makes a big difference. View and Collab seats get only 20 tool calls per month, while Dev or Full seats get 200 per day on Professional and Organization, and 600 per day on Enterprise. For an automated pipeline, a Dev or Full seat on Professional is the realistic minimum.
3. Whose account: in Cloud Agents, OAuth for MCP is per user, even for servers shared at team level. So the Figma connection runs as the Figma account of whoever the agent runs as, and the calls count against that person's seat. To decouple it from one person, the cleanest option is a dedicated account for the automation with its own Dev seat. A token-based setup would mean running a stdio MCP server inside the agent's VM, and Cursor notes that the agent can read that server's configuration and environment variables there.

Sources: Figma MCP rate limits and access, Guide to the Figma MCP server, Cursor Cloud Agent capabilities