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

twchat-get_conversation ~36

Get a single Teamwork Chat conversation by ID.

Input Output Examples

Name	Type	Req	Description
conversation_id	integer	yes	The ID of the conversation to retrieve.

No output schema declared.

No examples provided.

twchat-get_current_user ~35

Get the current authenticated Teamwork Chat user, including identity, counts (unread conversations/messages, mentions), and settings.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

twchat-get_or_create_dm ~73

Get the 1:1 direct-message conversation with a person, creating it if it does not exist yet. Returns the conversation (use its id with send_message). Use list_people to find user_id.

Input Output Examples

Name	Type	Req	Description
user_id	integer	yes	The ID of the person to get the direct-message conversation with.

No output schema declared.

No examples provided.

twchat-list_conversations ~134

List Teamwork Chat conversations the current user is a member of.

Input Output Examples

Name	Type	Req	Description
include_message_data	—	—	Include the latest message in each conversation.
page_limit	—	—	Number of conversations to return (max 10).
page_offset	—	—	The index position to start retrieving results from (not a page number).
search_term	—	—	A search term to filter conversations by title.
sort	—	—	Sort order for the returned conversations.
status	—	—	Filter by conversation status.
type	—	—	Filter by conversation type: "rooms" for group/channel conversations, "pair" for 1:1 direct messages.

No output schema declared.

No examples provided.

twchat-list_messages ~137

List messages within a Teamwork Chat conversation. Requires conversation_id.

Input Output Examples

Name	Type	Req	Description
after_message_id	—	—	Return messages newer than this message ID (cursor).
before_message_id	—	—	Return messages older than this message ID (cursor).
conversation_id	integer	yes	The ID of the conversation to read messages from.
created_after	—	—	Return messages created after this time.
created_before	—	—	Return messages created before this time.
page	—	—	Page number for pagination of results.
page_size	—	—	Number of messages per page (1-200).
search_term	—	—	A search term to filter messages by text content.

No output schema declared.

No examples provided.

twchat-list_people ~73

List people in the Teamwork Chat installation. Useful for resolving names to user IDs.

Input Output Examples

Name	Type	Req	Description
page_limit	—	—	Number of people to return.
page_offset	—	—	The index position to start retrieving results from (not a page number).
search_term	—	—	A search term to filter people by name or email.

No output schema declared.

No examples provided.

twchat-send_dm ~77

Send a direct message to a person, resolving (or creating) the 1:1 conversation automatically. Requires user_id and body. Use list_people to find user_id.

Input Output Examples

Name	Type	Req	Description
body	string	yes	The message text. Supports Markdown.
user_id	integer	yes	The ID of the person to send the direct message to.

No output schema declared.

No examples provided.

twchat-send_message ~57

Send a message to a Teamwork Chat conversation. Requires conversation_id and body.

Input Output Examples

Name	Type	Req	Description
body	string	yes	The message text. Supports Markdown.
conversation_id	integer	yes	The ID of the conversation to post the message to.

No output schema declared.

No examples provided.

twdesk-create_company ~107

Create Desk company.

Input Output Examples

Name	Type	Req	Description
description	—	yes	The description of the company.
details	—	yes	The details of the company.
domains	—	yes	The domains for the company.
industry	—	yes	The industry of the company.
kind	—	yes	The kind of the company.
name	string	yes	The name of the company.
note	—	yes	The note for the company.
permission	—	yes	The permission level of the company.
website	—	yes	The website of the company.

No output schema declared.

No examples provided.

twdesk-create_customer ~160

Create customer.

Input Output Examples

Name	Type	Req	Description
address	—	yes	The address of the customer.
email	—	yes	The email of the customer.
extraData	—	yes	The extra data of the customer.
facebookURL	—	yes	The Facebook URL of the customer.
firstName	—	yes	The first name of the customer.
jobTitle	—	yes	The job title of the customer.
lastName	—	yes	The last name of the customer.
linkedinURL	—	yes	The LinkedIn URL of the customer.
mobile	—	yes	The mobile number of the customer.
notes	—	yes	The notes of the customer.
organization	—	yes	The organization of the customer.
phone	—	yes	The phone number of the customer.
twitterHandle	—	yes	The Twitter handle of the customer.

No output schema declared.

No examples provided.

twdesk-create_file ~77

Upload file. Attach the returned ID to tickets or messages.

Input Output Examples

Name	Type	Req	Description
data	string	yes	The content of the file as a base64-encoded string.
disposition	—	yes	The disposition of the file.
mimeType	string	yes	The MIME type of the file.
name	string	yes	The name of the file.

No output schema declared.

No examples provided.

twdesk-create_helpdoc_article ~108

Create a new help doc article.

Input Output Examples

Name	Type	Req	Description
contents	—	yes	The body content of the article.
description	—	yes	A short description / summary of the article.
isPrivate	—	yes	Set to true to make the article private.
siteID	integer	yes	The ID of the help doc site to create the article in.
status	—	yes	Publication status of the article (e.g. "published", "draft").
title	string	yes	The title of the article.

No output schema declared.

No examples provided.

twdesk-create_priority ~36

Create ticket priority.

Input Output Examples

Name	Type	Req	Description
color	—	yes	The color of the priority.
name	string	yes	The name of the priority.

No output schema declared.

No examples provided.

twdesk-create_status ~48

Create ticket status.

Input Output Examples

Name	Type	Req	Description
color	—	yes	The color of the status.
displayOrder	—	yes	The display order of the status.
name	string	yes	The name of the status.

No output schema declared.

No examples provided.

twdesk-create_tag ~36

Create Desk tag.

Input Output Examples

Name	Type	Req	Description
color	—	yes	The color of the tag.
name	string	yes	The name of the tag.

No output schema declared.

No examples provided.

twdesk-create_ticket ~256

Create ticket.

Input Output Examples

Name	Type	Req	Description
agentId	—	yes	Agent the ticket is assigned to. Use twdesk-list_users to discover.
bcc	—	yes	Email addresses to BCC.
body	string	yes	The body of the ticket.
cc	—	yes	Email addresses to CC.
customerEmail	—	yes	Customer email; required when customerId is not given. Existing customers are matched, otherwise a new customer is created.
customerId	—	yes	Customer of the ticket. Use twdesk-list_customers to discover.
files	—	yes	File IDs to attach. Use twdesk-create_file to upload.
inboxId	integer	yes	Inbox of the ticket. Use twdesk-list_inboxes to discover.
notifyCustomer	—	yes	Set to true if the customer should be sent a copy of the ticket.
priorityId	—	yes	Priority of the ticket. Use twdesk-list_priorities to discover.
statusId	—	yes	Status of the ticket. Use twdesk-list_statuses to discover.
subject	string	yes	The subject of the ticket.
tags	—	yes	Tags to associate with the ticket. Use twdesk-list_tags to discover.
typeId	—	yes	Ticket type. Use twdesk-list_ticket_types to discover.

No output schema declared.

No examples provided.

twdesk-create_ticket_type ~58

Create ticket type.

Input Output Examples

Name	Type	Req	Description
displayOrder	—	yes	The display order of the type.
enabledForFutureInboxes	—	yes	Whether the type is enabled for future inboxes.
name	string	yes	The name of the ticket type.

No output schema declared.

No examples provided.

twdesk-get_company ~59

Get Desk company (customer organization).

Input Output Examples

Name	Type	Req	Description
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
id	integer	yes	The ID of the company to retrieve.

No output schema declared.

No examples provided.

twdesk-get_customer ~55

Get customer.

Input Output Examples

Name	Type	Req	Description
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
id	integer	yes	The ID of the customer to retrieve.

No output schema declared.

No examples provided.

twdesk-get_helpdoc_article ~64

Get a help doc article by ID.

Input Output Examples

Name	Type	Req	Description
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
id	integer	yes	The ID of the help doc article to retrieve.

No output schema declared.

No examples provided.

twdesk-get_inbox ~56

Get inbox.

Input Output Examples

Name	Type	Req	Description
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
id	integer	yes	The ID of the inbox to retrieve.

No output schema declared.

No examples provided.

twdesk-get_priority ~56

Get ticket priority.

Input Output Examples

Name	Type	Req	Description
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
id	integer	yes	The ID of the priority to retrieve.

No output schema declared.

No examples provided.

twdesk-get_status ~56

Get ticket status.

Input Output Examples

Name	Type	Req	Description
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
id	integer	yes	The ID of the status to retrieve.

No output schema declared.

No examples provided.

twdesk-get_tag ~56

Get Desk tag.

Input Output Examples

Name	Type	Req	Description
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
id	integer	yes	The ID of the tag to retrieve.

No output schema declared.

No examples provided.

twdesk-get_ticket ~55

Get ticket.

Input Output Examples

Name	Type	Req	Description
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
id	integer	yes	The ID of the ticket to retrieve.

No output schema declared.

No examples provided.

twdesk-get_ticket_type ~58

Get ticket type.

Input Output Examples

Name	Type	Req	Description
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
id	integer	yes	The ID of the ticket type to retrieve.

No output schema declared.

No examples provided.

twdesk-get_user ~56

Get support agent.

Input Output Examples

Name	Type	Req	Description
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
id	integer	yes	The ID of the user to retrieve.

No output schema declared.

No examples provided.

twdesk-list_companies ~145

List Desk companies. Filter by name, domains, or kind.

Input Output Examples

Name	Type	Req	Description
domains	—	yes	The domains of the company to filter by.
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
kind	—	yes	The kind of the company to filter by.
name	—	yes	The name of the company to filter by.
orderBy	—	yes	The field to order the results by.
orderDirection	—	yes	The direction to order the results by (asc, desc).
page	—	yes	Page number for pagination of results.
pageSize	—	yes	Number of results per page for pagination.

No output schema declared.

No examples provided.

twdesk-list_customers ~143

List customers. Filter by company or email.

Input Output Examples

Name	Type	Req	Description
companyIDs	—	yes	The IDs of the companies to filter by.
companyNames	—	yes	The names of the companies to filter by.
emails	—	yes	The emails of the customers to filter by.
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
orderBy	—	yes	The field to order the results by.
orderDirection	—	yes	The direction to order the results by (asc, desc).
page	—	yes	Page number for pagination of results.
pageSize	—	yes	Number of results per page for pagination.

No output schema declared.

No examples provided.

twdesk-list_inboxes ~129

List inboxes. Filter by name or email.

Input Output Examples

Name	Type	Req	Description
email	—	yes	The email of the inbox to filter by.
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
name	—	yes	The name of the inbox to filter by.
orderBy	—	yes	The field to order the results by.
orderDirection	—	yes	The direction to order the results by (asc, desc).
page	—	yes	Page number for pagination of results.
pageSize	—	yes	Number of results per page for pagination.

No output schema declared.

No examples provided.

twdesk-list_priorities ~129

List ticket priorities. Filter by name or color.

Input Output Examples

Name	Type	Req	Description
color	—	yes	The color of the priority to filter by.
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
name	—	yes	The name of the priority to filter by.
orderBy	—	yes	The field to order the results by.
orderDirection	—	yes	The direction to order the results by (asc, desc).
page	—	yes	Page number for pagination of results.
pageSize	—	yes	Number of results per page for pagination.

No output schema declared.

No examples provided.

twdesk-list_statuses ~145

List ticket statuses. Filter by name, color, or code.

Input Output Examples

Name	Type	Req	Description
code	—	yes	The code of the status to filter by.
color	—	yes	The color of the status to filter by.
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
name	—	yes	The name of the status to filter by.
orderBy	—	yes	The field to order the results by.
orderDirection	—	yes	The direction to order the results by (asc, desc).
page	—	yes	Page number for pagination of results.
pageSize	—	yes	Number of results per page for pagination.

No output schema declared.

No examples provided.

twdesk-list_tags ~146

List Desk tags. Filter by name, color, or inbox.

Input Output Examples

Name	Type	Req	Description
color	—	yes	The color of the tag to filter by.
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
inboxIDs	—	yes	The IDs of the inboxes to filter by.
name	—	yes	The name of the tag to filter by.
orderBy	—	yes	The field to order the results by.
orderDirection	—	yes	The direction to order the results by (asc, desc).
page	—	yes	Page number for pagination of results.
pageSize	—	yes	Number of results per page for pagination.

No output schema declared.

No examples provided.

twdesk-list_ticket_types ~134

List ticket types. Filter by name or inbox.

Input Output Examples

Name	Type	Req	Description
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
inboxIDs	—	yes	Filter by inbox. Use twdesk-list_inboxes to discover.
name	—	yes	The name of the type to filter by.
orderBy	—	yes	The field to order the results by.
orderDirection	—	yes	The direction to order the results by (asc, desc).
page	—	yes	Page number for pagination of results.
pageSize	—	yes	Number of results per page for pagination.

No output schema declared.

No examples provided.

twdesk-list_users ~181

List support agents. For customers, use twdesk-list_customers.

Input Output Examples

Name	Type	Req	Description
email	—	yes	The email addresses of the users to filter by.
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
firstName	—	yes	The first names of the users to filter by.
inboxIDs	—	yes	The IDs of the inboxes to filter by.
isPartTime	—	yes	Whether to include part-time users in the results.
lastName	—	yes	The last names of the users to filter by.
orderBy	—	yes	The field to order the results by.
orderDirection	—	yes	The direction to order the results by (asc, desc).
page	—	yes	Page number for pagination of results.
pageSize	—	yes	Number of results per page for pagination.

No output schema declared.

No examples provided.

twdesk-reply_ticket ~101

Reply to a ticket. Use threadType=note for internal agent notes.

Input Output Examples

Name	Type	Req	Description
bcc	—	yes	Email addresses to BCC.
body	string	yes	The body of the message.
cc	—	yes	Email addresses to CC.
threadType	—	yes	'message' is a customer-facing reply; 'note' is an internal agent note.
ticketID	integer	yes	The ID of the ticket that the message will be sent to.

No output schema declared.

No examples provided.

twdesk-search_helpdoc_articles ~107

Search help doc articles. Filter by search term, status, site, or category.

Input Output Examples

Name	Type	Req	Description
categoryID	—	yes	Filter by help doc category ID.
page	—	yes	Page number (1-based).
pageSize	—	yes	Number of results per page.
search	—	yes	Free-text search term matched against article title and content.
siteID	—	yes	Filter by help doc site ID.
status	—	yes	Filter by article status (e.g. "published", "draft").

No output schema declared.

No examples provided.

twdesk-search_tickets ~254

Search tickets. Filter by inbox, customer, company, tag, status, priority, or user.

Input Output Examples

Name	Type	Req	Description
companyIDs	—	yes	Filter by company. Use twdesk-list_companies to discover.
customerIDs	—	yes	Filter by customer. Use twdesk-list_customers to discover.
fields	—	yes	Sparse fieldset: field names to include (e.g. ["id","name"]). Omit to receive all fields.
inboxIDs	—	yes	Filter by inbox. Use twdesk-list_inboxes to discover.
orderBy	—	yes	The field to order the results by.
orderDirection	—	yes	The direction to order the results by (asc, desc).
page	—	yes	Page number for pagination of results.
pageSize	—	yes	Number of results per page for pagination.
priorityIDs	—	yes	Filter by priority. Use twdesk-list_priorities to discover.
search	—	yes	Search term matched against subject, body, and other ticket fields.
statusIDs	—	yes	Filter by status. Use twdesk-list_statuses to discover.
tagIDs	—	yes	Filter by tag. Use twdesk-list_tags to discover.
userIDs	—	yes	Filter by user. Use twdesk-list_users to discover.

No output schema declared.

No examples provided.

twdesk-update_company ~128

Update Desk company.

Input Output Examples

Name	Type	Req	Description
description	—	yes	The new description of the company.
details	—	yes	The new details of the company.
domains	—	yes	The new domains for the company.
id	integer	yes	The ID of the company to update.
industry	—	yes	The new industry of the company.
kind	—	yes	The new kind of the company.
name	—	yes	The new name of the company.
note	—	yes	The new note for the company.
permission	—	yes	The new permission level of the company.
website	—	yes	The new website of the company.

No output schema declared.

No examples provided.

twdesk-update_customer ~187

Update customer.

Input Output Examples

Name	Type	Req	Description
address	—	yes	The new address of the customer.
email	—	yes	The new email of the customer.
extraData	—	yes	The new extra data of the customer.
facebookURL	—	yes	The new Facebook URL of the customer.
firstName	—	yes	The new first name of the customer.
id	integer	yes	The ID of the customer to update.
jobTitle	—	yes	The new job title of the customer.
lastName	—	yes	The new last name of the customer.
linkedinURL	—	yes	The new LinkedIn URL of the customer.
mobile	—	yes	The new mobile number of the customer.
notes	—	yes	The new notes of the customer.
organization	—	yes	The new organization of the customer.
phone	—	yes	The new phone number of the customer.
twitterHandle	—	yes	The new Twitter handle of the customer.

No output schema declared.

No examples provided.

twdesk-update_helpdoc_article ~101

Update an existing help doc article.

Input Output Examples

Name	Type	Req	Description
contents	—	yes	The new body content of the article.
description	—	yes	A short description / summary of the article.
id	integer	yes	The ID of the help doc article to update.
isPrivate	—	yes	Set to true to make the article private.
status	—	yes	Publication status (e.g. "published", "draft").
title	—	yes	The new title of the article.

No output schema declared.

No examples provided.

twdesk-update_priority ~49

Update ticket priority.

Input Output Examples

Name	Type	Req	Description
color	—	yes	The color of the priority.
id	integer	yes	The ID of the priority to update.
name	—	yes	The new name of the priority.

No output schema declared.

No examples provided.

twdesk-update_status ~61

Update ticket status.

Input Output Examples

Name	Type	Req	Description
color	—	yes	The color of the status.
displayOrder	—	yes	The display order of the status.
id	integer	yes	The ID of the status to update.
name	—	yes	The new name of the status.

No output schema declared.

No examples provided.

twdesk-update_tag ~49

Update Desk tag.

Input Output Examples

Name	Type	Req	Description
color	—	yes	The color of the tag.
id	integer	yes	The ID of the tag to update.
name	—	yes	The new name of the tag.

No output schema declared.

No examples provided.

twdesk-update_ticket ~200

Update ticket.

Input Output Examples

Name	Type	Req	Description
agentId	—	yes	Agent the ticket is assigned to. Use twdesk-list_users to discover.
bcc	—	yes	Email addresses to BCC.
body	—	yes	The body of the ticket.
cc	—	yes	Email addresses to CC.
deleteTags	—	yes	Tags to remove from the ticket. Use twdesk-list_tags to discover.
id	integer	yes	The ID of the ticket to update.
inboxId	—	yes	Inbox of the ticket. Use twdesk-list_inboxes to discover.
priorityId	—	yes	Priority of the ticket. Use twdesk-list_priorities to discover.
statusId	—	yes	Status of the ticket. Use twdesk-list_statuses to discover.
subject	—	yes	The subject of the ticket.
tags	—	yes	Tags to associate with the ticket. Use twdesk-list_tags to discover.
typeId	—	yes	Ticket type. Use twdesk-list_ticket_types to discover.

No output schema declared.

No examples provided.

twdesk-update_ticket_type ~71

Update ticket type.

Input Output Examples

Name	Type	Req	Description
displayOrder	—	yes	The display order of the type.
enabledForFutureInboxes	—	yes	Whether the type is enabled for future inboxes.
id	integer	yes	The ID of the ticket type to update.
name	—	yes	The new name of the type.

No output schema declared.

No examples provided.

twprojects-add_project_member ~45

Add a user to a project.

Input Output Examples

Name	Type	Req	Description
project_id	integer	yes	The ID of the project to add the member to.
user_ids	—	—	Users to add.

No output schema declared.

No examples provided.

twprojects-clone_project ~329

Clone/copy an existing project or instantiate one from a template.

Input Output Examples

Name	Type	Req	Description
company_id	—	—	The ID of the company associated with the new cloned project. If not provided, the company of the original project will be used.
days_offset	—	—	DaysOffset is the number of days to shift all scheduled dates in the cloned project relative to the base date. When cloning from a template, it defines the project duration span. When copying an exis…
description	—	—	The description of the new cloned project. If not provided, the description of the original project will be used.
id	integer	yes	The ID of the project to clone.
name	—	—	The name of the new cloned project. If not provided, the name of the original project will be used with an incremental suffix (e.g., 'Project Name (1)').
new_from_template	—	—	Indicates whether the new project should be a regular one created from a template.
target_date	—	—	Desired start or end date for the cloned project (chosen by template_date_target). Only applies when new_from_template=true. Format: YYYYMMDD. Defaults to today.
template_date_target	—	—	Specifies whether target_date represents the project's start or end date. When 'end', the start date is calculated by subtracting the template project's duration from target_date. Only applicable whe…
to_template	—	—	Indicates whether the new project should be set as a template.

No output schema declared.

No examples provided.

twprojects-complete_task ~31

Mark task complete.

Input Output Examples

Name	Type	Req	Description
id	integer	yes	The ID of the task to mark as complete.

No output schema declared.

No examples provided.

twprojects-complete_timer ~45

Stop a timer permanently and convert it to a timelog. Use pause_timer to pause without converting.

Input Output Examples

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

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

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