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
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.
- Windows (confirmed): Run
npx clear-npx-cachein a terminal, then restart Cursor or your IDE. Another commenter confirmed this fixed the error. - 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'sconfig.fish, sonpxcould not resolve; addingexport PATH="/opt/homebrew/bin:$PATH"to~/.zshrcfixed it. - Run the server locally (suggested, not confirmed in the thread): Clone the repo, run
pnpm install, copy.env.exampleto.env, add your Figma token, then runpnpm 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=xxxxkeeps the token in your MCP config and in the process list; running the server from.envavoids that.Did this work for you?- Windows (confirmed): Run
What @AhmedAyman-96 tried on GitHub (Worked)
On Windows, ran
npx clear-npx-cachefrom 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?What @orlovmyk tried on GitHub (Worked)
Launched Cursor from a shell with
--verbose --log=traceto diagnose the failure. Found that env vars configured only in fish'sconfig.fishwere not loaded by Cursor's default zsh shell; addingexport PATH="/opt/homebrew/bin:$PATH"to~/.zshrcfixed npx resolution.Source: https://github.com/GLips/Figma-Context-MCP/issues/212#issuecomment-3213395565 (opens external site)
Did this work for you?What a GitHub user tried on GitHub (Partly worked)
Configured the stdio MCP server with
npx -y figma-developer-mcp --figma-api-key=xxxx --stdioin 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?What @noscripter tried on GitHub (Outcome unclear)
Ran the server locally with
pnpm install, copied.env.exampleto.env, added the Figma token, started it withpnpm start, and registered it in Cursor as a StreamableHTTP server athttp://localhost:3883/mcp.Source: https://github.com/GLips/Figma-Context-MCP/issues/212#issuecomment-3162355152 (opens external site)
Did this work for you?
Related questions
- Figma-Context-MCP: RangeError: Invalid string length when fetching large Figma files
- How to use Figma-Context-MCP with VS Code and GitHub Copilot?
- Figma-Context-MCP: why does my AI host pick the wrong tool, and what changed in v0.1.6?
- Figma-Context-MCP fails to connect in Cline — how to configure it?
- Figma-Context-MCP get_figma_data fails: 'Error fetching file: [object Object]'