Is Teamwork.com agent-ready?

Teamwork.com scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is MCP and agent posture; its weakest is schema observability.

Does Teamwork.com publish an OpenAPI spec?

No published OpenAPI specification was found when Teamwork.com was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.

What is Teamwork.com's Headless Index score?

Teamwork.com scores 57/100 on the Headless Index thesis-fit rubric and sits in Band C in the Project & Task Management category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Project & Task Management

Teamwork.com

Headless Index

57/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Teamwork.com earns Band C in the Project & Task Management category of The Headless Index, with a thesis-fit score of 57/100. Its strongest dimension is MCP and agent posture (15/20); its weakest scored dimension is schema observability (8/20). No public OpenAPI specification was found when Teamwork.com was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Teamwork.com is partially headless and partly UI-led. The Headless Index thesis-fit score of 57/100 puts it mid-table on the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where Teamwork.com lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Teamwork runs a versioned REST surface at {site}.teamwork.com/projects/api/v3 alongside a still-live v1, which is a migration burden agents inherit. Client coverage is Go only and thin (github.com/Teamwork/twapi-go-sdk, two stars), plus desksdkgo and spacessdkgo for the sibling products. No JavaScript, Python or Ruby package exists, so most integrators hand roll HTTP against the docs portal. An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: Projects, tasklists, tasks, milestones, time entries and people are all addressable, so an agent can run delivery work end to end. Provisioning is not: installation settings, permission templates, project templates and the Desk and Spaces tie-ins are configured in the browser. No CLI, no Terraform provider, no self-host option (teamwork.com is cloud only).^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Teamwork ships a genuine first party server (github.com/Teamwork/mcp), written in Go, with commits landing the same week this was checked and 24 stars. Coverage reaches across Projects and Desk rather than one product. What is missing is packaging: no published binary or npm wrapper, no registry.modelcontextprotocol.io entry, and no dedicated agent documentation on the developer site.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Webhooks are managed through the API and the catalogue is broad, spanning task, milestone, comment, timelog and project triggers (PROJECT.CREATED, TASK.COMPLETED, TIMELOG.CREATED). Payloads mirror the v1 object shapes rather than v3, which is an inconsistency agents must absorb. Signing and retry behaviour are underdocumented; the developer portal does not state a verification header or a backoff policy. Net assessment: integrators can build agent flows against Teamwork.com, but the rough edge to plan around is schema observability^[3]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent12/20

scored

Teamwork runs a versioned REST surface at {site}.teamwork.com/projects/api/v3 alongside a still-live v1, which is a migration burden agents inherit. Client coverage is Go only and thin (github.com/Teamwork/twapi-go-sdk, two stars), plus desksdkgo and spacessdkgo for the sibling products. No JavaScript, Python or Ruby package exists, so most integrators hand roll HTTP against the docs portal.

signals (5)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 34 probe paths
−GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
+SDKs maintained3 (go); top by stars: Teamwork/twapi-go-sdk (2 stars)
+SDK recency2 of 3 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-19)

cite (1)

ai_review_browser.auth@2026-08-19

Headless operation10/20

scored

Projects, tasklists, tasks, milestones, time entries and people are all addressable, so an agent can run delivery work end to end. Provisioning is not: installation settings, permission templates, project templates and the Desk and Spaces tie-ins are configured in the browser. No CLI, no Terraform provider, no self-host option (teamwork.com is cloud only).

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
−API operations exposedNo OpenAPI spec; operations count unknown
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

ai_review_browser.topics_found@2026-08-19

MCP & agent posture15/20

scored

Teamwork ships a genuine first party server (github.com/Teamwork/mcp), written in Go, with commits landing the same week this was checked and 24 stars. Coverage reaches across Projects and Desk rather than one product. What is missing is packaging: no published binary or npm wrapper, no registry.modelcontextprotocol.io entry, and no dedicated agent documentation on the developer site.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+Official MCP serverhttps://github.com/Teamwork/mcp (24 stars, last commit 0 days ago)
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability8/20

scored

The developer portal at apidocs.teamwork.com renders endpoint by endpoint, but no machine readable document backs it; probes for spec.json and openapi.json return 404, and there is no spec repository under the org (github.com/Teamwork). The Go SDK is the closest thing to a typed contract. An agent must scrape HTML or read prose to learn field shapes.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 34 standard probe paths
−GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)

cite (1)

github.sdks@2026-08-19

Webhooks & events12/20

scored

Webhooks are managed through the API and the catalogue is broad, spanning task, milestone, comment, timelog and project triggers (PROJECT.CREATED, TASK.COMPLETED, TIMELOG.CREATED). Payloads mirror the v1 object shapes rather than v3, which is an inconsistency agents must absorb. Signing and retry behaviour are underdocumented; the developer portal does not state a verification header or a backoff policy.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

github.sdks@2026-08-19

JAIRF · 6 dimensions

JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Band rationale:C band: scores 40-75 range

04 / Embed

Show Teamwork.com's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Peers in Project & Task Management

ProductboardC

Headless Index 56/100

monday.comC

Headless Index 56/100

HeightC

Headless Index 56/100

See full Project & Task Management ranking →

FAQ

Teamwork.com and agent readiness

Is Teamwork.com agent-ready?: Teamwork.com scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is MCP and agent posture; its weakest is schema observability.
Does Teamwork.com publish an OpenAPI spec?: No published OpenAPI specification was found when Teamwork.com was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Teamwork.com's Headless Index score?: Teamwork.com scores 57/100 on the Headless Index thesis-fit rubric and sits in Band C in the Project & Task Management category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.