Jira vs Teamwork.com for AI agents

As of 14 Oct 2026, both reach L1 · Needs a person, and our agent got as far with each: with Jira it was stopped at sign up (needs a human), with Teamwork.com it was stopped at sign up (blocked).

JiraL1Needs a person

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.

Stopped at sign up: needs a human. Next: let an agent sign up on its own

An agent cannot get into Jira on its own: both email sign-ups are stopped by reCAPTCHA (an invisible score refusal, then a visible checkbox). The docs, llms.txt and the official MCP server's OAuth metadata (PRM, DCR) are agent-friendly, but every capability sits behind an account, so none could be driven.

Driven 14 Oct 2026 · The drive and its evidence

Teamwork.comL1Needs a person

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: blocked. Next: let an agent sign up on its own

Needs a person. Sign-up stops at the account form: after passing an invisible reCAPTCHA, it asks for a phone number our agent did not have, and no human supplied one. The account was never created. With no account, the key page, the official MCP server and the Swagger-documented endpoints stayed out of reach. Our agent got only an unauthenticated 401 from the API and from MCP's tools list, and no work was attempted. The pricing page lists a trial without a card and payment by card or bank transfer, but checkout sits behind the same sign-up form: our agent never reached it, and never had an account to cancel or delete.

Driven 6 Oct 2026 · The drive and its evidence

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

Where each one stops.

JiraStopped at sign up: needs a human

Teamwork.comStopped at sign up: blocked

Jira and Teamwork.com, checkpoint by checkpoint
Checkpoint	Jira	Teamwork.com
Docs	Headless	Headless
Sign up	Needs a human	Blocked
Verify	Not reached	Not reached
Key	Not reached	Not reached
First call	Not reached	Not reached
First action	Not reached	Not reached
Pay	Not reached	Not reached
Cancel	Not reached	Not reached
Delete	Not reached	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
	Jira	Teamwork.com
Headless (checkpoints)	1	1
In a browser (checkpoints)	0	0
Needs a human (checkpoints)	1	0
Blocked (checkpoints)	0	1
Not tested (checkpoints)	7	7
Work done	Not measured	Not measured
API	Yes	Yes
OpenAPI	Yes	Yes
MCP server	Yes (official)	Yes (official)
CLI	Yes	No
SDK	No	No
llms.txt	Yes	Yes

Bot checks, and where a person was needed.

Walls our agent met
	Jira	Teamwork.com
Bot check	Google reCAPTCHA (score, captcha_type=google-score) stopped it at sign up, without a visible challenge	reCAPTCHA (invisible) let it through at sign up
Wall type	A check of our network and browser	No bot-check wall
First wall	reCAPTCHA on the Atlassian sign-up	Phone number required at sign-up
A person helped	No	No

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.

Jira and Teamwork.com: level and part scores, 0 to 100
	Jira	Teamwork.com
Level	L1 · Needs a person	L1 · Needs a person
Agent-ready setup	100 of 100, good	90 of 100, good
Standards	MCP client registration (behind) · OpenAPI 3.0.1 (2 versions behind)	MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · MCP client registration (behind) · OpenAPI 2.0 (3 versions behind)

Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.

Pay, cancel and delete.

Paying, cancelling and deleting the account
	Jira	Teamwork.com
Pay	Payment not reached	Payment not reached
Free plan or trial	Free plan	Trial, no card
Cancel	Not reached	Not reached
Delete the account	Not reached	Not reached

How each one takes payment

Jira: Payment not reached.
Teamwork.com: Payment not reached.

Jira vs Teamwork.com: the short answers.

Which can an AI agent use, Jira or Teamwork.com?

Both reach L1 · Needs a person, and our agent got as far with each: with Jira it was stopped at sign up (needs a human), with Teamwork.com it was stopped at sign up (blocked). Driven 14 Oct 2026 (Jira) and 6 Oct 2026 (Teamwork.com).

Can an AI agent sign up for Jira and Teamwork.com on its own?

Jira: no, needs a human. Teamwork.com: no, blocked.

Do Jira and Teamwork.com have an MCP server?

Jira: yes (official). Teamwork.com: yes (official).

Can an AI agent delete its Jira or Teamwork.com account?

Jira: not reached. Teamwork.com: not reached.