GitHub vs Wrike for AI agents
As of 13 Oct 2026, GitHub 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: 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- Find: Docs for agents: llms.txt, 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
L1 · Needs a person: someone else has to sign up, verify and make the key before an agent can work. Our agent stopped at signup, where the registration call to reg.wrike.com hit a Cloudflare managed challenge and never cleared. No account followed, so verification, a key and every REST or MCP call stayed out of reach: both answer unauthenticated. Docs are ready for an agent to read first: llms.txt, Markdown pages, an OpenAPI catalog, an official MCP server, but none of that could be exercised. Paying and leaving stayed out of reach too: plans are bought in the app after sign-up, and deleting a free or expired account needs the web UI with a password.
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.
GitHubThrough every checkpoint
WrikeStopped at sign up: needs a human
| Checkpoint | GitHub | Wrike |
|---|---|---|
| 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 | Not reached |
| 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
| GitHub | Wrike | |
|---|---|---|
| Headless (checkpoints) | 3 | 1 |
| In a browser (checkpoints) | 1 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 1 | 7 |
| 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 | Yes |
Bot checks, and where a person was needed.
| GitHub | Wrike | |
|---|---|---|
| Bot check | A challenge on the form stopped one way in (Email and password); it got in another way | Cloudflare managed challenge (cf-mitigated: challenge) on reg.wrike.com stopped it at sign up, with a visible challenge |
| Wall type | A challenge on the form | A check of our network and browser |
| First wall | None | Cloudflare challenge on the sign-up endpoint |
| 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. A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. Where we drive from.
Level and part scores.
| GitHub | Wrike | |
|---|---|---|
| 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 | 90 of 100, good |
| Standards | MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · OpenAPI 3.0.3 (2 versions behind) | OpenAPI 3.0.1 (2 versions behind) |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| GitHub | Wrike | |
|---|---|---|
| Pay | Payment not tried | Payment not reached |
| Free plan or trial | Free plan | Trial, no card |
| Cancel | Not needed | Not reached |
| 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.
- Wrike: Payment not reached.
GitHub vs Wrike: the short answers.
Which can an AI agent use, GitHub or Wrike?
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 Wrike it was stopped at sign up (needs a human). Driven 13 Oct 2026 (GitHub) and 6 Oct 2026 (Wrike).
Can an AI agent sign up for GitHub and Wrike on its own?
GitHub: not needed. Wrike: no, needs a human.
Do GitHub and Wrike have an MCP server?
GitHub: yes (official). Wrike: yes (official).
Can an AI agent delete its GitHub or Wrike account?
GitHub: blocked. Wrike: 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.