Figma Weave MCP Call Failure: 2026 Troubleshooting Guide

Symptom → fastest fix: If Figma Weave tools are missing or a call fails, check the linked Figma and Weave accounts, the active Weave workspace, and your MCP client's support status first. Then verify the model type, required inputs, and any run confirmation.

Use this path when: You use an external AI Agent to create images or video and cannot find a Weave tool or start a task.
It also helps design-system maintainers checking account, workspace, and access settings, and Windows-based creatives deciding whether later work actually requires macOS.

Last updated October 27, 2026. The feature and connection details below were checked against the Figma release notes, the Figma Weave MCP help article, and the Figma MCP server guide.

SECTION 01Connection boundaries to check

Figma Weave tools can be called from external agents through Figma MCP. That does not mean every agent client is supported, or that Weave needs its own separate MCP server. Figma's current setup guidance describes connecting to the Figma MCP server through a supported client; use that guide and its current client list to check your exact setup.

As of the October 26, 2026 release notes, Figma has confirmed MCP access to image and video models available in Weave. The same feature has clear limits: direct calls support existing system models, while imported models are not supported through that path. MCP also cannot create or edit Weave workflows. Check the linked release notes and Weave instructions before treating a missing capability as a connection fault.

Keep these distinctions in view while troubleshooting:

• Figma MCP connection: links the supported agent client to Figma's MCP server.
• Weave account and workspace: determine which Weave tools are available to the linked account and active workspace.
• Tool or model call: runs an available tool or supported model. It does not build or revise a Weave workflow.

Boundary check: Do not add a separate Weave MCP server just because the agent's tool list is empty. First verify the documented Figma connection, account link, and active Weave workspace.

SECTION 02No Weave tools appear in the agent

Treat an empty tool list as a visibility problem first, not evidence that the model is broken. Work through these checks in order.

First, confirm the account link

Open the Weave account settings and confirm that the Figma account you intend to use is linked. If you use more than one account, check the actual account active in the agent workflow. A successful MCP connection does not by itself prove that the linked Weave identity is the one with access to the tools you expect.

Next, check whether the Figma MCP connection is established in the agent client. Follow the Figma MCP connection setup guide for the client and connection method you are using. If your client is not listed in Figma's current support documentation, do not assume that an MCP configuration written for another client will work unchanged.

Then, check the active Weave workspace

The agent can read tools associated with the active Weave workspace. Confirm that the tool you want is visible in that workspace and that your account can access it. Switching a Figma team, project, or file does not necessarily switch the active Weave workspace.

If the expected tool appears after changing the active Weave workspace, the issue was workspace selection rather than a missing MCP server. If the tool remains absent, recheck the account link and client support before changing connection settings.

• Likely workspace issue: other Weave tools are visible, but the target tool is not.
• Likely connection or account issue: no Weave tools appear, or the linked identity is not the intended one.
• Not enough evidence: a Figma team change alone does not confirm that Weave's active workspace changed.

For more detail about the available tools and how agents use them, see Figma's tool descriptions and example prompts.

SECTION 03Incorrect tool list or access denial

A visible tool is not necessarily an accessible tool. Check whether the intended tool belongs to the active workspace and whether the signed-in user has permission to use it. If a teammate can see a tool that you cannot, compare the active Weave workspace and account access before copying their MCP settings.

Use this sequence:

• Open Weave and identify the workspace that is active for the current session.
• Find the target tool in that workspace, rather than assuming it is available everywhere.
• Confirm that the account linked to Figma MCP is the account with access to that tool.
• Refresh the agent's tool list after correcting the workspace or account.

Do not use a Figma team switch as a substitute for selecting a Weave workspace. They are separate context checks. If access still differs between users after those checks, record the workspace and account used, then follow the official Figma MCP server FAQ for connection and access troubleshooting.

SECTION 04Visible tools cannot run the requested model

First decide which task you are asking the agent to perform. Calling a published Weave tool and directly calling a model are different paths. A published tool may package a workflow that is already available in Weave; a direct model call asks the agent to invoke a model itself.

Figma's documented direct-call path supports existing system models, not imported models. If the model you want was imported, a failed direct call is consistent with that documented limit. Choose an available system model or a published tool that fits the task; do not keep changing MCP connection settings to overcome an unsupported model type.

MCP also does not create or edit Weave workflows. If your request is to change the nodes, logic, or structure of a workflow, do that in the supported Weave interface rather than asking the agent to make the change through MCP. The Weave FAQ covers current product behavior and feature boundaries.

SECTION 05Tasks that stall before execution

A request that never begins may be incomplete, blocked on a permission, or waiting for you to approve the run. Check the request itself before retrying it.

• Confirm required inputs. Compare your prompt with the selected tool's instructions. Add any required text, image, video, or other input instead of assuming the tool can infer it.
• Check the uploaded asset. Make sure the image or video is present in the agent conversation and matches what the selected tool expects. If the tool cannot access the asset, reselect or reattach it through the documented flow.
• Look for a confirmation step. If the agent displays a permission or cost confirmation, review it and approve only if you want the task to run.
• Check the run state before resending. A delayed response can mean the request is waiting for input or authorization. Sending the same prompt again may create a duplicate task rather than unblock the first one.

Both Weave tools and direct model calls consume Weave credits. The official documentation does not justify assuming a fixed charge per request or a universal free allowance. Check the usage information shown for your account and the current run details before approving. If the agent shows a confirmation with a credit estimate, use that displayed information rather than a number copied from an older guide.

Avoid this false fix: Repeatedly reconnecting MCP will not supply a missing image, grant tool access, or approve a run that is waiting for confirmation.

SECTION 06Running tasks with no visible result

A started task and a returned result are separate states. Check whether the agent still reports the task as running, whether it has completed, and whether the output has appeared in the conversation or the tool's expected result area.

If the task is still processing, do not label it a model failure just because the conversation has not updated yet. Use the available run-status or output controls described by the tool. If a cancel action is available, use it only when you intend to stop the task; cancellation is not a retry and does not produce the missing output.

If the agent reports completion but you cannot find the result, inspect the original conversation and the tool output location before launching another run. Check that you are looking at the same account and workspace used to start the task. A task that is still processing, a result returned in an unexpected location, and an MCP connection failure are different states; identify which one you have before reconnecting or resending the prompt.

A quick symptom-to-action example

A designer links the right accounts and can see several Weave tools, but a direct request for an imported video model fails. That points away from an empty MCP connection: the tool list proves that some connection is working, while the requested model type falls outside the documented direct-call support. The next action is to choose an available system model or an appropriate published tool, not to install another server.

SECTION 07Run this checklist before changing settings

• [ ] Confirm that the intended Figma and Weave accounts are linked.
• [ ] Confirm that your agent client and connection method appear in Figma's current MCP documentation.
• [ ] Check the active Weave workspace, then verify the target tool is visible there.
• [ ] Confirm that your account can access the tool.
• [ ] Identify whether you are calling a published Weave tool or a model directly.
• [ ] If calling a model directly, verify that it is an existing system model, not an imported model.
• [ ] Attach the required image, video, or other inputs and review any run authorization or credit confirmation.
• [ ] Check the task status and output location before sending the request again.

If the first checks fail, fix the account, workspace, or supported-client connection. If the call fails only for a particular model or workflow-edit request, check the feature boundary instead. If the task has started, inspect its status and output before retrying.

SECTION 08Quick answers

Why are Figma Weave tools missing from an AI Agent?

Check the account link, then confirm that the client is supported and connected to the Figma MCP server. If the connection is sound, check the active Weave workspace and whether the target tool is visible and accessible there. An empty tool list does not by itself prove that you need a separate Weave MCP server.

Does Figma Weave need its own MCP server?

No separate Weave MCP server is required for the documented external-agent workflow. Connect through the supported Figma MCP setup, link your Figma and Weave accounts, and select the right active Weave workspace. Use Figma's current client guidance rather than assuming that every agent supports the same connection method.

Can MCP directly call an imported model or edit a workflow?

Direct MCP model calls support existing system models, not imported models. MCP also does not create or edit Weave workflows. If the task needs an imported model or a workflow change, use a supported model or make the change through the Weave interface rather than repeatedly repairing a working MCP connection.

Why can I still not find tools after linking both accounts?

The active Weave workspace determines which tools the agent can read. Check that the tool is present in that workspace and that your linked account has access. Switching Figma teams is not the same as changing the active Weave workspace, so verify the workspace inside Weave and refresh the agent's tool list.

What credits does an image or video task use?

Weave tools and direct model calls consume Weave credits. Do not assume a fixed amount or free usage based on another person's run. Review your current task details and account usage information, and check any cost confirmation shown by the agent before authorizing the task.

SECTION 09Decide whether a Mac belongs in the next step

A Figma MCP connection problem is not, by itself, a reason to rent a Mac. Account linking, workspace selection, supported-client status, model limits, missing inputs, and run authorization are the relevant checks. The official Figma guides describe a remote MCP connection; they do not make macOS a requirement for that troubleshooting path.

A remote Mac may be worth evaluating only if a later creative task or a specific agent client in your workflow actually requires macOS. Verify that requirement against the software's current documentation and test your own task before committing. If your work is otherwise browser-based and the MCP client you use runs on your existing computer, adding a Mac would introduce another environment to manage without fixing a Figma or Weave configuration problem.

If you have a confirmed macOS-dependent step, review the MACNOX service overview and current plan information, then check that your chosen software and access method fit the task before renting. If no step requires macOS, stay with your current setup and resolve the MCP issue at its source. If a short-term Mac test is justified, you can review MACNOX rental options and validate your actual workflow before making it part of your regular toolchain.

SECTION 10FAQ