# Teamwork.com > Teamwork.com is a hosted project management and professional services platform for client work, covering projects, tasks, time, resourcing and budgets. Agents reach it through REST API v3 and an official MCP server, hosted at mcp.ai.teamwork.com or run locally. - Canonical: https://www.anchorterminal.com/tools/teamwork - Markdown: https://www.anchorterminal.com/tools/teamwork.md (~8,300 tokens) - Slim: https://www.anchorterminal.com/tools/teamwork.min.md (~1,930 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/teamwork.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade B · 65.9/100 · rank #251 of 722 · #6 in Project & task management · not agent-ready · confidence medium** ## Assessment The official MCP server is MIT licensed, released almost daily, and has typed tools with annotations, profile endpoints and no delete tools on the shipped servers. OAuth scopes stop at product level, access tokens are permanent, and no SLA, API changelog or prompt-injection guidance was found in the reviewed documentation. ## Facts | Field | Value | | --- | --- | | Vendor | Teamwork Crew Limited (https://www.teamwork.com) | | Kind | HTTP API | | Category | Project & task management (https://www.anchorterminal.com/categories/project-management) | | Transport | HTTP, Streamable HTTP, SSE (legacy), stdio | | Endpoint | `https://mcp.ai.teamwork.com` | | Auth | OAuth or key · Self-serve. Any user with an active seat, client users and collaborators included, copies an API key from their profile and sends it over Basic auth, which the docs suggest for personal use and testing. Apps use the OAuth 2.0 authorisation code flow with a client ID and secret from the Developer Portal, or register themselves by dynamic client registration, with PKCE (S256). Scopes are per product (`projects`, `desk`, `spaces`, `chat`), and the token is described as permanent. An app works only on its own site until Teamwork verifies it for publication, which takes up to 5 working days. The MCP server takes the same bearer token or browser sign-in, after an administrator enables MCP under Settings, AI. | | Pricing | Freemium ($9.99 / seat-mo) · The API is open to every active user and Teamwork charges nothing per call. Free is $0 for up to 5 users and 5 projects, Basics $9.99 and Accelerate $24.99 a user a month billed annually (minimum 3 and 5 users), and the two larger plans are quoted by sales. A 14-day trial needs no card, so an agent's owner can start on Free or the trial without a contract. Webhooks need a paid plan, and the API rate limit rises with the plan (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the API docs, the MCP repository or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under Teamwork.com's terms of service. The MCP server on GitHub is MIT | | Tools exposed | 225 | | Packages | go: `github.com/teamwork/twapi-go-sdk`; npm: `@teamwork/get-bearer-token` | | Source | https://github.com/Teamwork/mcp | | Docs | https://apidocs.teamwork.com | | llms.txt | not found | | Last release | 2026-10-06 | | GitHub stars | 26 (as of 2026-10-08) | | Surfaces | REST API v3 at https://{site}.teamwork.com/projects/api/v3 (EU sites at {site}.eu.teamwork.com), with v1 and v2 still documented, and the official MCP server, hosted at https://mcp.ai.teamwork.com (Streamable HTTP, SSE at `/sse`) or run locally as `tw-mcp` over stdio | | MCP tools | 225 in the generated tool reference at v1.51.1. Projects 147 (tasks, tasklists, workflows, projects, milestones, comments, time, allocations, people), Desk 46, Spaces 24, Chat 8. No delete tools on the shipped servers | | MCP profiles | `/project-manager`, `/support` (alias `/desk`), `/analyst`, `/knowledge-manager` and `/ops`, each loading a subset of 14 toolsets | | Credentials | OAuth 2.0 authorisation code flow with PKCE (S256) and dynamic client registration, giving a bearer token the docs call permanent. Per-user API key or username and password over Basic auth for personal use | | Scopes | `projects`, `desk`, `spaces`, `chat`. Access inside a product follows the user's permissions | | Rate limits | 150 requests a minute on Free, Basics and Accelerate, 300 on the top self-serve plan, 500 on Enterprise, shared across the site. 429 with `X-Rate-Limit-Limit`, `X-Rate-Limit-Remaining` and `X-Rate-Limit-Reset` | | Pagination | `page` and `pageSize` (default 50, up to 500 on most v3 endpoints), a `meta.page` object with `hasMore`, sparse fieldsets through `fields[type]`, sideloading through `include`, and a cap of 50,000 records per query | | Contract | Swagger 2.0 file for API v3 with 319 paths and 430 operations, downloadable from each reference page | | Webhooks | Site and project webhooks on paid plans, with an optional token for an HMAC SHA-256 checksum in `X-Projects-Signature`. `fireWebhook=false` suppresses the event for one request | | SDKs | Go only. `github.com/teamwork/twapi-go-sdk` v1.35.0, plus `desksdkgo` and `spacessdkgo`. The npm package `@teamwork/get-bearer-token` 1.6.1 fetches a bearer token | | Free tier | Free plan at $0 for up to 5 users and 5 projects with 100 MB of storage. 14-day trial of paid plans with no card | | Certifications | ISO/IEC 27001:2022 and SOC 2 Type 2 per teamwork.com/security | | Status | status.teamwork.com on Statuspage, 22 components by product and region (US and EU) | | Sub-processors | AWS, Mailgun, Sendgrid, Datadog, DigitalOcean, Zapier, Clicktel, Sentry, LaunchDarkly and Pendo in the DPA, without locations. AI processing by AWS, OpenAI, Anthropic and Google | | Capabilities | tasks.create, tasks.update, projects.manage, tasks.comments, projects.reporting, automation.webhooks | | Tags | official, hosted, mcp, oauth, api-key, openapi, webhooks, freemium, free-tier, no-card, go, status-page, soc2 | | JSON | https://www.anchorterminal.com/api/v1/tools/teamwork.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 73 | 14.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 72 | 11.7 | | Agent ergonomics | 13% | 16.2 | 68 | 11.1 | | Security & auth | 14% | 17.5 | 58 | 10.2 | | Payments & pricing | 10% | 12.5 | 30 | 3.8 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 88 | 7.7 | | Transparency & trust (editorial 63, provenance 96) | 7% | 8.8 | 80 | 7.0 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **65.9 → B** | ### Why each score - Reliability 73: Graded on the hosted lines for REST API v3 and the hosted MCP server. status.teamwork.com is a Statuspage site with 22 components, among them Teamwork Projects for the US and EU regions, the Developer Portal and the API docs, though none for the API or the MCP server by name (20). In the 90 days to 8 October 2026 it lists one incident, a 40-minute problem with task creation in Projects in both regions on 24 September, marked with no impact level (20). The pricing page gives the API limit per plan, 150 requests a minute on Free, Basics and Accelerate, 300 on the plan above it and 500 on Enterprise (15). A 429 comes with `X-Rate-Limit-Limit`, `X-Rate-Limit-Remaining` and `X-Rate-Limit-Reset` and the guide says access returns after 60 seconds. No Retry-After header and no idempotency keys were found (8 of 15). No SLA found. The terms promise reasonable endeavours and the security page states a goal of over 99.9 per cent (0). API v3 and MCP server 1.x carry no beta label (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 72: A Swagger 2.0 file for API v3 downloads from each reference page (319 paths, 430 operations) with no security scheme declared, and every MCP tool has a typed JSON Schema input in the public source (23 of 25). apidocs.teamwork.com/llms.txt returns 404. The main site has an llms.txt about the company and a Markdown pricing page, and the MCP tool reference is Markdown on GitHub (3 of 10). MCP descriptions say when to use a tool and name pitfalls, for example that a workflow from another project is ignored without a warning. API parameter descriptions are one line each (15 of 20). Enums, minimums and maximums and required fields in both, with nullable unions on many MCP inputs (12 of 15). Reference pages show response examples and 400, 403, 404 and 409 responses, while the error guide is brief and has no error body format (10 of 15). The API is versioned v1, v2 and v3 and the MCP server has tagged releases on GitHub, but no changelog for the REST API was found (9 of 15). - Agent ergonomics 68: The generated tool reference lists 225 tools on the main MCP endpoint, 147 of them for Projects, which earns 5. Profile endpoints, 14 named toolsets, a `-read-only` flag on the local server and `verbose=false` on list tools add 9 back, and API v3 has sparse fieldsets (14 of 25). `page` and `pageSize` (default 50, up to 500 on most v3 endpoints), date, status and custom field filters, sorting and sideloading through `include` (20). MCP tools return text errors that name the bad parameter. The API error guide lists six status codes with causes and no body format (12 of 20). Tools carry readOnlyHint, destructiveHint and openWorldHint annotations, and batch tools validate every item before writing. No idempotency keys were found (12 of 20). Creating a task needs a name and a tasklist id. The one official SDK found is for Go (9 of 15). - Security & auth 58: OAuth 2.0 authorisation code flow with PKCE (S256) and dynamic client registration, with scopes at product level only (`projects`, `desk`, `spaces`, `chat`). The app login flow guide calls the access token permanent, and personal use is by a per-user API key or username and password over Basic auth. Credentials travel in the `Authorization` header (20 of 30). Every credential acts with its user's permissions. An administrator has to enable MCP for the site, the shipped servers register no delete tools, and the local server has a `-read-only` flag. The hosted server has no documented read-only mode or confirmation step (12 of 20). Task descriptions, comments, tickets and chat messages written by other people reach the model, and no injection guidance was found (3 of 15). An activity tool and a guide to project change history exist. No log of API or MCP calls for the operator was found (8 of 15). security.txt is valid until 17 July 2027 and names security@teamwork.com, the MCP repository has a security policy with a 48-hour acknowledgement, and the security page lists ISO/IEC 27001:2022 and SOC 2 Type 2. No bug bounty or public advisories found (15 of 20). - Payments & pricing 30: No x402, MPP or L402 (0). Plan prices are public, Free $0, Basics $9.99 and Accelerate $24.99 a user a month billed annually, with the two larger plans quoted by sales. API calls aren't priced (10). The Free plan covers up to 5 users and 5 projects, and the 14-day trial needs no card (20). A person signs up in a browser and creates the key or approves the OAuth app (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 88: MCP server v1.51.1 was tagged on 6 October 2026 (30). The repository has 57 tags between 27 July and 6 October 2026 (20). The GitHub API shows 3 open issues, and a bug report of 6 October (#581) was fixed and released the same day (20 of 25). The repository's `server.json` names `com.teamwork/mcp`, but the official MCP registry timed out on both attempts, so the entry is unchecked. The Go SDK `twapi-go-sdk` was last pushed on 1 October 2026 and is the only official SDK found (10 of 15). A test workflow runs on every push, and dependency updates are merged within days (8 of 10). - Transparency & trust 80: Closed service under terms naming Teamwork Crew Limited, with the MCP server, the Go SDK and the token helper open on GitHub and the MCP server under MIT (18 of 30). The privacy notice, last updated 19 August 2024, sends customer data to the DPA. The DPA and the terms agree that data is deleted after termination unless a copy is requested within 10 days, and the AI policy says customer data isn't used to train models. No retention periods are given (20 of 30). No written deprecation policy. The removal of localhost redirect URIs for dynamically registered OAuth apps was announced on 16 June 2026 for 1 August 2026 with Deprecation and Sunset headers, and the paging guide dates the end of total record counts to 6 January 2025 (12 of 20). The DPA lists ten sub-processors by function without locations, the AI list names AWS, OpenAI, Anthropic and Google with locations given as varying, and the security page says hosting is on AWS in the US and the EU (13 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (18 items): https://www.anchorterminal.com/fixes/teamwork.md (JSON https://www.anchorterminal.com/fixes/teamwork.json) ### What we couldn't check - unchecked: the official MCP registry. registry.modelcontextprotocol.io timed out on both attempts, so whether `com.teamwork/mcp` from the repository's `server.json` is published there was not established. - unchecked: the live tool list. tools/list on the hosted server answers 401 without a token, so the count of 225 and the annotations are read from the generated tool reference and the source at v1.51.1. - unchecked: whether the Free plan includes the MCP server and webhooks. The webhooks guide says webhooks need a paid plan, and the pricing page lists an API rate limit for Free. - unchecked: whether OAuth access tokens can be revoked by the user or expire. The app login flow guide calls the token permanent. - The rate limit guide still names the Grow and Scale plans (150 and 300 a minute), which the pricing page no longer lists. The listing uses the pricing page's figures. - The lead named Teamwork Crew Ltd. The terms and DPA name Teamwork Crew Limited, registered number 313652, trading as Teamwork.com. The lead gave only the REST API. Teamwork also has an official MCP server, which the listing grades alongside the API. - www.teamwork.com/llms.txt has a section of instructions addressed to AI assistants on how to describe the company. Recorded as a fact, with no deduction, and not acted on. - No REST API changelog, SLA, bug bounty or audit log of API calls was found in the pages read. The trust reports behind the security page's Learn more links were not read. - Terms carry no visible version date. The privacy notice says it was last updated on 19 August 2024. ### Sources - API docs home: (seen 2026-10-08) - API getting started (site URL, API key, who has access): (seen 2026-10-08) - authentication guide: (seen 2026-10-08) - app login flow (OAuth 2.0): (seen 2026-10-08) - developer portal and app verification: (seen 2026-10-08) - rate limit guide: (seen 2026-10-08) - error codes guide: (seen 2026-10-08) - paging guide: (seen 2026-10-08) - sparse fieldsets guide: (seen 2026-10-08) - webhooks setup: (seen 2026-10-08) - deprecation notice for localhost redirect URIs: (seen 2026-10-08) - sunset notice for localhost redirect URIs: (seen 2026-10-08) - API reference index: (seen 2026-10-08) - create task reference: (seen 2026-10-08) - list tasks reference: (seen 2026-10-08) - Swagger 2.0 file for API v3: (seen 2026-10-08) - MCP server repository (README, tool reference, usage guides, source, tags): (seen 2026-10-08) - MCP tool reference: (seen 2026-10-08) - MCP protected resource metadata: (seen 2026-10-08) - OAuth authorisation server metadata: (seen 2026-10-08) - GitHub API, repository and issues: (seen 2026-10-08) - pricing in Markdown: (seen 2026-10-08) - site llms.txt: (seen 2026-10-08) - status incidents feed: (seen 2026-10-08) - status components feed: (seen 2026-10-08) - security page: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - terms of service: (seen 2026-10-08) - privacy notice: (seen 2026-10-08) - data processing agreement and sub-processors: (seen 2026-10-08) - AI policy: (seen 2026-10-08) - AI sub-processors: (seen 2026-10-08) - RDAP for teamwork.com: (seen 2026-10-08) ## Who's behind it (provenance 96/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Teamwork Crew Limited | 20/20 | | Domain age | teamwork.com, registered 1995-03-29 (31 years) | 15/15 | | Endpoint on the vendor's domain | mcp.ai.teamwork.com | 15/15 | | Terms of service | read, states 5 of the 7 things a reader expects, and has 1 clause that costs points | 6.3/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.teamwork.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The terms of service are between the customer and Teamwork Crew Limited. The DPA gives registered number 313652 and a registered office at Teamwork Campus 1, Park House, Blackpool Retail Park, Blackpool, Cork, T23 F902, Ireland, trading as Teamwork.com. The terms govern the hosted service and incorporate the DPA. The privacy notice, last updated 19 August 2024, covers the websites and the platform and refers customer data processed for customers to the DPA. The API answers on each customer's teamwork.com subdomain and the MCP server at mcp.ai.teamwork.com. www.teamwork.com/.well-known/security.txt names security@teamwork.com and expires on 17 July 2027. RDAP for teamwork.com gives a registration date of 1995-03-29. The changelog link is the MCP server's GitHub releases. No changelog for the REST API was found. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.teamwork.com/legal/terms-of-service/), read 2026-10-08, gives no date, states 5 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "access all or any part of the Services in order to build a product or service which competes with the Services and/or any documentation provided in relation to the Service by Teamwork.com; or" - To know. Says access can be ended without notice or for any reason. "Teamwork.com may terminate this Agreement with immediate effect without cause by giving five (5) days written notice to the Customer." - Not found in the text. Gives the date it was last updated. - Says how changes to the terms are announced. Gives 5 business days of notice before a change. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Teamwork.com may at its sole discretion charge additional fees if it believes the customer or its users have misused the services or used them excessively. "use the Services in an excessive manner compared to the anticipated standard use (for instance, an inappropriate use of features etc.), to impose additional fees for the continued use of the Services." - Also in the text (2026-10-08). After termination Teamwork.com may destroy customer data unless it receives a written request for the latest back-up within ten days. "Teamwork.com may destroy or otherwise dispose of any of the Customer Data in its possession unless Teamwork.com receives, no later than ten (10) days after the effective date of the termination of this Agreement, a written request for the delivery to the Customer" - Also in the text (2026-10-08). For customers on a monthly subscription, total liability is limited to the subscription fees paid in the month before the claim arose. "for Customers whose Subscription Period is monthly, to the total Subscription Fees paid by the Customer for the Service Subscriptions in the month preceding the date on which the claim arose; and" **Privacy policy** (https://www.teamwork.com/legal/privacy-notice/), read 2026-10-08, dated 2024-08-19, states 7 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2024-08-19. - Says how long data is kept. For as long as needed, with no period named. - Not found in the text. Says whether personal data is sold or shared for advertising. - Gives a privacy contact. Names a data protection officer. - Says where data is transferred or stored. Relies on standard contractual clauses. - Also in the text (2026-10-08). Teamwork.com says it collects, uses and shares aggregated data derived from personal data for any purpose. "We also collect, use and share Aggregated Data such as statistical or demographic data for any purpose." ## Live (updated 2026-10-08 21:58 UTC) - Right now: up, HTTP 401, 414 ms, checked 2026-10-08 21:53 UTC (get on `https://mcp.ai.teamwork.com`, asks for auth) - Uptime 24h 100.0% (28 probes) · 30 days 100.0% (28 probes) · p50 336 ms · p95 414 ms - Vendor status page: none, All Systems Operational - Always current: https://www.anchorterminal.com/api/v1/live/teamwork.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Free (API included) | free | per seat per month | Up to 5 users and 5 projects | | Basics | $9.99 | per seat per month | Billed annually, minimum 3 users, as shown on 2026-10-08 | | Accelerate | $24.99 | per seat per month | Billed annually, minimum 5 users, as shown on 2026-10-08 | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Official MCP server under MIT at https://mcp.ai.teamwork.com, with profile endpoints such as `/project-manager` that load a subset of tools - No delete tool reaches a client. Delete operations sit behind an `allowDelete` flag that no shipped server enables - A Swagger 2.0 file for API v3 downloads from the docs, with 319 paths and 430 operations - OAuth 2.0 authorisation code flow with PKCE (S256) and dynamic client registration, per the authorisation server metadata - The Free plan (up to 5 users) and the 14-day trial need no card, and the pricing page gives an API rate limit for every plan ## Weaknesses - OAuth scopes are per product only (`projects`, `desk`, `spaces`, `chat`), and the token from the app login flow is described as permanent - The main MCP endpoint loads every tool. The generated tool reference lists 225, 147 of them for Projects - 429 responses carry `X-Rate-Limit-Reset` but no Retry-After, and no idempotency keys were found - No SLA found. The terms promise reasonable endeavours and the security page states a 99.9 per cent uptime goal - No changelog for the REST API was found, and the docs site has no llms.txt ## Before you call it (notes for agents) 1. Use a profile endpoint such as https://mcp.ai.teamwork.com/project-manager. The base URL loads every tool across Projects, Desk, Spaces and Chat. 2. Ask a site administrator to enable MCP under Settings, AI before connecting. 3. Build REST URLs from `installation.apiEndPoint` in the token response. Sites live at {site}.teamwork.com (US) or {site}.eu.teamwork.com (EU). 4. Stay under 150 requests a minute on Free, Basics and Accelerate. The limit is shared by the whole site. On 429, wait until `X-Rate-Limit-Reset`. 5. Pass `verbose=false` to `list_*` tools to get ids and names only, and use `twprojects-create_tasks` for many tasks in one call. ## Connect First request: ```bash curl -i https://{yourSiteName}.teamwork.com/projects/api/v3/projects.json -H "Authorization: Bearer {token}" ``` Claude Code: ```bash claude mcp add --transport http teamwork https://mcp.ai.teamwork.com/ ``` MCP client configuration: ```json { "mcpServers": { "Teamwork.com": { "args": [], "command": "tw-mcp", "env": { "TW_MCP_BEARER_TOKEN": "\u003ctoken\u003e" } } } } ``` Through letme (picks today, calling later): https://letme.dev/teamwork. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Shortcut | C | 60.2 | 411 | tasks.create, tasks.update, projects.manage, tasks.comments, projects.reporting, automation.webhooks | no | https://www.anchorterminal.com/tools/shortcut.md | | Wrike | C | 60.1 | 413 | tasks.create, tasks.update, projects.manage, tasks.comments, projects.reporting, automation.webhooks | no | https://www.anchorterminal.com/tools/wrike.md | | monday.com | BB | 76.4 | 32 | tasks.create, tasks.update, projects.manage, tasks.comments, projects.reporting | no | https://www.anchorterminal.com/tools/monday.md | | Asana | BB | 70.1 | 141 | tasks.create, tasks.update, projects.manage, tasks.comments, projects.reporting | no | https://www.anchorterminal.com/tools/asana.md | | Basecamp | B | 67.9 | 197 | tasks.create, tasks.update, projects.manage, tasks.comments, projects.reporting | no | https://www.anchorterminal.com/tools/basecamp.md | | Plane | B | 67.6 | 204 | tasks.create, tasks.update, projects.manage, tasks.comments, projects.reporting | no | https://www.anchorterminal.com/tools/plane.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The hosted MCP server answers at https://mcp.ai.teamwork.com over Streamable HTTP and at `/sse`, with profile endpoints `/project-manager`, `/support`, `/analyst`, `/knowledge-manager` and `/ops` (source: ) - The generated tool reference lists create, get, list and update tools across Projects, Desk, Spaces and Chat, and says delete operations are gated behind an `allowDelete` flag that no shipped server enables (source: ) - The authorisation server metadata lists the authorisation code grant, S256 code challenges, a registration endpoint and the scopes `projects`, `desk`, `spaces` and `chat` (source: ) - Localhost redirect URIs for dynamically registered OAuth apps were deprecated on 16 June 2026 and refused from 1 August 2026, with Deprecation and Sunset headers in between (source: ) - The API rate limit is shared by the whole site, 150 requests a minute on Free, Basics and Accelerate, 300 on the plan above it and 500 on Enterprise (source: ) - A Swagger 2.0 file for API v3 with 319 paths and 430 operations downloads from the reference pages (source: ) - www.teamwork.com/llms.txt has a section of instructions addressed to AI assistants on how to describe the company. It is recorded here as a fact about the page (source: ) ## Compare - [Asana vs Teamwork.com](https://www.anchorterminal.com/compare/asana-vs-teamwork.md): BB 70.1 vs B 65.9 - [Basecamp vs Teamwork.com](https://www.anchorterminal.com/compare/basecamp-vs-teamwork.md): B 67.9 vs B 65.9 - [ClickUp vs Teamwork.com](https://www.anchorterminal.com/compare/clickup-vs-teamwork.md): C 60.9 vs B 65.9 - [monday.com vs Teamwork.com](https://www.anchorterminal.com/compare/monday-vs-teamwork.md): BB 76.4 vs B 65.9 - [Plane vs Teamwork.com](https://www.anchorterminal.com/compare/plane-vs-teamwork.md): B 67.6 vs B 65.9 - [Roma vs Teamwork.com](https://www.anchorterminal.com/compare/roma-vs-teamwork.md): D 51.1 vs B 65.9 - [Shortcut vs Teamwork.com](https://www.anchorterminal.com/compare/shortcut-vs-teamwork.md): C 60.2 vs B 65.9 - [Teamwork.com vs Todoist](https://www.anchorterminal.com/compare/teamwork-vs-todoist.md): B 65.9 vs B 66.9 - [Teamwork.com vs Trello](https://www.anchorterminal.com/compare/teamwork-vs-trello.md): B 65.9 vs C 61.1 - [Teamwork.com vs Wrike](https://www.anchorterminal.com/compare/teamwork-vs-wrike.md): B 65.9 vs C 60.1 - [Teamwork.com vs YouTrack](https://www.anchorterminal.com/compare/teamwork-vs-youtrack.md): B 65.9 vs D 49.9 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on teamwork.com or one of its subdomains, or the README of github.com/Teamwork/mcp. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "teamwork", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Teamwork.com on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Teamwork.com on Anchor Terminal](https://www.anchorterminal.com/badges/teamwork.svg)](https://www.anchorterminal.com/tools/teamwork) ``` Plain link: ```html Teamwork.com on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Teamwork.com is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/teamwork-dark.png - Light: https://www.anchorterminal.com/assets/share/teamwork-light.png