com.teamwork/mcp

OCI · DOCKER.IO/TEAMWORK/MCP:V1.26.4 · 3 COMPONENTS · SCANNED AUG 3

The Teamwork.com official MCP server helps teams efficiently manage client projects with AI.

Available components

remote · mcp.ai.teamwork.com 75 remote · mcp.ai.teamwork.com 18 oci · docker.io/teamwork/mcp:v1.26.4 37

37 37 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security0

Malware scan not yet available for this package.Unverified
CVE data not yet available for this package.Unverified
Install-script risk not yet assessed.Unverified
Dependency-health data not yet available.Unverified

Provenance & Transparency32

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
License check failed: no license is declared. See how to fix → Fail
Actively maintained (last published 2 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability79

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 20972 tokens (~109/item across 191 items; 190 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

Tool Coverage96

93% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
100% of tool parameters carry a description.Pass
Structured output schemas are declared (32% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a current MCP spec version (2026-07-28).Pass
Supports UI / widget rendering.Pass

Unverified: 2 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · docker.io/teamwork/mcp:v1.26.4

Claude Codex opencode Hermes Other

# add to Claude Code

claude mcp add com-teamwork-mcp -- docker run --rm -i docker.io/teamwork/mcp:v1.26.4

# add to Codex CLI

codex mcp add com-teamwork-mcp -- docker run --rm -i docker.io/teamwork/mcp:v1.26.4

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-teamwork-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "docker.io/teamwork/mcp:v1.26.4"
      ],
      "enabled": true
    }
  }
}

# ~/.hermes/config.yaml

mcp_servers:
  com-teamwork-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "docker.io/teamwork/mcp:v1.26.4"]

// mcp.json

{
  "mcpServers": {
    "com-teamwork-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/teamwork/mcp:v1.26.4"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

1 Aug 26 +31
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 93 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 32 functional
- First check of Capabilities: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
31 Jul 26 6

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed oci/docker.io/teamwork/mcp:v1.26.4

Provenance none

Ecosystem: oci · Outcome: none

Reason: no_attestation

MCP tools — 190 exposed · ~20,953 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

twprojects-get_workflow ~28

Get workflow.

Input Output Examples

Name	Type	Req	Description
id	integer	yes	The ID of the workflow to get.

Name	Type	Req	Description
workflow	object	yes	—

No examples provided.

twprojects-get_workflow_stage ~48

Get workflow stage.

Input Output Examples

Name	Type	Req	Description
id	integer	yes	The ID of the workflow stage to get.
workflow_id	integer	yes	The ID of the workflow that owns the stage.

Name	Type	Req	Description
stage	object	yes	—

No examples provided.

twprojects-link_project_to_workflow ~63

Link a project to a workflow so its tasks track through workflow stages.

Input Output Examples

Name	Type	Req	Description
project_id	integer	yes	The ID of the project to link to the workflow.
workflow_id	integer	yes	The ID of the workflow to link the project to.

No output schema declared.

No examples provided.

twprojects-list_activities ~127

List recent activity events. Scope by project_id or omit for site-wide.

Input Output Examples

Name	Type	Req	Description
end_date	—	—	End of the activity window.
log_item_types	—	—	Filter activities by item types.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_id	—	—	The ID of the project to retrieve activities from. Omit to list activities across all projects.
start_date	—	—	Start of the activity window.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
activities	null\|array	—	—
meta	object	—	—

No examples provided.

twprojects-list_calendar_events ~168

List events from a calendar, including time-blocking events that link a calendar slot to a Teamwork project, task or timelog. Use twprojects-list_calendars to find the calendar ID; the calendar of type 'blocked_time' holds the account's time-blocking events.

Input Output Examples

Name	Type	Req	Description
calendar_id	integer	yes	The ID of the calendar to list events from.
cursor	—	—	Cursor for fetching the next page of results.
ended_before_date	—	—	Filter events that end before this date (format: YYYY-MM-DD).
limit	—	—	Maximum number of events to return.
started_after_date	—	—	Filter events that start after this date (format: YYYY-MM-DD).
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
events	null\|array	—	—
included	object	—	—
meta	object	—	—

No examples provided.

twprojects-list_calendars ~93

List calendars. Calendars hold events such as meetings, out-of-office periods and time-blocking entries; the calendar of type 'blocked_time' holds the account's time-blocking events.

Input Output Examples

Name	Type	Req	Description
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
calendars	null\|array	—	—
meta	object	—	—

No examples provided.

twprojects-list_comments ~244

List comments. Scope by one of task_id, milestone_id, notebook_id, link_id, or file_version_id; omit all for site-wide.

Input Output Examples

Name	Type	Req	Description
file_version_id	—	—	The ID of the file version to retrieve comments for. Each file can have multiple versions, and comments can be associated with specific versions.
link_id	—	—	The ID of the link to retrieve comments for. Provide this to scope comments to a link.
milestone_id	—	—	The ID of the milestone to retrieve comments for. Provide this to scope comments to a milestone.
notebook_id	—	—	The ID of the notebook to retrieve comments for. Provide this to scope comments to a notebook.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
search_term	—	—	A search term to filter comments by name.
task_id	—	—	The ID of the task to retrieve comments for. Provide this to scope comments to a task.
updated_after	—	—	Filter comments updated after. Defaults to the last 3 months.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
comments	null\|array	—	—
meta	object	—	—

No examples provided.

twprojects-list_companies ~124

List companies (aka clients).

Input Output Examples

Name	Type	Req	Description
match_all_tags	—	—	If true, match all tags; if false, match any.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
search_term	—	—	A search term to filter companies by name. Each word from the search term is used to match against the company name.
tag_ids	—	—	A list of tag IDs to filter companies by tags.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
companies	null\|array	—	—
included	object	—	—
meta	object	—	—

No examples provided.

twprojects-list_custom_field_values ~119

List the custom field values of a task, project or company.

Input Output Examples

Name	Type	Req	Description
custom_field_ids	—	—	Filter by custom field.
entity	string	yes	The type of entity to list custom field values for.
entity_id	integer	yes	The ID of the task, project or company to list custom field values for.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
customfieldValues	null\|array	—	—
meta	object	—	—

No examples provided.

twprojects-list_custom_fields ~195

List custom fields.

Input Output Examples

Name	Type	Req	Description
entities	—	—	Filter custom fields by entity type.
ids	—	—	Custom field IDs to retrieve.
include_site_level	—	—	Whether to also include installation-level custom fields when filtering by project.
only_project_level	—	—	Whether to return only project-level custom fields.
only_site_level	—	—	Whether to return only installation-level custom fields.
order_by	—	—	The field to sort the results by.
order_mode	—	—	The direction to sort the results in.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_ids	—	—	Filter custom fields by project.
search_term	—	—	A search term to filter custom fields by name.
show_deleted	—	—	Whether to include deleted custom fields in the results.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
customfields	null\|array	—	—
meta	object	—	—

No examples provided.

twprojects-list_custom_item_fields ~228

List fields on a custom item type. Each entry includes the twId you need when writing record values. Custom items are user-defined entity types — Contracts, Leads, Deals, or anything else a customer has set up on a project. Use these tools when the user refers to an entity that is NOT a built-in Teamwork concept (Task, Tasklist, Project, Milestone, Comment, Notebook, Company, Team, User, Tag). If you don't recognise an entity name in the user's request, assume it is a custom item and call twprojects-list_custom_items on the relevant project to confirm.

Input Output Examples

Name	Type	Req	Description
custom_item_id	integer	yes	Custom item type ID to list fields for.
ids	—	—	Restrict to these field IDs.
order_mode	—	—	The direction to order the results by (asc, desc).
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
search_term	—	—	A search term to filter custom item fields by display name.
show_deleted	—	—	Include deleted fields.

Name	Type	Req	Description
customItemFields	null\|array	—	—
meta	object	—	—

No examples provided.

twprojects-list_custom_item_records ~260

List records on a custom item type. Returns each record with field values keyed by display name. Use the section_ids filter to scope to a specific section. Custom items are user-defined entity types — Contracts, Leads, Deals, or anything else a customer has set up on a project. Use these tools when the user refers to an entity that is NOT a built-in Teamwork concept (Task, Tasklist, Project, Milestone, Comment, Notebook, Company, Team, User, Tag). If you don't recognise an entity name in the user's request, assume it is a custom item and call twprojects-list_custom_items on the relevant project to confirm.

Input Output Examples

Name	Type	Req	Description
custom_item_id	integer	yes	Custom item type ID to list records for.
ids	—	—	Restrict to these record IDs.
order_by	—	—	Field to sort by.
order_mode	—	—	The direction to order the results by (asc, desc).
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
search_term	—	—	A search term to filter custom item records by name.
section_ids	—	—	Restrict to records in these sections.
show_deleted	—	—	Include deleted records.

Name	Type	Req	Description
customItemRecords	null\|array	—	—
meta	object	—	—

No examples provided.

twprojects-list_custom_items ~254

List the custom item types defined on a project. Returns each type's id, display name and labels — call get_custom_item to see a type's fields and sections. Custom items are user-defined entity types — Contracts, Leads, Deals, or anything else a customer has set up on a project. Use these tools when the user refers to an entity that is NOT a built-in Teamwork concept (Task, Tasklist, Project, Milestone, Comment, Notebook, Company, Team, User, Tag). If you don't recognise an entity name in the user's request, assume it is a custom item and call twprojects-list_custom_items on the relevant project to confirm.

Input Output Examples

Name	Type	Req	Description
ids	—	—	Restrict to these custom item type IDs.
order_by	—	—	Field to sort by.
order_mode	—	—	The direction to order the results by (asc, desc).
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_id	integer	yes	Project ID to list custom item types for.
search_term	—	—	A search term to filter custom items by display name or labels.
show_deleted	—	—	Include deleted custom item types.

Name	Type	Req	Description
customItems	null\|array	—	—
included	object	—	—
meta	object	—	—

No examples provided.

twprojects-list_industries ~21

List supported company (aka client) industries.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
industries	null\|array	yes	—

No examples provided.

twprojects-list_jobroles ~113

List job roles.

Input Output Examples

Name	Type	Req	Description
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
search_term	—	—	A search term to filter job roles by name, or assigned users. The job role will be selected if each word of the term matches the name, or assigned user first or last name, not requiring that the word…
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
jobRoles	null\|array	—	—
meta	object	—	—

No examples provided.

twprojects-list_links ~169

List links.

Input Output Examples

Name	Type	Req	Description
match_all_tags	—	—	If true, match all tags; if false, match any.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_id	—	—	The ID of the project to filter links by.
search_term	—	—	A search term to filter links by title or description. Each word from the search term is used to match against the link title or description. The link will be selected if each word of the term matche…
tag_ids	—	—	A list of tag IDs to filter links by tags.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
links	null\|array	—	—

No examples provided.

twprojects-list_message_replies ~155

List replies under a message thread. Filter by message_ids or project_ids.

Input Output Examples

Name	Type	Req	Description
message_ids	—	—	Filter by message.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_ids	—	—	Filter by project.
search_term	—	—	A search term to filter message replies by body or title. Each word from the search term is used to match against the message reply body or title. The message reply will be selected if each word of t…
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
messageReplies	null\|array	—	—
meta	object	—	—

No examples provided.

twprojects-list_messages ~180

List project messages (top-level posts). Use twprojects-list_message_replies for thread replies.

Input Output Examples

Name	Type	Req	Description
match_all_tags	—	—	If true, match all tags; if false, match any.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_ids	—	—	Filter messages by project.
search_term	—	—	A search term to filter messages by body or title. Each word from the search term is used to match against the message body or title. The message will be selected if each word of the term matches the…
tag_ids	—	—	A list of tag IDs to filter messages by tags.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
messages	null\|array	—	—
meta	object	—	—

No examples provided.

twprojects-list_milestones ~189

List milestones. Scope by project_id or omit for site-wide.

Input Output Examples

Name	Type	Req	Description
match_all_tags	—	—	If true, match all tags; if false, match any.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_id	—	—	The ID of the project from which to retrieve milestones. Omit to list milestones across all projects.
search_term	—	—	A search term to filter milestones by name. Each word from the search term is used to match against the milestone name and description. The milestone will be selected if each word of the term matches…
tag_ids	—	—	A list of tag IDs to filter milestones by tags.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
meta	object	—	—
milestones	null\|array	—	—

No examples provided.

twprojects-list_notebooks ~163

List notebooks.

Input Output Examples

Name	Type	Req	Description
include_contents	—	—	If true, include notebook contents in the response.
match_all_tags	—	—	If true, match all tags; if false, match any.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_ids	—	—	Filter notebooks by project.
search_term	—	—	A search term to filter notebooks by name or description. The notebook will be selected if each word of the term matches the notebook name or description, not requiring that the word matches are in t…
tag_ids	—	—	A list of tag IDs to filter notebooks by tags.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
meta	object	—	—
notebooks	null\|array	—	—

No examples provided.

twprojects-list_project_budgets ~105

List project budgets (top-level project financial budgets). Filter by project_ids or status.

Input Output Examples

Name	Type	Req	Description
cursor	—	—	Cursor for fetching the next page of results.
limit	—	—	Maximum number of budgets to return.
page_size	—	—	Number of results per page for pagination.
project_ids	—	—	Filter budgets by project.
status	—	—	Filter budgets by status.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
budgets	null\|array	—	—
included	object	—	—
meta	object	—	—

No examples provided.

twprojects-list_project_categories ~73

List project categories.

Input Output Examples

Name	Type	Req	Description
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
search_term	—	—	A search term to filter project categories by name.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
meta	object	—	—
projectCategories	null\|array	—	—

No examples provided.

twprojects-list_project_templates ~104

List project templates.

Input Output Examples

Name	Type	Req	Description
match_all_tags	—	—	If true, match all tags; if false, match any.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_category_ids	—	—	Filter project templates by category.
search_term	—	—	A search term to filter project templates by name or description.
tag_ids	—	—	A list of tag IDs to filter project templates by tags.

Name	Type	Req	Description
included	object	—	—
meta	object	—	—
projects	null\|array	—	—

No examples provided.

twprojects-list_projects ~118

List projects.

Input Output Examples

Name	Type	Req	Description
match_all_tags	—	—	If true, match all tags; if false, match any.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_category_ids	—	—	Filter projects by category.
search_term	—	—	A search term to filter projects by name or description.
tag_ids	—	—	A list of tag IDs to filter projects by tags.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
included	object	—	—
meta	object	—	—
projects	null\|array	—	—

No examples provided.

twprojects-list_skills ~110

List skills.

Input Output Examples

Name	Type	Req	Description
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
search_term	—	—	A search term to filter skills by name, or assigned users. The skill will be selected if each word of the term matches the name, or assigned user first or last name, not requiring that the word match…
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
meta	object	—	—
skills	null\|array	—	—

No examples provided.

twprojects-list_tags ~105

List tags.

Input Output Examples

Name	Type	Req	Description
item_type	—	—	Filter tags by item type.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_ids	—	—	Filter by project.
search_term	—	—	A search term to filter tags by name. Each word from the search term is used to match against the tag name.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
meta	object	—	—
tags	null\|array	—	—

No examples provided.

twprojects-list_tasklist_budgets ~93

List tasklist budgets nested under a project budget. Requires project_budget_id.

Input Output Examples

Name	Type	Req	Description
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_budget_id	integer	yes	The ID of the project budget to list tasklist budgets for.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
included	object	—	—
meta	object	—	—
tasklistBudgets	null\|array	—	—

No examples provided.

twprojects-list_tasklists ~127

List tasklists. Scope by project_id or omit for site-wide.

Input Output Examples

Name	Type	Req	Description
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_id	—	—	The ID of the project from which to retrieve tasklists. Omit to list tasklists across all projects.
search_term	—	—	A search term to filter tasklists by name.
show_completed	—	—	If true, include completed tasklists; excluded by default.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
meta	object	—	—
tasklists	null\|array	—	—

No examples provided.

twprojects-list_tasks ~354

List tasks with structured filters (tasklist_id, project_id, or site-wide). For keyword search use search.

Input Output Examples

Name	Type	Req	Description
assignee_user_ids	—	—	Filter tasks by assignee.
completed_after	—	—	Filter tasks completed after.
completed_before	—	—	Filter tasks completed before.
created_after	—	—	Filter tasks created after.
created_before	—	—	Filter tasks created before.
created_by_user_ids	—	—	Filter tasks by creator.
due_after	—	—	Filter tasks due after.
due_before	—	—	Filter tasks due before.
match_all_tags	—	—	If true, match all tags; if false, match any.
only_unassigned	—	—	If true, only return tasks that have no assignee.
only_unplanned	—	—	If true, only return tasks that are unplanned, meaning they are missing an assignee, a due date, or estimated time.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_id	—	—	The ID of the project from which to retrieve tasks. Omit to list tasks across all projects.
search_term	—	—	A search term to filter tasks by name.
show_completed	—	—	If true, include completed tasks and tasks belonging to completed tasklists; both excluded by default.
tag_ids	—	—	A list of tag IDs to filter tasks by tags.
tasklist_id	—	—	The ID of the tasklist from which to retrieve tasks. Takes precedence over project_id.
updated_after	—	—	Filter tasks updated after.
updated_before	—	—	Filter tasks updated before.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
included	object	—	—
meta	object	—	—
tasks	null\|array	—	—

No examples provided.

twprojects-list_teams ~137

List teams. Scope by company_id or project_id, or omit for site-wide.

Input Output Examples

Name	Type	Req	Description
company_id	—	—	The ID of the company from which to retrieve teams. Omit to list teams across all companies.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_id	—	—	The ID of the project from which to retrieve teams. Omit to list teams across all projects.
search_term	—	—	A search term to filter teams by name or handle.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
teams	null\|array	—	—

No examples provided.

twprojects-list_timelogs ~249

List timelogs. Scope by project_id or task_id, or omit for site-wide.

Input Output Examples

Name	Type	Req	Description
assigned_company_ids	—	—	Filter timelogs by assigned company.
assigned_team_ids	—	—	Filter timelogs by assigned team.
assigned_user_ids	—	—	Filter timelogs by assigned user.
end_date	—	—	End of the timelog window.
match_all_tags	—	—	If true, match all tags; if false, match any.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_id	—	—	The ID of the project from which to retrieve timelogs. Omit to list timelogs across all projects.
start_date	—	—	Start of the timelog window.
tag_ids	—	—	A list of tag IDs to filter timelogs by tags.
task_id	—	—	The ID of the task from which to retrieve timelogs. Omit to list timelogs across all tasks.
ticketIds	—	—	Filter timelogs by associated desk ticket.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
meta	object	—	—
timelogs	null\|array	—	—

No examples provided.

twprojects-list_timers ~148

List timers.

Input Output Examples

Name	Type	Req	Description
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_id	—	—	The ID of the project to filter timers by. Only timers associated with this project will be returned.
running_timers_only	—	—	If true, only running timers are returned.
task_id	—	—	The ID of the task to filter timers by. Only timers associated with this task will be returned.
user_id	—	—	The ID of the user to filter timers by. Only timers associated with this user will be returned.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
meta	object	—	—
timers	null\|array	—	—

No examples provided.

twprojects-list_users ~173

List users. Scope by project_id or filter by type (account/collaborator/contact).

Input Output Examples

Name	Type	Req	Description
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
project_id	—	—	The ID of the project from which to retrieve users. Omit to list users across all projects.
search_term	—	—	A search term to filter users by first or last names, or e-mail. The user will be selected if each word of the term matches the first or last name, or e-mail, not requiring that the word matches are…
type	—	—	Type of user to filter by. The available options are account, collaborator or contact.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
meta	object	—	—
people	null\|array	—	—

No examples provided.

twprojects-list_workflow_stages ~77

List workflow stages.

Input Output Examples

Name	Type	Req	Description
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
verbose	—	—	If false, returns id + name only — useful when scanning many results.
workflow_id	integer	yes	The ID of the workflow whose stages to list.

Name	Type	Req	Description
meta	object	—	—
stages	null\|array	—	—

No examples provided.

twprojects-list_workflows ~71

List workflows.

Input Output Examples

Name	Type	Req	Description
page	—	—	Page number for pagination of results.
page_size	—	—	Number of results per page for pagination.
search_term	—	—	A search term to filter workflows by name.
verbose	—	—	If false, returns id + name only — useful when scanning many results.

Name	Type	Req	Description
meta	object	—	—
workflows	null\|array	—	—

No examples provided.

twprojects-move_task_to_workflow_stage ~75

Move a task to a workflow stage.

Input Output Examples

Name	Type	Req	Description
stage_id	integer	yes	The ID of the workflow stage to move the task to.
task_id	integer	yes	The ID of the task to move.
workflow_id	integer	yes	The ID of the workflow that contains the target stage.

No output schema declared.

No examples provided.

twprojects-pause_timer ~42

Pause a running timer; can be resumed later. Use complete_timer to stop permanently.

Input Output Examples

Name	Type	Req	Description
id	integer	yes	The ID of the timer to pause.

No output schema declared.

No examples provided.

twprojects-resume_timer ~33

Resume a paused timer back to running.

Input Output Examples

Name	Type	Req	Description
id	integer	yes	The ID of the timer to resume.

No output schema declared.

No examples provided.

twprojects-search ~130

Cross-entity keyword search across projects, tasks, files, messages, and more.

Input Output Examples

Name	Type	Req	Description
cursor	—	—	Cursor for pagination of results.
extended_search	—	—	Whether to perform an extended search, which includes items updated more than 5 years ago.
include_completed_items	—	—	Whether to include completed items in the search results.
limit	—	—	Number of results per page for pagination.
project_id	—	—	The ID of the project to limit the search to.
search_term	—	yes	A search term to to look for items.
updated_after	—	—	Only include items updated after this date.

Name	Type	Req	Description
included	object	yes	—
meta	object	yes	—
search	null\|array	yes	—

No examples provided.

twprojects-summarize_timelogs ~356

Deterministic, complete time-tracking totals for a date window, grouped by user or project. Returns every group in one call with exact minute sums and 2-decimal hours — no pagination for the caller, any model tier. Use this instead of twprojects-list_timelogs whenever the question is about totals, sums, or breakdowns (e.g. "how many hours did X log", "time per project this month", billable vs billed vs unbilled); use list_timelogs only when you need the individual timelog entries. Minutes are exact and authoritative; hours are minutes ÷ 60 rounded to 2 decimals. unbilledBillable = billable − billed. The sum of the group columns equals the totals block exactly (reconcile in minutes, not hours).

Input Output Examples

Name	Type	Req	Description
company_ids	—	—	Filter to timelogs on projects of these companies/clients.
end_date	string	yes	Inclusive end of the report window (YYYY-MM-DD).
group_by	string	—	Dimension to group totals by. Defaults to user.
include_archived_projects	—	—	Include time from archived projects. Defaults to false.
project_ids	—	—	Filter to timelogs on these projects.
start_date	string	yes	Inclusive start of the report window (YYYY-MM-DD).
task_ids	—	—	Filter to timelogs on these tasks.
tasklist_ids	—	—	Filter to timelogs on these task lists.
team_ids	—	—	Filter to timelogs logged by members of these teams.
timelog_tag_ids	—	—	Filter to timelogs carrying these tags.
user_ids	—	—	Filter to timelogs logged for these users.

Name	Type	Req	Description
groups	null\|array	yes	—
scope	object	yes	—
totals	object	yes	—

No examples provided.

twprojects-update_comment ~102

Update comment.

Input Output Examples

Name	Type	Req	Description
body	string	yes	The content of the comment. The content can be added as text or HTML.
content_type	—	—	The content type of the comment. It can be either 'TEXT' or 'HTML'.
id	integer	yes	The ID of the comment to update.
notify	—	—	Who to notify of the comment change.
notify_current_user	—	—	Whether the current user should be notified about the comment change.

No output schema declared.

No examples provided.

twprojects-update_company ~254

Update company (aka client).

Input Output Examples

Name	Type	Req	Description
address_one	—	—	The first line of the address of the company.
address_two	—	—	The second line of the address of the company.
city	—	—	The city of the company.
country_code	—	—	The country code of the company, e.g., 'US' for the United States.
email_one	—	—	The primary email address of the company.
email_three	—	—	The tertiary email address of the company.
email_two	—	—	The secondary email address of the company.
fax	—	—	The fax number of the company.
id	integer	yes	The ID of the company to update.
industry_id	—	—	The ID of the industry the company belongs to.
manager_id	—	—	The ID of the user who manages the company.
name	—	—	The name of the company.
phone	—	—	The phone number of the company.
profile	—	—	A profile description for the company.
state	—	—	The state of the company.
tag_ids	—	—	A list of tag IDs to associate with the company.
website	—	—	The website of the company.
zip	—	—	The ZIP or postal code of the company.

No output schema declared.

No examples provided.

twprojects-update_custom_field ~208

Update custom field.

Input Output Examples

Name	Type	Req	Description
currency_code	—	—	The ISO currency code for 'currency' or 'financial' type custom fields.
description	—	—	An optional description for the custom field.
formula	—	—	The formula expression for 'formula' type custom fields.
id	integer	yes	The ID of the custom field to update.
name	—	—	The display name of the custom field.
options	—	—	Type-specific options for the custom field. For 'dropdown' and 'multiselect' types, provide {"choices": [{"value": "...", "color": "#rrggbb"}, ...]}. For 'rating' type, provide {"icon": "star\|heart\|.…
required	—	—	Whether the custom field must have a value when set on an entity.
unit	—	—	The unit associated with the custom field, when applicable.

No output schema declared.

No examples provided.

twprojects-update_custom_field_value ~180

Update a custom field value on a task, project or company.

Input Output Examples

Name	Type	Req	Description
country_code	—	—	The country code for currency-type custom field values.
currency_code	—	—	The ISO currency code for currency-type custom field values.
custom_field_id	integer	yes	The ID of the custom field the value belongs to.
entity	string	yes	The type of entity the custom field value is attached to.
entity_id	integer	yes	The ID of the task, project or company the custom field value belongs to.
value	—	—	The value to assign, typed per the field: string (text), number (number), boolean (checkbox), choice value string (dropdown/status; array for multiselect), ISO-8601 string (date).
value_id	integer	yes	The ID of the custom field value entry to update.

No output schema declared.

No examples provided.

twprojects-update_custom_item ~183

Update a custom item type's display name, description, or labels. Custom items are user-defined entity types — Contracts, Leads, Deals, or anything else a customer has set up on a project. Use these tools when the user refers to an entity that is NOT a built-in Teamwork concept (Task, Tasklist, Project, Milestone, Comment, Notebook, Company, Team, User, Tag). If you don't recognise an entity name in the user's request, assume it is a custom item and call twprojects-list_custom_items on the relevant project to confirm.

Input Output Examples

Name	Type	Req	Description
description	—	—	New description for the custom item type.
display_name	—	—	New display name for the custom item type.
id	integer	yes	Custom item type ID to update.
label_plural	—	—	New plural label.
label_singular	—	—	New singular label.

No output schema declared.

No examples provided.

twprojects-update_custom_item_field ~186

Update a field on a custom item type. Custom items are user-defined entity types — Contracts, Leads, Deals, or anything else a customer has set up on a project. Use these tools when the user refers to an entity that is NOT a built-in Teamwork concept (Task, Tasklist, Project, Milestone, Comment, Notebook, Company, Team, User, Tag). If you don't recognise an entity name in the user's request, assume it is a custom item and call twprojects-list_custom_items on the relevant project to confirm.

Input Output Examples

Name	Type	Req	Description
custom_item_id	integer	yes	Custom item type ID the field belongs to.
definition	—	—	Replacement type-specific configuration as a JSON object.
display_name	—	—	New display name.
id	integer	yes	Field ID to update.
position_after_id	—	—	Move this field after the given field ID.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

31 Jul 3 Aug