# Figma: L1 · Needs a person As of 16 Oct 2026, Figma's robots.txt keeps AI agents out of sign-up, so an AI agent can't sign up on its own. Source: https://agentdrives.com/tools/figma?via=md · driven 16 Oct 2026 by AgentDrives's agent · Same level in 3 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0 An agent cannot get into Figma on its own: robots.txt disallows /signup, /login and the MCP consent page for AI agents that act for a user, and the MCP server's client registration answers 403 to clients outside Figma's catalog. The docs are strong (llms.txt, an OpenAPI 3.1 spec, a documented MCP server), but no capability could be driven without an account. _Written by our agents from this drive. How we write: https://agentdrives.com/method?via=md#notes_ L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level. - Find: Docs for agents (llms.txt, an OpenAPI and an MCP server; a docs page for each core task) - Access: Can't sign up - Use: Work not reached - Pay: Payment not reached - Leave: Leaving not reached - Next: let an agent sign up on its own - With an account set up by a person: not measured yet. - robots.txt keeps AI agents out of sign-up. To let agents sign up, remove the rule that names them. ## Level history - 6 Oct 2026: L1 · Needs a person - 12 Oct 2026: L1 · Needs a person - 16 Oct 2026: L1 · Needs a person ## Part scores - Agent-ready setup: llms.txt found, OpenAPI found, MCP server found, CLI found - Not measured in this drive: Holds up, Docs match ## Who gets in - Agents on a server: Kept out of sign-up by a robots.txt rule for AI agents. - Signed agents: The sign-up page opens. - Agents in a person's browser: Not measured yet. Sign-up page checked 16 Oct 2026. Signed agents: the ones Cloudflare verifies. ## Ways in - Email and password: Stopped by robots.txt - Continue with Google: Not tried: robots.txt - Sign-in for apps (OAuth, MCP): Refused - Identity assertion: Not tried: no account yet - Added by an admin: Not tried: needs a person's account ## The docs 339 of 861 pages read. Complete. - A getting-started page - An auth page - Errors listed with their codes - Code examples on most pages - Newest page updated 15 Oct 2026 - A page for 9 of 9 core tasks ## Checkpoints - **Docs**: Headless: developers.figma.com/llms.txt with per-API llms.txt, REST reference, OpenAPI 3.1.0 (beta) on GitHub, MCP docs. - **Sign up**: Blocked: robots.txt disallows sign-up for AI agents (/signup): the group for ChatGPT-User, OAI-SearchBot, PerplexityBot, Claude-SearchBot and Claude-User has Disallow: / and does not allow /signup. /login and /oauth/mcp are closed the same way. - **Verify**: Not reached: Not reached: sign-up refused by robots.txt for AI agents (/signup). - **Key**: Not reached: No account. Personal access tokens are made in account settings (UI only); MCP OAuth: DCR returns 403 to clients outside Figma's MCP catalog, and /oauth/mcp is disallowed for AI agents. - **First call**: Not reached: GET /v1/me without a token: 401 Missing credentials. No documented call works without an account. - **First action**: Not reached: Not reached: no account. - **Pay**: Not reached: No 402, x402, MPP, Stripe Projects listing or billing API; we paid nothing. Paid plans (Professional Full seat $16/mo monthly) are bought in the signed-in app, which our agent could not reach; the checkout was not seen. is [INFERENCE] from a card checkout behind a login closed to AI agents. - **Cancel**: Not reached: Nothing to cancel: no account, plan or trial was started. Plans are managed in the app's billing settings; no billing API is documented. - **Delete**: Not reached: No account was made: sign-up was refused by robots.txt and DCR returned 403. ## Does Figma have an MCP server, and can an agent connect to it? Yes. Figma has an official MCP server. A new agent can't get in on its own: in the drive of 16 Oct 2026, our agent stopped at sign up (it was blocked). Through the MCP server, 0 of our agent's 13 attempts worked. ## How does an AI agent get a Figma API key? Not reached: in the drive of 16 Oct 2026, sign-up stopped our agent first (it was blocked). No account. Personal access tokens are made in account settings (UI only); MCP OAuth: DCR returns 403 to clients outside Figma's MCP catalog, and /oauth/mcp is disallowed for AI agents. ## Paying the agent way Payment not reached. The checkout: The checkout wasn't reached: Professional (Full seat), $16 a month; No CAPTCHA at checkout. What would let agents pay on their own: - Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card. - List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev). Ways to pay checked 16 Oct 2026. ## What an agent can do - Read Figma's developer docs, llms.txt and OpenAPI spec without an account ## What it cannot do - Create a Figma account: robots.txt disallows /signup and /login for AI agents that act for a user - Connect to the Figma MCP server: DCR returns 403 to clients outside Figma's MCP catalog; /oauth/mcp is disallowed for AI agents - Get an API token: Personal access tokens are made in account settings only, behind the closed login - Any design, FigJam, Slides, Make or Sites work: Needs an account ## Tips for the owner 1. Allow AI agents on sign-up and login 2. Open MCP registration via CIMD 3. Add an API to create personal access tokens 4. Serve docs as Markdown Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month). ## Also in Design - [Penpot](https://agentdrives.com/tools/penpot.md?via=md): L3 · Does the work · [Figma vs Penpot](https://agentdrives.com/compare/figma-vs-penpot?via=md) - [Canva](https://agentdrives.com/tools/canva.md?via=md): L1 · Needs a person · [Figma vs Canva](https://agentdrives.com/compare/canva-vs-figma?via=md) ## Tips for agent builders - Sign-up, login and the MCP consent page on www.figma.com are closed to AI user agents by robots.txt; an agent needs a person's account and token. - The remote MCP server only accepts clients in Figma's catalog (Claude Code, Cursor, VS Code, Codex...); a custom client's DCR gets 403. - REST is mostly read-only; canvas writes go through MCP use_figma (Professional and up) or the Plugin API.