MCP server to connect to the Teamwork.com API
MCP server to connect to the Teamwork.com API. That is what the teamwork mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
An MCP server that connects to the Teamwork API, providing a simplified interface for interacting with Teamwork projects and tasks.
The server publishes 14 tools. What each one is for:
getProjects — Get all projects from TeamworkgetCurrentProject — Gets details about the current projectcreateProject — Create a new project in TeamworkgetTasks — Get all tasks from TeamworkgetTasksByProjectId — Get all tasks from a specific project in TeamworkgetTaskListsByProjectId — Get all task lists from a specific project in TeamworkgetTasksByTaskListId — Gets all tasks from a specific task list ID from TeamworkgetTaskById — Get a specific task by ID from TeamworkcreateTask — Create a new task in TeamworkcreateSubTask — Create a new subtask under a parent task in TeamworkupdateTask — Update an existing task in TeamworkdeleteTask — Delete a task from TeamworkThe server ships on npm as @vizioz/teamwork-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Configuration is passed through the environment: PROJECT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Teamwork MCP's toolset — getProjects, getCurrentProject, createProject and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Vizioz; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Teamwork MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| getProjects | Get all projects from Teamwork |
| getCurrentProject | Gets details about the current project |
| createProject | Create a new project in Teamwork |
| getTasks | Get all tasks from Teamwork |
| getTasksByProjectId | Get all tasks from a specific project in Teamwork |
| getTaskListsByProjectId | Get all task lists from a specific project in Teamwork |
| getTasksByTaskListId | Gets all tasks from a specific task list ID from Teamwork |
| getTaskById | Get a specific task by ID from Teamwork |
| createTask | Create a new task in Teamwork |
| createSubTask | Create a new subtask under a parent task in Teamwork |
| updateTask | Update an existing task in Teamwork |
| deleteTask | Delete a task from Teamwork |
| getTasksMetricsComplete | Get the total count of completed tasks in Teamwork |
| getTasksMetricsLate | Get the total count of late tasks in Teamwork |
{
"mcpServers": {
"teamwork": {
"command": "npx",
"args": ["-y", "@vizioz/teamwork-mcp"],
"env": {
"PROJECT_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PROJECT_ID | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.