Productivity & Project Management · Teamwork + Claude
Teamwork MCP with Claude: Automate Projects, Tasks and Time Tracking
The short answer
Claude works with Teamwork through the Model Context Protocol, an open standard that lets Claude securely read and act in the tool with permissions you control. Once connected, Claude can create tasks, update projects, track time and summarise team workload from a simple written request, with people approving important changes.
What is Teamwork?
Teamwork is a project management platform used to plan projects, coordinate tasks, collaborate with teams and track time. Project managers, agency leaders, consultants and operations teams use it to keep client work, deadlines, workload and billable hours organised in one place. It suits teams that deliver work for clients and need clear visibility of who is doing what and how long it takes.
How Claude connects to Teamwork through MCP
The Model Context Protocol, or MCP, is an open standard that acts like a universal adapter between Claude and other software. It lets Claude use a tool such as Teamwork to read information and take actions, while the organisation decides exactly what Claude is allowed to see and change.
Once Claude is connected to Teamwork, it can typically look up projects and tasks, create new tasks, update deadlines or assignees, log time against work and summarise how hours are spread across a team. Staff can simply ask in everyday language, for example asking for the overdue tasks on a client project.
Access is limited by design. Connections use the sign-in method Teamwork supports, here an API key, and are set up with least-privilege permissions. Consequential actions such as bulk changes or updates to client projects can require a person's approval before they happen, and activity can be logged for review.
What you can automate
Creating tasks from client requests
An account manager describes a new request in plain language, such as a set of revisions for a client website. Claude can draft the task list, assign owners and set due dates in Teamwork, so the account manager reviews the structure rather than typing every item by hand. This saves time at the start of each piece of client work.
Weekly workload summaries
A department head can ask for a summary of who is carrying the heaviest load this week. Claude can review open tasks and due dates across projects and produce a clear overview of workload by person. This helps leaders rebalance work before deadlines slip and avoids overloading individual team members.
Time tracking and billable hours
Consultants often forget to log hours until the end of the month. Claude can help staff record time against the right task and project using a short request, and can summarise billable hours by client. Finance teams then receive cleaner figures for invoicing with fewer chasing emails.
Project status updates
Before a client call, a project lead can ask for a status view across active tasks, milestones and blockers. Claude can gather this from Teamwork and present it as a short briefing. The lead can then update the project's progress notes or due dates with a single approved change.
Overdue task follow-up
Operations teams can ask Claude to list overdue tasks by owner and project. Claude can prepare a reminder list or proposed new dates for managers to approve. This keeps deadlines visible and reduces the time spent manually scanning boards each morning.
An end-to-end workflow: Client request to billable project plan
TriggerA new client request is received by e-mail or in the shared operations inbox.
Claude reads the request and summarises the scope, deliverables and requested dates.
Claude proposes a project in Teamwork with tasks, owners and due dates based on the team's usual structure.
The project manager reviews and approves the proposed plan before it is created.
Claude creates the approved project and tasks in Teamwork and sets the billable client against the project.
As staff work, Claude logs time entries from their updates and prepares a weekly hours summary.
The summary is shared with finance, which uses it to prepare the client's invoice from the Microsoft 365 workspace.
OutcomeProjects start faster with consistent structure, managers approve each plan, and billable hours reach finance accurately and on time. Results vary by team and typically improve as the workflow is refined.
How we set it up
Free automation audit
We review how your team uses Teamwork today and identify the workflows, such as task creation, time tracking and workload reporting, that are worth automating. You receive a clear recommendation at no cost.
Secure connection
We connect Claude to your Teamwork account using an API key, created and held under your control. Access is set to least privilege, so Claude can only do what your workflows need.
Workflow design
We design the end-to-end process across Teamwork and your other systems, such as Microsoft 365, CRM or finance tools. We define which actions run automatically and which need a person's approval.
Testing with real cases
We test the workflow against past projects and real requests from your team. We check accuracy, adjust prompts and rules, and confirm that approvals and audit logs work as intended.
Launch and training
We launch with monitoring in place and train your project managers, account teams and staff on how to make requests. We review usage after launch and refine the workflow as needed.
Who benefits
- Project managers
- Spend less time setting up tasks and updating statuses, and more time guiding delivery and client communication.
- Agency and consultancy leaders
- Gain a clearer view of team workload and billable hours across client accounts.
- Finance and billing teams
- Receive timely, cleaner time records to support accurate client invoicing.
- Operations and PMO teams
- Keep deadlines and overdue work visible without manual board checks each day.
Security and control
- Connections use an API key with least-privilege permissions, limited to the actions each workflow needs.
- People approve consequential actions such as bulk changes, client-facing updates or deadline shifts.
- Activity is logged so changes can be reviewed and traced.
- Only the data needed for each request is used, and access can be revoked at any time by the organisation.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can have Teamwork workflows designed to fit their own data handling and internal policies. Businesses in India are supported in line with the Digital Personal Data Protection Act, 2023, and organisations in the UAE and Saudi Arabia are supported in line with local data protection laws. Custom Claude applications can be hosted in India, the United States, the United Kingdom or the European Union, and the hosting region is chosen to meet your specific requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Teamwork MCP server do?
The Teamwork MCP server acts as a secure bridge between Teamwork and AI tools such as Claude. It allows an approved AI assistant to create tasks, update projects, track time and summarise workload using natural language. The server only exposes the actions the organisation has permitted, so it extends what your team can do without giving open access to the account.
Is connecting Claude to Teamwork secure?
Security depends on how the connection is set up. Connections typically use the API key that Teamwork supports, with least-privilege permissions, so Claude only sees and changes what is needed. Consequential actions can require human approval, and activity can be logged for review. We design these controls with you before launch.
What can Claude do with Teamwork once connected?
Typically, Claude can look up projects and tasks, create new tasks, update due dates or owners, log time entries and produce summaries of team workload and billable hours. The exact actions available depend on the permissions you grant during setup.
How long does setup take?
Timelines vary with the number of workflows and systems involved. A focused connection with a few clearly defined workflows is often set up in a matter of weeks, including testing and team training. A broader rollout across several systems typically takes longer. The free automation audit gives you a realistic estimate.
What Teamwork account access is needed?
Access depends on the sign-in method and the permissions your workflows require. Generally, an API key tied to an account with the right level of access is used, and we recommend a dedicated account with only the permissions the workflow needs. We confirm the exact requirements during the audit.