com.teamwork/mcp

REMOTE · MCP.AI.TEAMWORK.COM · 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

+6 this week 75 75 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security78

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability77

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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

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.

remote · mcp.ai.teamwork.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http com-teamwork-mcp https://mcp.ai.teamwork.com/

# ~/.codex/config.toml

[mcp_servers.com-teamwork-mcp]
url = "https://mcp.ai.teamwork.com/"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-teamwork-mcp": {
      "type": "remote",
      "url": "https://mcp.ai.teamwork.com/",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-teamwork-mcp --url https://mcp.ai.teamwork.com/ --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-teamwork-mcp:
    url: "https://mcp.ai.teamwork.com/"

// mcp.json

{
  "mcpServers": {
    "com-teamwork-mcp": {
      "type": "http",
      "url": "https://mcp.ai.teamwork.com/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +3
- First check of Authorization: partial security
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 1.26.3 → 1.26.4 functional
- Server version: 1.26.2 → 1.26.3 functional
- Server version: 1.26.1 → 1.26.2 functional
29 Jul 26 +1
- The server no longer declares the “logging” capability functional
- Server version: 1.25.4 → 1.26.0 functional
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 69

First indexed and scored.

Show 4 earlier entries 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 · Probed https://mcp.ai.teamwork.com

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=*.eks.us.teamworkops.com	CN=Amazon RSA 2048 M04,O=Amazon,C=US	21 Jun 2026	4 Jan 2027	RSA 2048	SHA256-RSA	55ecd7796e6cd7996d2683854dc6516
SANs: .eks.us.teamworkops.com, .teamwork.com, .helpdocsite.com, .us.teamworkops.com, .helpdocs.com, .teamworkdesk.com, *.ai.teamwork.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA)	CN=Amazon Root CA 1,O=Amazon,C=US	23 Aug 2022	23 Aug 2030	RSA 2048	SHA256-RSA	773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA)	CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US	25 May 2015	31 Dec 2037	RSA 2048	SHA256-RSA	67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

DNSSEC insecure

Validation of mcp.ai.teamwork.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
teamwork.com.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result	Enforced and verified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.ai.teamwork.com/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://mcp.ai.teamwork.com/.well-known/oauth-protected-resource"

Protected resource metadata

Document	https://mcp.ai.teamwork.com/.well-known/oauth-protected-resource
Retrieved	Yes
Resource	https://mcp.ai.teamwork.com
Authorisation server	https://teamwork.com

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.ai.teamwork.com	Verified	200
http (plaintext)	http://mcp.ai.teamwork.com	Inconclusive	404

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-create_comment ~126

Create comment on a task, milestone, notebook, file, or link.

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'.
notify	—	—	Who to notify of the new comment.
notify_current_user	—	—	Whether the current user should be notified about the new comment.
object	object	yes	The object to create the comment for. It can be a tasks, milestones, files or notebooks.

No output schema declared.

No examples provided.

twprojects-create_company ~242

Create 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.
industry_id	—	—	The ID of the industry the company belongs to.
manager_id	—	—	The ID of the user who manages the company.
name	string	yes	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-create_custom_field ~273

Create 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.
entity	string	yes	The type of entity this custom field can be applied to. Use 'all' for installation-level custom fields that are available across the workspace.
formula	—	—	The formula expression for 'formula' type custom fields.
name	string	yes	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\|.…
project_id	—	—	The ID of the project to scope the custom field to. When omitted, the custom field is created at the installation level.
required	—	—	Whether the custom field must have a value when set on an entity.
type	string	yes	The data type of the custom field.
unit	—	—	The unit associated with the custom field, when applicable.

No output schema declared.

No examples provided.

twprojects-create_custom_field_value ~177

Set a custom field value on a task, project or company. The custom field must already exist and be applicable to the target entity.

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 is attached to.
value	—	yes	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).

No output schema declared.

No examples provided.

twprojects-create_custom_item ~238

Create a new custom item type (e.g. Contracts, Leads, Deals) on a project. 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	—	—	An optional human-readable description for the custom item type.
display_name	string	yes	The display name of the custom item type (e.g. "Contracts").
label_plural	—	—	Plural label for many records (e.g. "Contracts"). Defaults to the display name when omitted.
label_singular	—	—	Singular label for one record (e.g. "Contract"). Defaults to the display name when omitted.
project_id	integer	yes	Project ID that will own the new custom item type.

No output schema declared.

No examples provided.

twprojects-create_custom_item_field ~334

Add a field (column) to a custom item type. Field types include text, number, dropdown, multiselect, checkbox, url, user, date, time and datetime. 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 that will own the new field.
definition	—	—	Optional type-specific configuration as a JSON object. Examples: for number-decimal fields {"precision": "2", "unit": {"type": "currency"}}; for user fields {"limit": 1, "source": "workspace"}. See t…
display_name	string	yes	Human-readable name of the field (e.g. "Status").
options	—	—	Choices for dropdown/multiselect fields. Each option is {label: "Active", color: "#22c55e"}.
position_after_id	—	—	Place this field after the given field ID. Null appends to the end.
tw_type	—	—	Optional sub-classification for dropdown fields. Use "status" for a Status field.
type	string	yes	Field data type.

No output schema declared.

No examples provided.

twprojects-create_custom_item_record ~339

Create a record (row) on a custom item type. For example, add a Contract on the Contracts type. Pass field values by name; the tool resolves names to the API's internal IDs. 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 that will own the new record.
field_values	—	—	Field values to set on the record. Each entry is {field_name, value}. Field names are matched case-insensitively against the custom item type's fields. Values are coerced by field type: dropdown/mult…
name	string	yes	Display name of the record (e.g. "Acme Inc Contract").
position_after_id	—	—	Place the record after the given record ID. Null appends to the end.
section_id	—	—	Optional section ID to place the record in.

No output schema declared.

No examples provided.

twprojects-create_jobrole ~28

Create job role.

Input Output Examples

Name	Type	Req	Description
name	string	yes	The name of the job role.

No output schema declared.

No examples provided.

twprojects-create_link ~143

Create link.

Input Output Examples

Name	Type	Req	Description
code	string	yes	The URL of the link. This is the actual web address that the link points to.
description	—	—	The description of the link. Longer text that provides detailed information about the link.
notify	—	—	Who to notify of the new link.
notify_current_user	—	—	Whether the current user should be notified about the new link.
project_id	integer	yes	The ID of the project to create the link in.
tag_ids	—	—	A list of tag IDs to associate with the link.
title	—	—	The title of the link, which provides a brief summary of the purpose of the link.

No output schema declared.

No examples provided.

twprojects-create_message ~88

Create message in a project.

Input Output Examples

Name	Type	Req	Description
body	string	yes	The body of the message.
notify	—	—	Who to notify of the new message.
notify_current_user	—	—	Whether the current user should be notified about the new message.
project_id	integer	yes	The ID of the project to create the message in.
title	string	yes	The title of the message.

No output schema declared.

No examples provided.

twprojects-create_message_reply ~77

Create message reply.

Input Output Examples

Name	Type	Req	Description
body	string	yes	The body of the message reply.
message_id	integer	yes	The ID of the message to create the reply in.
notify	—	—	Who to notify of the new reply.
notify_current_user	—	—	Whether the current user should be notified about the new message reply.

No output schema declared.

No examples provided.

twprojects-create_milestone ~133

Create milestone in a project.

Input Output Examples

Name	Type	Req	Description
assignees	object	yes	Assignees for the milestone.
description	—	—	A description of the milestone.
due_date	string	yes	The due date of the milestone (format: YYYYMMDD). Used for related tasks without their own due date.
name	string	yes	The name of the milestone.
project_id	integer	yes	The ID of the project to create the milestone in.
tag_ids	—	—	A list of tag IDs to associate with the milestone.
tasklist_ids	—	—	Tasklists to associate with the milestone.

No output schema declared.

No examples provided.

twprojects-create_notebook ~97

Create notebook in a project.

Input Output Examples

Name	Type	Req	Description
contents	string	yes	The contents of the notebook.
description	—	—	A description of the notebook.
name	string	yes	The name of the notebook.
project_id	integer	yes	The ID of the project to create the notebook in.
tag_ids	—	—	A list of tag IDs to associate with the notebook.
type	string	yes	The type of the notebook.

No output schema declared.

No examples provided.

twprojects-create_project ~131

Create project.

Input Output Examples

Name	Type	Req	Description
category_id	—	—	The ID of the category to which the project belongs.
company_id	—	—	The ID of the company associated with the project.
description	—	—	The description of the project.
end_at	—	—	End date of the project (format: YYYYMMDD).
name	string	yes	The name of the project.
owned_id	—	—	The ID of the user who owns the project.
start_at	—	—	Start date of the project (format: YYYYMMDD).
tag_ids	—	—	A list of tag IDs to associate with the project.

No output schema declared.

No examples provided.

twprojects-create_project_category ~72

Create project category.

Input Output Examples

Name	Type	Req	Description
color	—	—	The color of the project category in hex format (e.g., #FF5733).
name	string	yes	The name of the project category.
parent_id	—	—	The ID of the parent project category, if any. This allows for nested categories.

No output schema declared.

No examples provided.

twprojects-create_project_template ~141

Create project template.

Input Output Examples

Name	Type	Req	Description
category_id	—	—	The ID of the category to which the project template belongs.
company_id	—	—	The ID of the company associated with the project template.
description	—	—	The description of the project template.
end_at	—	—	End date of the project template (format: YYYYMMDD).
name	string	yes	The name of the project template.
owned_id	—	—	The ID of the user who owns the project template.
start_at	—	—	Start date of the project template (format: YYYYMMDD).
tag_ids	—	—	A list of tag IDs to associate with the project template.

No output schema declared.

No examples provided.

twprojects-create_skill ~38

Create skill.

Input Output Examples

Name	Type	Req	Description
name	string	yes	The name of the skill.
user_ids	—	—	The user IDs associated with the skill.

No output schema declared.

No examples provided.

twprojects-create_tag ~58

Create tag.

Input Output Examples

Name	Type	Req	Description
name	string	yes	The name of the tag. It must have less than 50 characters.
project_id	—	—	The ID of the project to associate the tag with. This is for project-scoped tags.

No output schema declared.

No examples provided.

twprojects-create_task ~257

Create task in a tasklist.

Input Output Examples

Name	Type	Req	Description
assignees	—	—	Assignees for the task.
change_followers	—	—	Followers of any task changes.
comment_followers	—	—	Followers of any task comments.
complete_followers	—	—	Followers of any task completions.
description	—	—	The description of the task. Support for plain text and Markdown formatting.
due_date	—	—	The due date of the task. If omitted, falls back to the milestone due date when one is set.
estimated_minutes	—	—	The estimated time to complete the task in minutes.
name	string	yes	The name of the task.
parent_task_id	—	—	The ID of the parent task if creating a subtask.
predecessors	—	—	Task dependencies that must be completed before this task can start.
priority	—	—	The priority of the task.
progress	—	—	The progress of the task, as a percentage (0-100). Only whole numbers are allowed.
start_date	—	—	The start date of the task.
tag_ids	—	—	A list of tag IDs to associate with the task.
tasklist_id	integer	yes	Tasklist ID. Use twprojects-list_tasklists to find one.

No output schema declared.

No examples provided.

twprojects-create_tasklist ~78

Create tasklist in a project.

Input Output Examples

Name	Type	Req	Description
description	—	—	The description of the tasklist.
milestone_id	—	—	The ID of the milestone to associate with the tasklist.
name	string	yes	The name of the tasklist.
project_id	integer	yes	The ID of the project to create the tasklist in.

No output schema declared.

No examples provided.

twprojects-create_team ~146

Create team.

Input Output Examples

Name	Type	Req	Description
company_id	—	—	The ID of the company. This is used to create a team scoped for a specific company.
description	—	—	The description of the team.
handle	—	—	The handle of the team. It is a unique identifier for the team. It must not have spaces or special characters.
name	string	yes	The name of the team.
parent_team_id	—	—	The ID of the parent team. This is used to create a hierarchy of teams.
project_id	—	—	The ID of the project. This is used to create a team scoped for a specific project.
user_ids	—	—	Users to add to the team.

No output schema declared.

No examples provided.

twprojects-create_timelog ~228

Create timelog entry against a project or task.

Input Output Examples

Name	Type	Req	Description
billable	—	—	If true, the timelog is billable.
date	string	yes	The date of the timelog.
description	—	—	A description of the timelog.
hours	integer	yes	The number of hours spent on the timelog. Must be a positive integer.
is_utc	—	—	If true, the time is in UTC.
minutes	integer	yes	Minutes spent on the timelog. Must be a positive integer less than 60; otherwise increment hours instead.
project_id	—	—	Project the timelog is logged against. Provide exactly one of project_id or task_id.
tag_ids	—	—	A list of tag IDs to associate with the timelog.
task_id	—	—	Task the timelog is logged against. Provide exactly one of project_id or task_id.
time	string	yes	The time of the timelog in the format HH:MM:SS.
user_id	—	—	User the timelog is logged for. Defaults to the authenticated user.

No output schema declared.

No examples provided.

twprojects-create_timer ~125

Create and start a timer.

Input Output Examples

Name	Type	Req	Description
billable	—	—	If true, the timer is billable.
description	—	—	A description of the timer.
project_id	integer	yes	The ID of the project to associate the timer with.
running	—	—	If true, the timer will start running immediately.
seconds	—	—	The number of seconds to set the timer for.
stop_running_timers	—	—	If true, any other running timers will be stopped when this timer is created.
task_id	—	—	The ID of the task to associate the timer with.

No output schema declared.

No examples provided.

twprojects-create_user ~129

Create user.

Input Output Examples

Name	Type	Req	Description
admin	—	—	Indicates whether the user is an administrator.
company_id	—	—	The ID of the client/company to which the user belongs.
email	string	yes	The email address of the user.
first_name	string	yes	The first name of the user.
last_name	string	yes	The last name of the user.
title	—	—	The job title of the user, such as 'Project Manager' or 'Senior Software Developer'.
type	—	—	The type of user, such as 'account', 'collaborator', or 'contact'.

No output schema declared.

No examples provided.

twprojects-create_workflow ~26

Create workflow.

Input Output Examples

Name	Type	Req	Description
name	string	yes	The name of the workflow.

No output schema declared.

No examples provided.

twprojects-create_workflow_stage ~47

Create workflow stage.

Input Output Examples

Name	Type	Req	Description
name	string	yes	The name of the workflow stage.
workflow_id	integer	yes	The ID of the workflow to add the stage to.

No output schema declared.

No examples provided.

twprojects-get_comment ~27

Get comment.

Input Output Examples

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

Name	Type	Req	Description
comments	object	yes	—

No examples provided.

twprojects-get_company ~30

Get company (aka client).

Input Output Examples

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

Name	Type	Req	Description
company	object	yes	—
included	object	yes	—

No examples provided.

twprojects-get_custom_field ~30

Get custom field.

Input Output Examples

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

Name	Type	Req	Description
customfield	object	yes	—

No examples provided.

twprojects-get_custom_field_value ~85

Get a single custom field value from a task, project or company.

Input Output Examples

Name	Type	Req	Description
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_id	integer	yes	The ID of the custom field value entry to retrieve.

Name	Type	Req	Description
customfieldValue	object	yes	—

No examples provided.

twprojects-get_custom_item ~148

Get a custom item type with its fields and sections inline, so you can see its schema before creating or updating records. 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
id	integer	yes	Custom item type ID to retrieve.

Name	Type	Req	Description
customItem	object	yes	—
included	object	yes	—

No examples provided.

twprojects-get_custom_item_field ~148

Get a single 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.
id	integer	yes	Field ID.

Name	Type	Req	Description
customItemField	object	yes	—

No examples provided.

twprojects-get_custom_item_record ~161

Get a single record. Field values come back keyed by display name with dropdown values translated to their human-readable 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
custom_item_id	integer	yes	Custom item type ID the record belongs to.
id	integer	yes	Record ID.

Name	Type	Req	Description
customItemRecord	object	yes	—

No examples provided.

twprojects-get_jobrole ~30

Get job role.

Input Output Examples

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

Name	Type	Req	Description
jobRole	object	yes	—

No examples provided.

twprojects-get_link ~27

Get link.

Input Output Examples

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

Name	Type	Req	Description
link	object	yes	—

No examples provided.

twprojects-get_message ~27

Get message.

Input Output Examples

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

Name	Type	Req	Description
message	object	yes	—

No examples provided.

twprojects-get_message_reply ~30

Get message reply.

Input Output Examples

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

Name	Type	Req	Description
messageReply	object	yes	—

No examples provided.

twprojects-get_milestone ~29

Get milestone.

Input Output Examples

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

Name	Type	Req	Description
milestone	object	yes	—

No examples provided.

twprojects-get_notebook ~28

Get notebook.

Input Output Examples

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

Name	Type	Req	Description
notebook	object	yes	—

No examples provided.

twprojects-get_project ~27

Get project.

Input Output Examples

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

Name	Type	Req	Description
included	object	yes	—
project	object	yes	—

No examples provided.

twprojects-get_project_category ~30

Get project category.

Input Output Examples

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

Name	Type	Req	Description
projectCategory	object	yes	—

No examples provided.

twprojects-get_skill ~27

Get skill.

Input Output Examples

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

Name	Type	Req	Description
skill	object	yes	—

No examples provided.

twprojects-get_tag ~27

Get tag.

Input Output Examples

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

Name	Type	Req	Description
tag	object	yes	—

No examples provided.

twprojects-get_task ~27

Get task.

Input Output Examples

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

Name	Type	Req	Description
included	object	yes	—
task	object	yes	—

No examples provided.

twprojects-get_tasklist ~30

Get tasklist.

Input Output Examples

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

Name	Type	Req	Description
tasklist	object	yes	—

No examples provided.

twprojects-get_team ~27

Get team.

Input Output Examples

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

Name	Type	Req	Description
team	object	yes	—

No examples provided.

twprojects-get_timelog ~30

Get timelog.

Input Output Examples

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

Name	Type	Req	Description
timelog	object	yes	—

No examples provided.

twprojects-get_timer ~27

Get timer.

Input Output Examples

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

Name	Type	Req	Description
timer	object	yes	—

No examples provided.

twprojects-get_user ~27

Get user.

Input Output Examples

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

Name	Type	Req	Description
person	object	yes	—

No examples provided.

twprojects-get_user_me ~17

Get the currently authenticated user.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
person	object	yes	—

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

26 Jul 3 Aug

Day	Score
26 Jul	69
27 Jul	69
28 Jul	70
29 Jul	71
30 Jul	71
31 Jul	74
1 Aug	74
2 Aug	75
3 Aug	75