Model Context Protocol
The Teamwork.com MCP server publishes Projects, Desk, Spaces and Chat as a typed toolset. A connected client reads the catalogue below on connect, so it knows which operations exist and what each one needs — and every call runs with the permissions of the account that authorised it, nothing more.
The hosted server speaks streamable HTTP and authenticates with OAuth. Point a client at the endpoint and it discovers everything on this page automatically.
Loads every toolset. A local STDIO binary is available too — see the usage guide.
https://mcp.ai.teamwork.com
A narrower tool list keeps a client focused. Each profile is a fixed set of toolsets, served on its own path.
| Profile | Toolsets |
|---|---|
https://mcp.ai.teamwork.com/analyst |
Projects — Projects, Tasks, People, Planning, Time, Content; Desk — Tickets, Customers, Admin |
https://mcp.ai.teamwork.com/desk |
Desk — Tickets, Customers |
https://mcp.ai.teamwork.com/knowledge-manager |
Spaces — Spaces, Pages, Content |
https://mcp.ai.teamwork.com/ops |
Every toolset |
https://mcp.ai.teamwork.com/project-manager |
Projects — Projects, Tasks, People, Planning, Content |
https://mcp.ai.teamwork.com/support |
Desk — Tickets, Customers |
Generated from the server's own toolset registry, so it matches what a client actually receives. Each toolset opens with a coverage matrix — which resources support create, get, list and update — followed by every tool it publishes.
No tool matches that filter.
Comments, notebooks, milestones, tags, and activity feeds in Teamwork.com.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Activity | — | — | ✓ | — |
| Comment | ✓ | ✓ | ✓ | ✓ |
| Milestone | ✓ | ✓ | ✓ | ✓ |
| Notebook | ✓ | ✓ | ✓ | ✓ |
| Tag | ✓ | ✓ | ✓ | ✓ |
| Message | ✓ | ✓ | ✓ | ✓ |
| Message Reply | ✓ | ✓ | ✓ | ✓ |
| Link | ✓ | ✓ | ✓ | ✓ |
Tools
Users, companies, teams, skills, and job roles in Teamwork.com.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Company | ✓ | ✓ | ✓ | ✓ |
| Industry | — | — | ✓ | — |
| Job Role | ✓ | ✓ | ✓ | ✓ |
| Skill | ✓ | ✓ | ✓ | ✓ |
| Team | ✓ | ✓ | ✓ | ✓ |
| User | ✓ | ✓ | ✓ | ✓ |
| Current User (me) | — | ✓ | — | — |
Tools
Resource scheduling in Teamwork.com: allocations, which commit a person's time to a project, and the workload view of the time their assigned tasks are estimated to take. The two are separate planes of planning and are not summed.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Allocation | ✓ | ✓ | ✓ | ✓ |
Tools
Project, category, template, member, custom field, and custom item (user-defined entity types like Contracts, Leads, Deals) management in Teamwork.com.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Project Category | ✓ | ✓ | ✓ | ✓ |
| Project | ✓ | ✓ | ✓ | ✓ |
| Project Template | ✓ | — | ✓ | — |
| Custom Field | ✓ | ✓ | ✓ | ✓ |
| Custom Field Value | ✓ | ✓ | ✓ | ✓ |
| Custom Item | ✓ | ✓ | ✓ | ✓ |
| Custom Item Field | ✓ | ✓ | ✓ | ✓ |
| Custom Item Record | ✓ | ✓ | ✓ | ✓ |
| File | ✓ | — | — | — |
Tools
Task, tasklist, and workflow management in Teamwork.com.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Task | ✓ | ✓ | ✓ | ✓ |
| Tasklist | ✓ | ✓ | ✓ | ✓ |
| Workflow | ✓ | ✓ | ✓ | ✓ |
| Workflow Stage | ✓ | ✓ | ✓ | ✓ |
Tools
Time tracking via timelogs, timers, calendars with time blocking, and budget reporting in Teamwork.com.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Calendar Event | — | — | ✓ | — |
| Calendar | — | — | ✓ | — |
| Project Budget | — | — | ✓ | — |
| Tasklist Budget | — | — | ✓ | — |
| Timelog | ✓ | ✓ | ✓ | ✓ |
| Timer | ✓ | ✓ | ✓ | ✓ |
Tools
Inbox configuration: priorities, statuses, types, and tags in Teamwork Desk.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Priority | ✓ | ✓ | ✓ | ✓ |
| Status | ✓ | ✓ | ✓ | ✓ |
| Tag | ✓ | ✓ | ✓ | ✓ |
| Ticket Type | ✓ | ✓ | ✓ | ✓ |
Tools
Companies, customers, and user management in Teamwork Desk.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Company | ✓ | ✓ | ✓ | ✓ |
| Customer | ✓ | ✓ | ✓ | ✓ |
| User | — | ✓ | ✓ | — |
Tools
Help doc articles and sites in Teamwork Desk.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Helpdoc Article | ✓ | ✓ | — | ✓ |
| Helpdoc Site | — | ✓ | ✓ | — |
Tools
Tickets, messages, files, and inboxes in Teamwork Desk.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Inbox | — | ✓ | ✓ | — |
| Ticket | ✓ | ✓ | — | ✓ |
| File | ✓ | — | — | — |
Tools
Comments, tags, categories, and search in Teamwork Spaces.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Comment | ✓ | ✓ | ✓ | ✓ |
| Tag | ✓ | ✓ | ✓ | ✓ |
| Category | ✓ | ✓ | ✓ | ✓ |
Tools
Page CRUD, homepage, and duplication in Teamwork Spaces.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Page | ✓ | ✓ | ✓ | ✓ |
| Homepage | — | ✓ | — | — |
Tools
Space CRUD and collaborators in Teamwork Spaces.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Space | ✓ | ✓ | ✓ | ✓ |
| Space Collaborator | — | — | ✓ | — |
Tools
Read conversations, messages, and people, and send messages in Teamwork Chat.
Resource coverage
| Resource | Create | Get | List | Update |
|---|---|---|---|---|
| Current User | — | ✓ | — | — |
| Conversation | — | ✓ | ✓ | — |
| Message | — | — | ✓ | — |
| People | — | — | ✓ | — |
Tools
The catalogue above is the whole story for a hosted client — there is no second, wider set of tools behind it.
Every call is made as the account that authorised the connection, so a client can only read and change what that person already could in the Teamwork.com UI.
Delete tools exist in the codebase but sit behind an allowDelete flag that no shipped server turns on, so no client can call one. That is why no delete_* tool appears above.
Running a server with -read-only drops every write tool, leaving the 107 read tools listed above. Scopes narrow it further: a token carries one scope per product.