Resources / troubleshooting

URI for your assistant: designers://reference/troubleshooting Free

Troubleshooting: connecting, auth, limits

Run the doctor tool first: it reports what the server can see about your connection and matches your symptom to fixes. Say "call the doctor tool from the Designers server, my problem is ...".

First, three words

• An MCP server is a program that gives your AI assistant extra abilities. You connect it with a URL. This one is remote: nothing is installed on your computer.
• A tool is one ability, like "check this colour pair". The assistant calls it and gets an exact answer.
• A prompt is a saved set of instructions (a critique method, an accessibility review) that you pick instead of writing it yourself.

Decision tree

1. The server does not appear in my app.

• Did you restart the app fully after adding it? Quit it, do not just close the window.
• Is the URL exactly https://designers.allthepossibles.com/mcp ?
• Claude Desktop and claude.ai: add it under Settings, Connectors, Add custom connector. Custom connectors need a paid Claude plan; on a free plan the option may be missing.
• Claude Code: run claude mcp list. If it is not there, add it again with claude mcp add --transport http designers https://designers.allthepossibles.com/mcp
• Cursor and VS Code: check the JSON for commas and that the file is the one the app reads (workspace versus global).

2. It says connected but nothing happens.

• Ask: "Call the whoami tool from the Designers server." If it answers, the server works; the issue is how you ask.
• If the tool count is zero, remove the server and add it again.
• Ask for the job plainly with the input: "Check the contrast of #8a8a8a on white at 16px."

3. I get 401, 403 or "not authorised".

• Designers free tier needs no key. If you added a Pro key, it must be sent as Authorization: Bearer dz_... (include the word Bearer and a space). Run whoami to see if you are Pro or Free.
• Figma 403: your Figma account or seat cannot read that file. Open the same link in your browser as the same account. Viewer and Dev seats have different tool limits; Figma's seat documentation lists them.
• A personal access token for a community Figma server may have expired; create a new one in Figma, Settings, Security.

4. It worked, then it said I hit a limit.

• Run whoami to see calls left today per tool. Caps reset at midnight UTC.
• Figma's own server has its own, separate, lower limits that depend on your plan.
• Pass lists in one call (a whole set of colour pairs or strings) rather than one call per item.

5. The assistant does not use the tools or skills.

• Name the job and give the input. Models choose tools from the words you use.
• Start with the getting_started prompt or tool.
• In Claude Code, run /mcp to see the server and its tools. For skills, check the plugin is enabled and ask what design skills it has.
• Approve the permission prompt the first time a tool runs.

6. Figma: it cannot see my selection.

• The remote Figma server cannot see what you have selected in the canvas. In Figma, select the frame, right click, Copy/Paste as, Copy link to selection, and paste the link into your message.
• The link must have ?node-id= in it. Prototype links, Community pages and files you cannot open will not work.
• Figma's remote server may be restricted or rate-limited for your client or plan. Without it you can still give a screenshot or a live URL.

7. I was told to run npx, edit PATH, or use localhost.

• Those instructions are for local servers. This server is remote and needs only the URL. Claude Desktop and claude.ai cannot reach localhost at all.

Still stuck

Email support@allthepossibles.com with the doctor report and the exact error text.