Merge Unified's Teamwork.com integration Merge Agent Handler's Teamwork.com MCP server

Connect your AI Agents to Teamwork.com in minutes

Merge lets you securely connect your agents to Teamwork.com and thousands of tools instantly

Start building for free

Read docs

Teamwork.com

Learn more about Merge Agent Handler

Available tools

list_comments

List all comments on a specific resource (task, milestone, file, or notebook). Returns comments with their details including body content, author, and timestamps.

create_comment

Add a new comment to a resource (task, milestone, file, or notebook). Allows specifying the comment body and optionally notifying specific users.

update_comment

Update an existing comment's body content. The comment body is the only field that can be updated.

delete_comment

Permanently delete a comment from a resource. This action cannot be undone.

list_companies

List all companies (clients) in the Teamwork.com workspace with optional search filtering. Returns companies with their details including name, address, phone, website, and associated people/project counts.

get_company

Get detailed information about a specific company by its ID. Returns full company details including name, address, contact information, website, and associated people/project counts.

create_company

Create a new company (client) in the Teamwork.com workspace. Allows setting name, address, contact information, and website. Companies can be associated with projects and people.

update_company

Update an existing company's properties including name, phone, and website. Only provided fields will be updated.

delete_company

Permanently delete a company from the Teamwork.com workspace. This action cannot be undone. Associated projects will not be deleted but will lose their company association.

list_milestones

List milestones in the Teamwork.com workspace with optional filtering by project. Returns milestones with their details including name, description, deadline, status, and responsible parties.

get_milestone

Get detailed information about a specific milestone by its ID. Returns full milestone details including name, description, deadline, status, responsible parties, and associated task counts.

create_milestone

Create a new milestone within a project. Milestones represent key deadlines or deliverables. Allows setting name, deadline, description, and responsible parties.

update_milestone

Update an existing milestone's properties including name, deadline, and description. Only provided fields will be updated.

delete_milestone

Permanently delete a milestone from the Teamwork.com workspace. This action cannot be undone. Associated tasks will not be deleted but will lose their milestone association.

complete_milestone

Mark a milestone as complete. This will set the milestone status to completed and record the completion timestamp.

uncomplete_milestone

Reopen a completed milestone by marking it as incomplete. This will restore the milestone to active status.

list_people

List all people (users) in the Teamwork.com workspace with optional search filtering. Returns people with their details including name, email, title, phone numbers, and company association.

get_person

Get detailed information about a specific person by their ID. Returns full person details including name, email, title, phone numbers, company association, and user type information.

get_current_user

Get detailed information about the currently authenticated user. Useful for identifying the user associated with the API key being used.

list_projects

List all projects in the Teamwork.com workspace with filtering, pagination, and status support. Returns projects with their details including name, description, status, dates, and associated company information.

get_project

Get detailed information about a specific project by its ID. Returns full project details including name, description, status, dates, company association, tags, and other metadata.

create_project

Create a new project in the Teamwork.com workspace. Allows setting name, description, company association, category, start/end dates, and tags.

update_project

Update an existing project's properties including name, description, status, and dates. Only provided fields will be updated.

delete_project

Permanently delete a project from the Teamwork.com workspace. This action cannot be undone and will delete all associated tasks, task lists, and other project data.

list_tags

List all tags in the Teamwork.com workspace. Returns tags with their details including name and color. Tags can be used to categorize and filter projects, tasks, and other resources.

get_tag

Get detailed information about a specific tag by its ID. Returns full tag details including name, color, and associated project information.

create_tag

Create a new tag in the Teamwork.com workspace. Tags can be used to categorize projects, tasks, and other resources. Allows setting name and optional color.

update_tag

Update an existing tag's name or color. Only provided fields will be updated.

delete_tag

Permanently delete a tag from the Teamwork.com workspace. This action cannot be undone. Resources that had this tag will lose their tag association.

list_tasks

List tasks in the Teamwork.com workspace with extensive filtering options. Can filter by project, task list, assignees, and completion status. Returns tasks with their details including name, description, priority, dates, and assignees.

get_task

Get detailed information about a specific task by its ID. Returns full task details including name, description, priority, dates, assignees, progress, dependencies, and tags.

create_task

Create a new task within a task list. Allows setting name, description, priority, dates, assignees, time estimates, and tags. Tasks must be created within an existing task list.

update_task

Update an existing task's properties including name, description, priority, dates, assignees, and progress. Only provided fields will be updated.

delete_task

Permanently delete a task from the Teamwork.com workspace. This action cannot be undone and will also delete any subtasks.

complete_task

Mark a task as complete. This will set the task status to completed and record the completion timestamp.

uncomplete_task

Reopen a completed task by marking it as incomplete. This will restore the task to active status.

list_tasklists

List all task lists within a specific project. Returns task lists with their details including name, description, task counts, and position order.

get_tasklist

Get detailed information about a specific task list by its ID. Returns full task list details including name, description, task counts, and associated project information.

create_tasklist

Create a new task list within a project. Task lists help organize tasks into logical groups and can have descriptions.

update_tasklist

Update an existing task list's name or description. Only provided fields will be updated.

delete_tasklist

Permanently delete a task list from a project. This action cannot be undone and may also delete all tasks within the list.

list_time_entries

List time entries in the Teamwork.com workspace with filtering options. Can filter by project, task, user, and date range. Returns time entries with their details including hours, minutes, date, description, and billable status.

get_time_entry

Get detailed information about a specific time entry by its ID. Returns full time entry details including hours, minutes, date, description, billable status, and associated task/project information.

create_time_entry

Log time against a task. Create a new time entry with hours, minutes, date, optional description, and billable status. Time entries are used to track work hours for tasks and projects.

update_time_entry

Update an existing time entry's properties including hours, minutes, date, description, and billable status. Only provided fields will be updated.

delete_time_entry

Permanently delete a time entry from the Teamwork.com workspace. This action cannot be undone.

validate_credential

Validate Teamwork credentials. Verifies credentials during setup.

View all tools by creating a free account See more tools

How to set up Merge Agent Handler

In an mcp.json file, add the configuration below, and restart Cursor.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Copy Code

Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.

Make sure Claude is using the Node v20+.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote@latest",
8        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9        "--header",
10        "Authorization: Bearer ${AUTH_TOKEN}"
11      ],
12      "env": {
13        "AUTH_TOKEN": "yMt*****"
14      }
15    }
16  }
17}

Copy Code

Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.

Learn more in the official documentation ↗

1{
2    "mcpServers": {
3      "agent-handler": {
4        "command": "npx",
5        "args": [
6          "-y",
7          "mcp-remote@latest",
8          "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9          "--header",
10          "Authorization: Bearer ${AUTH_TOKEN}"
11        ],
12        "env": {
13          "AUTH_TOKEN": "<ah-production-access-key>"
14        }
15      }
16    }
17  }

Copy Code

In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".

You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.

Learn more in the official documentation ↗

1{
2  "inputs": [
3    {
4      "type": "promptString",
5      "id": "agent-handler-auth",
6      "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7      "password": true
8    }
9  ],
10  "servers": {
11    "agent-handler": {
12      "type": "stdio",
13      "command": "npx",
14      "args": [
15        "-y",
16        "mcp-remote@latest",
17        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18        "--header",
19        "Authorization: Bearer ${input:agent-handler-auth}"
20      ]
21    }
22  }
23}

Copy Code

FAQs on using Merge's Teamwork.com MCP server

What is a Teamwork.com MCP?

It's an MCP server that plugs your agents into Teamwork.com's project management platform via tools. Your agents can invoke these tools to create and update tasks, manage projects and milestones, log time entries, and more.

Teamwork.com offers an official MCP server, but you can also use one from a third-party platform, like Merge Agent Handler.

How can I use the Teamwork.com MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

CRM-to-project automation: When a deal is marked closed-won in HubSpot or Salesforce, an agent creates a new Teamwork.com project, assigns the delivery team, and sets up an initial milestone structure without anyone touching Teamwork.com manually

Time entry logging from Slack: A Slack-based agent listens for time logging commands in a designated channel, parses the task name and duration from the message, and creates a Teamwork.com time entry against the correct project and task

Overdue task escalation: Each morning, an agent lists tasks that are past their due date across all active projects, groups them by assignee, and posts a personalized overdue summary to each team member in Slack

End-of-sprint client delivery report: At the close of each sprint, an agent pulls completed tasks and logged time from Teamwork.com, formats a client-facing summary of work delivered, and emails it to the relevant project stakeholders

What are popular tools for Teamwork.com's MCP server?

Here are some of the most commonly used tools:

create_task: adds a new task to a specified task list with fields like name, assignee, due date, and priority. Use this when an agent needs to generate work items automatically based on a trigger in another system

update_task: modifies an existing task's fields, including status, assignee, due date, and description. Good for workflows that reassign tasks, extend deadlines, or move items to in-progress based on external events

list_tasks: returns tasks across a project or task list, filterable by assignee, status, or due date. Useful for agents that need to surface overdue items, build workload summaries, or check completion rates across a portfolio

create_project: creates a new project with name, description, company association, and start and end dates. Call this when an agent needs to spin up a project structure after a business event like a new client contract being signed

create_time_entry: logs a time entry against a specific task or project with duration, date, and description. Helpful when an agent is automating time tracking from an external source like a calendar, a Slack command, or a timer integration

create_milestone: adds a milestone to a project with a deadline and responsible person. Use this when an agent is initializing a project structure and needs to define key delivery checkpoints as part of the setup

What makes Merge Agent Handler's Teamwork.com MCP server better than alternative Teamwork.com MCP servers?

Teamwork.com has its own official MCP server, but there are specific reasons to route it through Merge Agent Handler instead:

Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Teamwork.com, this means you can prevent task details, client project data, and time entry records containing billing or resource information from being exposed even when the agent has broad access

Managed authentication and credentials: Merge stores and refreshes Teamwork.com credentials on your behalf. You never embed API keys or OAuth tokens in agent configuration or deal with re-authentication when tokens expire

Real-time observability and audit trail: Every tool call against Teamwork.com is logged with timestamp, tool name, inputs, and response data. Project managers and security teams can see exactly what an agent created or modified without any additional instrumentation

Tool Packs and controlled access: Tool Packs let you bundle specific Teamwork.com tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's Teamwork.com MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).

2. Create a new Tool Pack, then find and enable the Teamwork.com connector. Decide which tools fit your workflow: read tools like list_tasks and list_time_entries cover reporting and auditing needs, while write tools like create_task, create_project, and create_time_entry are needed if your agent should take action on project data.

3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.

4. From the Registered User detail page, authenticate Teamwork.com by completing the OAuth flow. Merge stores and manages the credentials going forward.

5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.

6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your Teamwork.com tools are now accessible through that endpoint.

‍