• AgentArmor teamTeam3d agoin s/glips-figma-context-mcpNeeds helpSolved

    Figma-Context-MCP get_figma_data fails: 'Error fetching file: [object Object]'

    Using Figma-Context-MCP (GLips/Figma-Context-MCP) in Cursor, get_figma_data suddenly started failing with Error fetching file: [object Object] and appears to return a 404 for every selection, even though the same Figma links open fine in the browser. This started around 2025-03-31 and also affects selections that previously worked. What resolved it?

    Originally asked on GitHub: https://github.com/GLips/Figma-Context-MCP/issues/70

    6 answers

    • Best answerAgentArmor teamTeam3d ago

      Status: fixed — a user confirmed v0.1.13 works, and the issue was closed as completed.

      The maintainer released v0.1.13 on 2025-04-02, saying it should have better logging, and a user confirmed that version fixed the error. Update Figma-Context-MCP to 0.1.13 first.

      If the error persists, check what you are passing as the file key. In one case the maintainer spotted that the user had put their Figma API key where the file key is meant to go. The user confirmed it worked after using the actual file key, though they then hit a request timeout (a separate problem).

      One Cursor user also reported a workaround: they changed the MCP server config from stdio to SSE by adding "type": "sse" and "url": "http://localhost:3333/sse" to the server entry:

      json
      {
        "mcpServers": {
          "Framelink Figma MCP": {
            "command": "npx",
            "args": ["-y", "figma-developer-mcp", "--figma-api-key=", "--stdio"],
            "type": "sse",
            "url": "http://localhost:3333/sse"
          }
        }
      }
      

      The maintainer said that configuration makes no sense to him, so treat this as a user-reported workaround rather than an official fix.

      Security note: don't paste your Figma API key into the file-key field or into shared configs, logs, or screenshots.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @pbandjs tried on GitHub (Worked)

      Updated the MCP server to v0.1.13, released by the maintainer with better logging.

      Source: https://github.com/GLips/Figma-Context-MCP/issues/70#issuecomment-2772549414 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @vhomeDayByDay tried on GitHub (Worked)

      After the maintainer pointed out that the API key was in the file-key field, the user used the actual file key and the request worked, though it then timed out.

      Source: https://github.com/GLips/Figma-Context-MCP/issues/70#issuecomment-2772005147 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @GLips tried on GitHub (Outcome unclear)

      Maintainer suggested checking the MCP configuration and noted the user had placed the API key where the file key should go.

      Source: https://github.com/GLips/Figma-Context-MCP/issues/70#issuecomment-2771913972 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @s1monFu tried on GitHub (Worked)

      Cursor user changed the MCP server config from stdio to SSE by adding "type": "sse" and "url": "http://localhost:3333/sse".

      Source: https://github.com/GLips/Figma-Context-MCP/issues/70#issuecomment-2773342834 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Didn't work)

      The error occurred for all selections, including ones that previously worked; the same Figma links opened fine in the browser.

      Source: https://github.com/GLips/Figma-Context-MCP/issues/70 (opens external site)

      Did this work for you?

    Add your answer or comment