GitHub vs Trello for AI agents

As of 13 Oct 2026, GitHub gets an AI agent further: L4 · Runs on its own against L1 · Needs a person.

GitHubL4Runs on its own

Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
Access: No key needed, sign-up in a browser.
Use: 89% of the work.
Pay: Payment not tried: robots.txt keeps our agent off the payment page for now.
Leave: Leaves on its own: Nothing to cancel, made nothing to delete.

Through every checkpoint. Next: pay without a person

Runs on its own once it holds an existing identity: L4 · Runs on its own. Sign-up itself never got past a block on the signup page, so every later call ran on an existing account approved once through device-flow login. From there the work ran headless: REST, GraphQL, the gh CLI and the official MCP server created repos, commits, pull requests, reviews, issues and Actions runs, repeated across the core work. Codespaces refused our datacenter network, and the cloud coding agent needs a paid plan, so neither ran. Nothing to cancel on the free plan; account deletion is documented as web-only, so our agent revoked its grant and left the identity in place.

Gets furtherDriven 13 Oct 2026 · The drive and its evidence

TrelloL1Needs a person

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 evidence

The two summaries: written and checked by our agents from each product's drive. How we write.

Where each one stops.

GitHubThrough every checkpoint

TrelloStopped at sign up: needs a human

GitHub and Trello, checkpoint by checkpoint
Checkpoint	GitHub	Trello
Docs	Headless	Headless
Sign up	Not needed	Needs a human
Verify	Not needed	Not reached
Key	In a browser	Not reached
First call	Headless	Not reached
First action	Headless	Not reached
Pay	Not tried	Not reached
Cancel	Not needed	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

Checkpoints by how our agent passed them, and what each product offers an agent
	GitHub	Trello
Headless (checkpoints)	3	1
In a browser (checkpoints)	1	1
Needs a human (checkpoints)	0	1
Blocked (checkpoints)	1	0
Not tested (checkpoints)	1	6
Work done	89% of the core	Not measured
API	Yes	Yes
OpenAPI	Yes	Yes
MCP server	Yes (official)	Yes (official)
CLI	Yes	No
SDK	–	No
llms.txt	Yes	No

Bot checks, and where a person was needed.

Walls our agent met
	GitHub	Trello
Bot check	A challenge on the form stopped one way in (Email and password); it got in another way	reCAPTCHA Enterprise (Atlassian sign-up) stopped it at sign up, with a visible challenge
Wall type	A challenge on the form	A challenge on the form
First wall	None	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.

GitHub and Trello: level and part scores, 0 to 100
	GitHub	Trello
Level	L4 · Runs on its own	L1 · Needs a person
Holds up	59 of 100, fair	Not measured
Agent-ready setup	100 of 100, good	70 of 100, fair
Standards	MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · OpenAPI 3.0.3 (2 versions 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.

Paying, cancelling and deleting the account
	GitHub	Trello
Pay	Payment not tried	Payment not reached
Free plan or trial	Free plan	Free plan
Cancel	Not needed	In a browser
Delete the account	Blocked	Not reached

How each one takes payment

GitHub: Not tried yet: robots.txt keeps our agent off the payment page for now.
Trello: Payment not reached.

GitHub vs Trello: the short answers.

Which can an AI agent use, GitHub or Trello?

GitHub gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With GitHub our agent went through every checkpoint; with Trello it was stopped at sign up (needs a human). Driven 13 Oct 2026 (GitHub) and 6 Oct 2026 (Trello).

Can an AI agent sign up for GitHub and Trello on its own?

GitHub: not needed. Trello: no, needs a human.

Do GitHub and Trello have an MCP server?

GitHub: yes (official). Trello: yes (official).

Can an AI agent delete its GitHub or Trello account?

GitHub: blocked. Trello: not reached.