Teamwork
Teamwork is a project management platform for planning projects, coordinating tasks, collaborating with teams, and tracking time.
Verdict
Common use cases
- Log action items during planning calls
- Check milestone deadlines before sprint kickoff
- Assign tasks to teammates from chat
- Filter overdue work by tag or assignee
- Pull project status into standup summaries
Integration
- Vendor
- Teamwork
- Category
- productivity
- Auth
- API_KEY
- Tools
- 12
- Composio slug
teamwork
Tools
- Create Tag
Create a Teamwork tag, or return the existing installation tag when the same name already exists.
- Create Task
Create a task in a Teamwork task list with common scheduling, assignment, estimate, privacy, and tag fields.
- List Milestones
List visible Teamwork milestones by project, status, due-date range, assignee, or text. Returns one page and an opaque continuation cursor.
- List People
List people visible to the connected Teamwork user for assignment and ownership workflows.
- List Projects
List projects visible to the connected Teamwork user, with focused filters for name, status, company, membership, and archival state. Returns one page and an opaque continuation cursor.
- List Tags
List Teamwork tags visible to the connected user, optionally filtered by project, item type, name, or usage. Returns one page and an opaque continuation cursor.
- List Task Lists
List Teamwork task lists, usually within one or more projects, so an agent can place or locate tasks.
- List Tasks
List and filter Teamwork tasks by project, task list, assignee, dates, completion state, or tags. Returns one page and an opaque cursor for continuation.
- List Time Entries
List accessible Teamwork time entries by project, task, person, date range, billing state, or tags. Returns one page and an opaque continuation cursor.
- Log Time Entry
Log time against a Teamwork task with a date, duration, optional start time, description, person, billing state, and tags without changing task status.
- Search Teamwork
Search across Teamwork projects, tasks, task lists, milestones, people, companies, time entries, and other supported item types. Returns one page of lightweight references, optional sideloaded details, and a continuation cursor.
- Update Task
Update selected fields of an existing Teamwork task while leaving omitted task fields unchanged.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find Teamwork in the MCP directory and click Connect. 3. You'll be prompted to paste a Teamwork API key — generate one by logging into Teamwork, visiting your profile settings, and creating a new API token under Integrations or API Access. 4. Copy the token and paste it into Switchy's prompt, then click Authorize. 5. Switchy will verify the key and confirm which Teamwork projects the connected user can access. 6. Open any Project in Switchy and type '@Teamwork list projects' to test the connection — you should see a list of active projects. 7. To create a task, try '@Teamwork create task in [task list name]: [task title]' and confirm it appears in Teamwork.
What teammates see: by default, memories from Teamwork are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Overdue Tasks
@Teamwork list all tasks that are overdue, grouped by assignee. Include the task name, due date, and project.
Create Follow-Up Task
@Teamwork create a task in the Marketing task list called 'Draft Q2 campaign brief' and assign it to Sarah, due next Friday.
Check Sprint Milestones
@Teamwork list all milestones due in the next 7 days across active projects. Show the milestone name, project, and due date.
Filter by Tag
@Teamwork list all tasks tagged 'client-facing' that are incomplete. Include the assignee and project name.
Summarize Project Status
@Teamwork show me all open tasks and milestones for the Website Redesign project. Group tasks by task list and highlight anything due this week.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@teamwork list all overdue tasks assigned to Sarah across our active projects, grouped by project name
Found 7 overdue tasks assigned to Sarah Chen across 3 active projects. In 'Q1 Product Launch': 3 tasks overdue (oldest: 'Finalize pricing tier copy' due Jan 15). In 'Customer Onboarding Redesign': 2 tasks overdue including 'Review wireframe feedback'. In 'Marketing Site Refresh': 2 tasks overdue. Each task includes its task list, due date, and current tags. This view helps identify where Sarah's workload needs immediate attention or reassignment.
This example uses list-tasks filtering by assignee and date range. The MCP returns one page at a time with a continuation cursor — if Sarah has dozens of overdue tasks across many projects, you'll need to paginate. Requires read access to the projects where Sarah is assigned work.
@teamwork create a task in the 'Website Updates' project called 'Add testimonial carousel to homepage' assigned to Marcus, due next Friday, tagged 'design-review'
Created task 'Add testimonial carousel to homepage' in the 'Website Updates' project under the 'Design Tasks' task list. Assigned to Marcus Rivera with a due date of January 24, 2025. Applied the 'design-review' tag so it appears in your weekly design triage. Task ID is TW-4721 and is now visible in Marcus's task queue. If the 'design-review' tag didn't exist, the MCP created it automatically for this installation.
This example demonstrates task creation with assignment, scheduling, and tagging in one prompt. The MCP needs the project name or ID and will place the task in an appropriate task list (you can specify one if needed). Requires write permissions on the target project and the ability to assign tasks to Marcus.
@teamwork show me all milestones due in the next 30 days, then draft a status email summarizing progress and blockers for each one
Retrieved 4 milestones due by February 20: 'Beta Launch' (Jan 28, 87% task completion), 'Q1 Marketing Campaign Kickoff' (Feb 5, 62% complete, 3 overdue tasks blocking), 'API v2 Documentation' (Feb 12, on track), and 'Sales Deck Refresh' (Feb 18, not started, assigned to external agency). Draft email: 'Team — here's our milestone outlook for the next month. Beta Launch is nearly ready with one backend task remaining. Marketing Campaign has three blockers we need to resolve this week…' The summary highlights completion rates and flags risks based on overdue or unstarted work.
This example pairs Teamwork's list-milestones tool with the AI's synthesis capability to turn raw project data into a stakeholder-ready summary. The milestone list returns one page; if you have many milestones, you'll paginate. The AI infers progress and risk from task states, but can't access detailed task comments or time-tracking data unless you explicitly list tasks per milestone.
Use-case deep-dives
When Teamwork MCP handles multi-client task routing better than Slack threads
A 6-person agency runs 8 active client projects in Teamwork, each with its own task lists, milestones, and tags. During weekly planning, the team needs to reassign tasks across projects as priorities shift. The Teamwork MCP wins here because List Projects, List Task Lists, and List Tasks let an AI surface cross-project workload in one query, then Create Task and tag operations move work without opening eight browser tabs. The threshold: if your agency runs fewer than 4 concurrent projects, the MCP's setup overhead outweighs the routing benefit—just use Teamwork's UI. But at 5+ projects with frequent handoffs, the MCP turns planning from a 30-minute tab circus into a 5-minute conversation.
Why this MCP is overkill for daily standups but essential for sprint closes
A 4-person product team ships two-week sprints with 15-20 tasks per cycle. They don't need the Teamwork MCP for daily standups—Teamwork's native notifications handle that. The MCP becomes the right call at sprint close, when the PM needs to audit completion rates, reassign stragglers, and tag retrospective themes across multiple task lists. List Milestones filters by due-date range to pull the sprint boundary, List Tasks shows what's incomplete, and Create Tag marks retro topics without manual clicking. The trade-off: if your sprints are under 10 tasks or you close sprints in Teamwork's UI anyway, skip the MCP. At 15+ tasks with structured retros, the MCP saves 20 minutes per sprint and keeps the close audit in your AI workspace.
When List People and Create Task beat email chains for freelancer ramp-up
A startup brings on 2-3 contractors per quarter, each needing 8-12 onboarding tasks assigned across design, dev, and ops projects. The Teamwork MCP handles this scenario cleanly: List People confirms the contractor's Teamwork account exists, List Projects and List Task Lists identify where onboarding tasks live, then Create Task assigns the full checklist in one AI session. The alternative—emailing the contractor a task list, then manually creating tasks in Teamwork—takes 15 minutes and risks missed steps. The boundary: if you onboard fewer than 4 people per year, the MCP setup isn't worth it. At 6+ onboardings annually, the MCP turns a repetitive admin chore into a 3-minute AI handoff and ensures no onboarding task gets dropped.
Frequently asked
What does the Teamwork MCP let me do in Switchy?
The Teamwork MCP gives your AI agents read and write access to your Teamwork projects, tasks, milestones, and tags. Agents can create tasks with assignments and estimates, filter tasks by project or assignee, list milestones by due date, and manage tags across your workspace. It's designed for teams that already run projects in Teamwork and want AI to handle routine task creation and status lookups without switching tabs.
Do I need admin access to connect Teamwork to Switchy?
No, but you need a Teamwork API key tied to a user account with the permissions you want the MCP to use. If your agents need to create tasks in a project, the connected user must have write access to that project. The MCP inherits whatever visibility and permissions the API key owner has in Teamwork, so choose an account that can see the projects and people your team cares about.
Can the Teamwork MCP update existing tasks or only create new ones?
The current tool set focuses on creating tasks and reading data—listing tasks, projects, milestones, people, and tags. It does not include tools to update task fields, change assignees, or mark tasks complete. If your workflow needs task updates, you'll need to do those manually in Teamwork or wait for Switchy to expand the tool set.
Why use the Teamwork MCP instead of just opening Teamwork?
The MCP lets your AI agents pull task lists, check milestone dates, and create tasks inline while they're already working on something else in Switchy—like drafting a project plan or triaging support tickets. You skip the context switch to Teamwork's UI. It's faster for repetitive lookups and bulk task creation, but you'll still open Teamwork for complex project views or manual task edits.
Who on the team should connect the Teamwork integration?
Whoever connects it should have visibility into the projects and people your agents need to reference. A project manager or team lead is usually a good fit. Avoid connecting a restricted account—agents will only see what that user sees, so if the connected account can't access a project, neither can your AI workflows.