Start here

Pick your track. You can switch any time.

New to this

You use an AI assistant (Claude, ChatGPT, Cursor and others) and you design things. You want it to review your work properly instead of saying "looks great". Here is what you need to know, in plain words.

What is an MCP server?

It is an add-on that gives your AI assistant extra abilities, a bit like installing an extension in your browser. You connect it by pasting one web address into your assistant's settings. Nothing is installed on your computer.

What is a tool?

A tool is one ability the add-on provides, such as "check whether this text colour is readable on this background". When you ask for something, the assistant picks the right tool, runs it, and uses the exact answer instead of guessing. That matters because assistants are often wrong about numbers like colour contrast.

What is a prompt?

A prompt here is a saved set of expert instructions, like a checklist a design lead would follow for a critique or an accessibility review. You pick it from a menu or ask for it by name, and the assistant follows the method step by step, calling the tools when it needs them.

What is a skill?

A skill is the same kind of expert instruction packaged as a folder your assistant loads on its own when your request matches, so you do not have to pick anything. Skills work in Claude Code and some other tools. You can use this whole service without them.

What you need

• An AI assistant that can add an MCP server: Claude Desktop or claude.ai (paid plans), Claude Code, Cursor, VS Code, Codex or ChatGPT (developer mode). The install page has the exact clicks for each.
• Optional: a Figma account, if you want your assistant to read Figma files. You give it a link to a frame; you do not need to select anything.
• Nothing to pay. Free covers the tools and prompts. Pro ($5 a month, 7-day trial) is for heavy use.

Do these three things

1. Add the server to your app (about two minutes).
2. Say: Call the getting_started tool. I have a Figma link and some button text. It will explain what it can do and suggest three first tasks for what you have.
3. Follow your first five minutes for an accessibility check you can see working.

If anything does not work, say Call the doctor tool. My problem is: ... or read troubleshooting.

Already use MCP and skills

• Remote Streamable HTTP server: https://designers.allthepossibles.com/mcp. Protocol 2025-06-18. Capabilities: tools, prompts, resources. All tools are annotated read-only with titles.
• Auth: none for Free. Pro: Authorization: Bearer dz_..., or x-api-key, or ?key= on the URL for clients that cannot send headers (a key in a URL can appear in client logs; prefer the header).
• 21 tools (reference), 22 prompts (reference), 15 resources at designers://... (reference). REST mirror of every tool at POST /api/<id>; every response has a report string.
• Figma: pair with Figma's own MCP server. Pass a link to a frame (with node-id); the remote Figma server cannot see your canvas selection, and its limits and seat rules are Figma's. The prompts call get_metadata, get_screenshot, get_design_context and get_variable_defs and hand exact values to our checkers. Nothing here needs Figma write access.
• Skills: /plugin marketplace add johnhowrey/atp-plugins then /plugin install atp-designers@atp-plugins, or copy folders from atp-design-skills.
• Limits: Free has per-tool daily caps per IP and 30 requests a minute; Pro has no daily caps and 300 a minute. whoami shows what is left; doctor diagnoses setup.

Next: install per client, tools, free and Pro.