addPeopleToProject
Add people to a specific project in Teamwork
LABSCO SUMMARY
It covers more than tasks — the time entries and the utilization reports are what make it worth wiring into a working day.
Two things to set before real use. Put a .teamwork file with PROJECT_ID in the repository so questions about 'this project' resolve without a lookup. And fence the tool list with --allow or --deny: delete tools for tasks, people and companies all sit in the default surface, and most sessions need none of them.
What it is
An MCP server over the Teamwork API, authenticated with your own account credentials, covering the project and task surface as well as the people, time and reporting side.
What you get
- Projects: list with filters and paging, create one, and resolve the project this repository belongs to from a .teamwork file
- Tasks all the way down: filtered lists, by project, by task list or by ID; create, create a subtask, update and delete; plus subtasks and comments for a given task
- Comments on tasks, milestones, notebooks, links and file versions, with private and notify flags
- People: list and filter, one by ID, who is on a project, adding people to a project, and updating or deleting a person
- Companies: list with filters and stats, one by ID, create, update and delete
- Time: every logged entry filtered by task, project, budget, invoice, tasklist or allocation, and the entries against a single allocation
- Reporting: user utilization data with billable breakdowns, task completion per user, top performers over a period, and a utilization report exported as CSV, HTML, PDF or XLSX
- Counts of completed and late tasks, and the timezone list you need before updating someone's timezone
Requirements
A Teamwork account with API access, and Node.js v14.17 or higher (18 or the latest LTS recommended). Credentials arrive either as TEAMWORK_DOMAIN, TEAMWORK_USERNAME and TEAMWORK_PASSWORD, or as --domain, --user and --pass on the command line. Run it with npx @vizioz/teamwork-mcp. --allow-tools and --deny-tools narrow the surface by individual name or by group, so --deny=deleteTask,updateTask leaves a read-mostly server. Logging writes error.log and combined.log into a logs directory unless you pass --disable-logging or set DISABLE_LOGGING=true. A .teamwork file in the project root holding PROJECT_ID lets getCurrentProject resolve the project without extra lookups.
Setup effort
One command plus credentials — npx @vizioz/teamwork-mcp, then supply credentials
USE CASES
01
Seeing what is on your plate in this project
Resolve the project from the repository, then pull its open tasks.
02
Filing a task in the right list
List the task lists on the project, then create the task inside the right one.
03
Breaking a big task into pieces
Open the parent task, add subtasks under it, then read the set back.
04
Catching up on the discussion around a task
Read its comments newest first, then add your own with the right visibility.
05
Working out where the time actually went
Pull logged entries filtered by project or task, and the entries against a specific allocation.
06
Reporting utilization for a period
Read the utilization data for the people involved, then export the formatted report.
36 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
createComment
Creates a new comment for a specific resource (tasks, milestones, notebooks, links, fileversions) in Teamwork
createCompany
Create a new company. This tool allows you to create a company. The request requires a companyRequest object with various properties like addressOne, emailOne, name, and tags.
createProject
Create a new project in Teamwork
createSubTask
Creates a subtask. Create a new subtask under the provided parent task.
createTask
Creates a task. Create a new task in the provided task list.
deleteCompany
This tool allows you to delete a company, be careful with this tool as it will delete the company and all associated data. It requires the following parameters: companyId.
deletePerson
Delete a person from Teamwork
deleteTask
Delete a task from Teamwork
getCompanies
Get a list of companies, retrieve all companies for the provided filters. This endpoint allows you to filter companies by various parameters including custom fields, tags, search terms, and more.
getCompanyById
Get a specific company by ID. Retrieves detailed information about a company identified by its ID.
getCurrentProject
Get the current solution's Teamwork project, always check the .teamwork file in the root of the solution for the Teamwork project ID or ask the user which project they are working on.
getPeople
Get all people from Teamwork
getPersonById
Get a specific person by ID from Teamwork
getProjectPeople
Get all people assigned to a specific project from Teamwork
getProjectPerson
Returns one or more people on a project. Retrieve a person(s) record.
getProjects
Get all projects from Teamwork
getProjectsAllocationsTime
Get time entries for a specific allocation. Return logged time entries for a specific allocation. Only the time entries that the logged-in user can access will be returned.
getProjectsPeopleMetricsPerformance
Performance of users completing the most tasks. Count the number of completed tasks by user for the provided period. By default the user with the most completed tasks is shown first.
getProjectsPeopleUtilization
Return the user utilization data. This endpoint provides detailed information about user utilization, including billable and non-billable time, availability, and various utilization metrics.
getProjectsReportingUserTaskCompletion
Returns task completions for a given user. Retrieve a person record and its task completion stats.
getProjectsReportingUtilization
Generate utilization report in various formats (CSV, HTML, PDF, XLSX). Generates a utilization report containing all people for the provided filters. Only the people that the logged-in user can access will be returned.
getTaskById
Get a specific task by ID from Teamwork
getTaskComments
Get comments for a specific task from Teamwork
getTaskListsByProjectId
Get all task lists by project ID
getTasks
Get tasks, Return multiple tasks according to the optional provided filter.
getTasksByProjectId
Get all tasks from a specific project in Teamwork
getTasksByTaskListId
Get all tasks from a specific task list in Teamwork
getTasksMetricsComplete
Get the total count of completed tasks in Teamwork
getTasksMetricsLate
Get the total count of late tasks in Teamwork
getTaskSubtasks
Get all subtasks for a specific task in Teamwork
getTime
Get all time entries. Return all logged time entries for all projects. Only the time entries that the logged-in user can access will be returned.
getTimezones
Get all timezones available in Teamwork. This is useful when you need to update a user's timezone and need to know the available options.
updateCompany
This tool allows you to update a company. It requires parameters: companyId and companyRequest.
updatePerson
Update a person in Teamwork. This endpoint allows you to modify user information like timezone, name, email, etc.
updateTask
Update an existing task. Modify the properties of an existing task.
BEFORE YOU INSTALL
What to know first
Tools you get
36 tools when we connected. --allow-tools and --deny-tools filter the set by tool or by group (Projects, Tasks, People, Reporting, Time, Comments). The five Company tools belong to no group, so a group-only allow list drops them.
Requires
- npx on PATH
- Node.js
- A Teamwork domain, username and password (passed as --domain, --user and --pass, or as TEAMWORK_DOMAIN, TEAMWORK_USERNAME and TEAMWORK_PASSWORD)
Where it runs
All 3 documented setups run the server on your machine.
CONTEXT COST
Heavy Standing cost
Rated by the size of the 36 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @vizioz/teamwork-mcpMCP Clients
Cursor — 0.47 and later
CURSOR — 0.47 AND LATER · JSON
{
"mcpServers": {
"Teamwork": {
"command": "npx",
"args": [
"-y",
"@vizioz/teamwork-mcp",
"--domain",
"<YOUR_DOMAIN>",
"--user",
"<YOUR_USER>",
"--pass",
"<YOUR_PASSWORD>"
]
}
}
}The --domain, --user and --pass values in the blocks are your Teamwork domain, sign-in email and password. Setting TEAMWORK_DOMAIN, TEAMWORK_USERNAME and TEAMWORK_PASSWORD in your environment or a .env file is the project's alternative to the arguments, not an extra step.
Cursor — tool filtering
CURSOR — TOOL FILTERING · JSON
{
"mcpServers": {
"Teamwork": {
"command": "npx",
"args": [
"-y",
"@vizioz/teamwork-mcp",
"--domain",
"<YOUR_DOMAIN>",
"--user",
"<YOUR_USER>",
"--pass",
"<YOUR_PASSWORD>",
"--allow",
"Tasks,Projects",
"--deny",
"getProjectsPeopleMetricsPerformance,getProjectsPeopleUtilization"
]
}
}
}The --domain, --user and --pass values in the blocks are your Teamwork domain, sign-in email and password. Setting TEAMWORK_DOMAIN, TEAMWORK_USERNAME and TEAMWORK_PASSWORD in your environment or a .env file is the project's alternative to the arguments, not an extra step.
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"teamwork": {
"command": "npx",
"args": [
"-y",
"@vizioz/teamwork-mcp",
"--domain",
"<YOUR_DOMAIN>",
"--user",
"<YOUR_USER>",
"--pass",
"<YOUR_PASSWORD>"
]
}
}
}The --domain, --user and --pass values in the blocks are your Teamwork domain, sign-in email and password. Setting TEAMWORK_DOMAIN, TEAMWORK_USERNAME and TEAMWORK_PASSWORD in your environment or a .env file is the project's alternative to the arguments, not an extra step.
