Tools / Doctor

Doctor Free

Diagnoses setup problems: connected but nothing happens, local versus remote, 401 and 403, limits, tools not triggering, and Figma links that point at the wrong thing.

MCP tool name: doctor. REST: POST /api/doctor. Does not use a daily call.

Ask for it in plain words

Call the doctor tool. My problem is: connected but nothing happens.

Diagnose setup problems. Reports what the server sees about this connection (client, whether a Pro key was received and is active, plan), checks a Figma link for the right shape (frame link with node-id, not a prototype or Community page), and matches a described symptom to fixes for: connected but nothing happens, local versus remote servers, 401 and 403, rate limits, tools or skills not triggering, and Figma selection problems. Does not use up a daily call.

Inputs

Name	Type	Meaning
`symptom`	string	What is going wrong, in the person's words
`client`	string	Claude Desktop, claude.ai, Claude Code, Cursor, VS Code, Codex or ChatGPT
`figmaLink`	string	A Figma link to check

* required

Example

curl -X POST https://designers.allthepossibles.com/api/doctor \
  -H "content-type: application/json" \
  -d '{"symptom":"it says connected but nothing happens","client":"Claude Desktop","figmaLink":"https://www.figma.com/design/AbC123/My-file?node-id=12-34"}'

Example output

The report field, for the input above (structured fields come back alongside it):

Doctor report

OK    Server reached: Your client reached designers.allthepossibles.com/mcp over HTTPS and got an answer, so the URL and your network are fine.
INFO  Client: You said Claude Desktop. The client did not identify itself.
INFO  Plan: No key was sent, so you are on the Free tier: every tool and prompt with daily caps. Add a Pro key to lift caps and use the crawl, scored reports and playbooks.
OK    Figma link: Design file, fileKey AbC123, node 12:34. This is the right shape: a link to one frame.

If: Shows connected, but nothing happens or no tools appear
  1. Fully quit and reopen the app (not just close the window). Connections are read at start-up.
  2. Open the client's MCP or connectors list and look at the tool count for this server. Zero tools with a green dot means the connection exists but the list failed; remove the server and add it again.
  3. Check the exact URL: https://designers.allthepossibles.com/mcp (with /mcp, https, no trailing text).
  4. Ask the assistant: "Call the whoami tool from the Designers server." If that answers, the server works and the problem is how you phrase requests.
  5. If you edited a JSON config, check for a missing comma or a duplicate "mcpServers" key; a broken file makes the client ignore every server in it.

Still stuck? Email support@allthepossibles.com with the doctor report and the exact wording of any error.

Limits of this tool

It can only see what your request shows the server (client name, whether a key arrived). It cannot see your app's settings or Figma's side.