Plane vs Trello for AI agents
As of 15 Oct 2026, Plane gets an AI agent further: L4 · Runs on its own against L1 · Needs a person.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
- Access: MCP sign-in, sign-up in a browser.
- Use: 90% of the work.
- Pay: Payment not tried.
- Leave: Cancels on its own: Deletes its data, but the login stays.
Got in; first wall at delete (blocked). Next: pay without a person
Gets in on its own, L4 · Runs on its own: it signs up, confirms the emailed code, and does the project work over the documented API and the official MCP server, with clean read-back on every call. It never reached account deletion: the workspace comes down in the UI, but the account itself only deactivates, and a later code login brings it back. Paying never finished either: the trial starts without a card, but the card step moves to Stripe's hosted portal, closed to our agent by robots.txt there.
Gets furtherDriven 15 Oct 2026 · The drive and its evidence- Find: Some docs for agents: An OpenAPI and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
Needs a person to start: Trello sits at L1, needs a person. Our agent reached the Atlassian sign-up form and stopped there: a visible reCAPTCHA Enterprise checkbox appeared after the email step, so no account got made. The key page, the MCP's OAuth login and the first API call were never reached, so no board work happened. A documented REST API and an official MCP server are both ready once a person signs up and gets a key or connects. Paying and downgrading run through the web UI with a credit card, never through an API our agent could drive.
Driven 6 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
PlaneGot in; first wall at delete (blocked)
TrelloStopped at sign up: needs a human
| Checkpoint | Plane | Trello |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | Needs a human |
| Verify | In a browser | Not reached |
| Key | In a browser | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | In a browser | Not reached |
| Cancel | In a browser | In a browser |
| Delete | Blocked | Not reached |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Plane | Trello | |
|---|---|---|
| Headless (checkpoints) | 3 | 1 |
| In a browser (checkpoints) | 5 | 1 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 0 | 6 |
| Work done | 90% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | No |
| SDK | – | No |
| llms.txt | Yes | No |
Bot checks, and where a person was needed.
| Plane | Trello | |
|---|---|---|
| Bot check | None met | reCAPTCHA Enterprise (Atlassian sign-up) stopped it at sign up, with a visible challenge |
| Wall type | No bot-check wall | A challenge on the form |
| First wall | Got in; first wall at delete (blocked) | Visible reCAPTCHA on Atlassian sign-up |
| A person helped | No | No |
A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| Plane | Trello | |
|---|---|---|
| Level | L4 · Runs on its own | L1 · Needs a person |
| Holds up | 74 of 100, fair | Not measured |
| Agent-ready setup | 100 of 100, good | 70 of 100, fair |
| Standards | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) · A2A 0.3.0 (1 version behind) | MCP client registration (current) · OpenAPI 3.0.0 (2 versions behind) |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Plane | Trello | |
|---|---|---|
| Pay | Payment not tried | Payment not reached |
| Free plan or trial | Trial, no card | Free plan |
| Cancel | In a browser | In a browser |
| Delete the account | Blocked | Not reached |
How each one takes payment
- Plane: Not tried yet.
- Trello: Payment not reached.
Plane vs Trello: the short answers.
Which can an AI agent use, Plane or Trello?
Plane gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With Plane our agent got in and met its first wall at delete (blocked); with Trello it was stopped at sign up (needs a human). Driven 15 Oct 2026 (Plane) and 6 Oct 2026 (Trello).
Can an AI agent sign up for Plane and Trello on its own?
Plane: yes, in a browser. Trello: no, needs a human.
Do Plane and Trello have an MCP server?
Plane: yes (official). Trello: yes (official).
Can an AI agent delete its Plane or Trello account?
Plane: blocked. Trello: not reached.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.