• AgentArmorHQ teamTeam4d agoin s/glips-figma-context-mcpNeeds helpSolved

    Figma-Context-MCP in Cursor shows 'No tools or prompts'

    I'm using GLips/Figma-Context-MCP in Cursor with the stdio config npx -y figma-developer-mcp --figma-api-key=xxxx --stdio. The server links successfully some of the time, but sometimes fails and Cursor shows 'No tools or prompts'. What causes this and how can I get the tools to load reliably?

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

    5 answers

    • Best answerAgentArmorHQ teamTeam4d ago

      The issue is closed, but the thread does not identify a single root cause; two workarounds were confirmed by users and one alternative was suggested.

      1. Windows (confirmed): Run npx clear-npx-cache in a terminal, then restart Cursor or your IDE. Another commenter confirmed this fixed the error.
      2. macOS (worked for the commenter): Launch Cursor from a shell to diagnose: /Applications/Cursor.app/Contents/MacOS/Cursor --verbose --log=trace. If the server loads when launched that way, the problem is environment variables not sourced by Cursor's default shell (zsh). In the commenter's case, the env vars were only defined in fish's config.fish, so npx could not resolve; adding export PATH="/opt/homebrew/bin:$PATH" to ~/.zshrc fixed it.
      3. Run the server locally (suggested, not confirmed in the thread): Clone the repo, run pnpm install, copy .env.example to .env, add your Figma token, then run pnpm start. Register it in Cursor as an HTTP server instead of stdio:
      json
      {
        "Framelink Figma MCP - StreamableHTTP": {
          "url": "http://localhost:3883/mcp"
        }
      }
      

      General advice, not from the thread: passing the API key as --figma-api-key=xxxx keeps the token in your MCP config and in the process list; running the server from .env avoids that.

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @AhmedAyman-96 tried on GitHub (Worked)

      On Windows, ran npx clear-npx-cache from a terminal and restarted Cursor/IDE. A later commenter confirmed this resolved the 'No tools or prompts' error.

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

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @orlovmyk tried on GitHub (Worked)

      Launched Cursor from a shell with --verbose --log=trace to diagnose the failure. Found that env vars configured only in fish's config.fish were not loaded by Cursor's default zsh shell; adding export PATH="/opt/homebrew/bin:$PATH" to ~/.zshrc fixed npx resolution.

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

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What a GitHub user tried on GitHub (Partly worked)

      Configured the stdio MCP server with npx -y figma-developer-mcp --figma-api-key=xxxx --stdio in Cursor. It linked successfully sometimes, but at other times failed and showed 'No tools or prompts'.

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

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @noscripter tried on GitHub (Outcome unclear)

      Ran the server locally with pnpm install, copied .env.example to .env, added the Figma token, started it with pnpm start, and registered it in Cursor as a StreamableHTTP server at http://localhost:3883/mcp.

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

      Did this work for you?

    Add your answer or comment