If you keep handing over the same image every time you make a mockup
Creating a branded mockup from a product photo may look quick, but it takes effort every time you switch tools. You organize the work in a chatbot, upload the image again in a production tool, then bring back the result to explain the next revision. Sometimes the process of passing inputs and results around takes longer than the design itself.
Figma Weave MCP is a connection method that can cut down on this back-and-forth. In MCP clients that support Figma Weave, such as ChatGPT, Claude, and Cursor, you can find available workflows, review their inputs, and receive execution results.
What gets reduced is not the design app itself. It is the effort of reassembling an already-built work process in another conversation. Still, not every Weave task appears automatically, and you also need a separate paid Weave account and workflow-specific input requirements.
What an agent runs is an “accessible published workflow”
Not every task on a Weave canvas appears in the MCP list. According to the official specification, agents can retrieve published workflows that the authenticated user can run in the currently active workspace. Tools you published, tools shared with your workspace, and tools directly shared with your email may qualify, but private workflows are not returned.
So if you run into “I made a tool, so why can’t I see it?”, you do not need to fix the prompt first. Check whether the workflow is published, shared with the Figma account you connected, and in the correct active workspace.
Tool names are examples only. “Brand mockup” used in this article is not a fixed feature included by default for every account. Select a workflow that actually appears in your list, then retrieve the input fields and formats that tool requires.
The Figma MCP Catalog shows Weave under supported products for Claude, ChatGPT, and Cursor. The catalog’s read/write labels describe client-level support and do not mean everyone can run a particular workflow. Final access depends on the authenticated account and its publishing and sharing status.
Behind one sentence is a flow from input checks to result retrieval
Before running anything, first check the tool’s input contract. Weave MCP is designed to let you retrieve each workflow’s required inputs, types, options, scopes, and defaults. Sending arbitrary images or options without checking can result in missing required values or format mismatches.
| Step | What to check | Common reason it gets blocked |
|---|---|---|
| Retrieve tools | Published workflows the current account can access | Private workflow, missing share permission, different workspace |
| Retrieve inputs | Required status, type, options, defaults | Missing required value, format mismatch |
| Provide assets | Supported attachment or a public HTTPS URL that returns the actual file | Unsupported format, inaccessible URL |
| Confirm execution | Number of runs and credit cost | Insufficient credits, paid execution cost not approved |
| Retrieve results | COMPLETED status and outputs | Input, permission, or workflow error |
A file attached in chat can be used as a Weave input through the asset upload tool. The image formats specified in the official documentation are PNG, JPG/JPEG, WebP, and HEIC. You can also enter a public HTTPS URL directly, but it must publicly provide access to the actual file, not a login page.
You can set the number of runs from 1 to 10. For executions that require credits, the cost is shown first and execution starts after confirmation; free executions skip the cost-confirmation step. After execution, the status can be retrieved as one of RUNNING, COMPLETED, FAILED, or CANCELED.
Consider Figma plans and Weave plans separately
To run Weave tools through MCP, you need a paid standalone Figma Weave account. Figma and Weave are separate products, with separate plans and credits. Weave executions that require credits use Weave credits, not Figma AI credits.
That does not mean every execution carries a credit cost. Actual cost varies by the model and configuration used by the workflow, and is presented before a paid execution starts. Whether ChatGPT or Claude itself requires a paid plan cannot be determined collectively from Figma documentation alone, so check the current requirements of the client you use separately.
General MCP tools that read Figma data also have seat- and plan-specific limits. Starter View and Collab seats have a maximum of 20 uses per month, while Professional, Organization, and Enterprise View and Collab seats have a maximum of 6 uses per month; Dev and Full seats follow separate daily and per-minute limits.
Do not reinterpret these numbers as Weave execution limits. Official documentation explains that those limits apply to tools that read Figma data, but does not state that they apply identically to Weave tool retrieval or execution. For a more accurate Weave adoption cost estimate, separately track account count, repeat execution volume, and the credits displayed before execution.
Connect your first run with a real image in Cursor
The steps below use Cursor, where the official documentation lets you confirm the installation screen and authentication sequence. They are based on public documentation, and the editorial team has not directly completed a paid Weave execution.
- Install Cursor and sign in.
Download and install the desktop app for your operating system from the Cursor official Quickstart. After launching it, sign in with your Cursor account before entering the next command in Agent chat. - Prepare the execution requirements.
You need a Figma account to connect via OAuth, a paid standalone Weave account, and a published workflow that account can access in the current workspace. For a paid run, also prepare enough Weave credits to cover the displayed cost. - Install the Figma plugin and authenticate.
Enter /add-plugin figma in Cursor’s Agent chat. After installation, select Connect next to Figma in Cursor Settings under Tools & MCP, then complete Figma OAuth authentication in your browser. The official remote server address for manual connection is https://mcp.figma.com/mcp. - Start by checking the list of runnable tools.
Ask Agent, “Show me the Weave tools I can run.” If the tool you want is absent, do not keep retrying; check the Figma account, active workspace, and publishing and sharing status. - Retrieve the real tool’s input contract.
Select a tool from the list and ask, “First show me this tool’s required inputs, accepted formats, defaults, and whether it uses credits.” If it does not take an image input or requires a different format, do not run the example below as-is; adjust it to the retrieved contract. - Attach a real image in a supported format.
Attach the PNG, JPG/JPEG, WebP, or HEIC file you want to use directly in the Cursor conversation. Ask it to upload the attached file to Weave, use it as the retrieved image input, and set the run count to 1. - Check the cost and completion status.
If a credit cost appears, review it and run only if you agree. A free run proceeds without this confirmation. Then retrieve the status and confirm that COMPLETED and an output are returned. If it is FAILED, correct the input format, sharing permissions, active workspace, or credit issue according to the returned error.
Show me the Weave tools I can run. For the tool I select from the list, first tell me its required inputs, defaults, and whether it uses credits. Upload the real product image attached to this conversation to Weave, use it as the image input, and run it once.
This request is an example of the structure. The tool name and image input field must match the contract actually retrieved. If you want to use a public URL, provide an HTTPS URL you manage that returns an actual image file, not an example address.
The first success criterion is not whether the output looks good. Confirm that the published workflow appears in the list, its input contract is retrieved, and a single execution with an attached asset returns a COMPLETED status and output. After passing that threshold, evaluate brand fit and the number of revisions.
If you want to dig deeper
Figma MCP Catalog You can check whether the client you use supports Weave, along with server and access types. figma.com
Tools and prompts This is the official specification for checking the retrieval scope of published workflows, input contracts, asset uploads, cost confirmation, and result statuses. developers.figma.com
Set up the remote server (recommended) Refer to this when you need the Cursor plugin command, OAuth connection, or the official remote server address. developers.figma.com
Figma Weave Pricing Before adoption, you can check how Figma and Weave plans and credits are separated. weave.figma.com
