Teamwork Desk MCP server

What the model can do

Teamwork Desk help desk: tickets with their subject, status, priority, inbox, assigned agent, customer, tags, response and resolution times; customers by name or company; inboxes, agents, statuses, priorities, ticket types and tags. Customers and agents are named with their e-mail; a ticket's messages are read, cut short. Phone numbers, addresses and notes are not read. Can open a ticket without notifying the customer, reply to the customer, change a ticket's status, priority, agent or inbox, add a customer, log time on a ticket and delete a ticket, each only when asked.

Reads

• teamworkdesk_ticketsTeamwork Desk tickets: subject, status, priority, inbox, assigned agent and customer (name and e-mail), tags, message count…
• teamworkdesk_ticketOne Teamwork Desk ticket by id: subject, status, priority, inbox, agent and customer (name and e-mail), tags, message count and times.
• teamworkdesk_ticket_messagesThe messages on one Teamwork Desk ticket, oldest first: who wrote each (agent or customer, by name), when, its thread type…
• teamworkdesk_customersSearch Teamwork Desk customers by name, e-mail or company: id, name, e-mail, organisation, job title, standing and ticket count.
• teamworkdesk_inboxesTeamwork Desk inboxes: id and name, for filtering tickets and opening one.
• teamworkdesk_agentsTeamwork Desk users (agents): id, name, e-mail, role and state, for assigning tickets.
• teamworkdesk_ticket_settingsTeamwork Desk's ticket statuses, priorities, types and tags, with their ids, for filtering and changing tickets.

Acts, when you ask

These change something in Teamwork Desk. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• teamworkdesk_create_ticketOpen a Teamwork Desk ticket in an inbox for a customer (an existing customer_id, or an e-mail, which adds the customer)…
• teamworkdesk_replyReply to a Teamwork Desk ticket as the key's user.
• teamworkdesk_update_ticketChange a Teamwork Desk ticket's status, priority, assigned agent or inbox (ids from teamworkdesk_ticket_settings…
• teamworkdesk_create_customerAdd a customer to Teamwork Desk with an e-mail and optionally a name.
• teamworkdesk_log_timeLog time against a Teamwork Desk ticket as the key's own user, with a description and whether it is billable.
• teamworkdesk_delete_ticketDelete a Teamwork Desk ticket.

Connect it

First connect Teamwork Desk on Dashboard → Connections, then add Memtro to your client once. The Teamwork Desk tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Teamwork Desk connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which tickets have breached their SLA this week?
• › What has BigCo raised with support this month?
• › Which urgent tickets are unassigned?
• › What did the customer say in the last message on ticket 2210?
• › Assign ticket 2210 to Sarah and set it to high priority

Questions

Is this an official Teamwork Desk MCP server?

No. It is Memtro's MCP server with Memtro's Teamwork Desk connector behind it: the connector reads Teamwork Desk through its API with the credentials you connect on Dashboard → Connections, and Teamwork Desk publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Teamwork Desk?

Only when you ask, and only what it has been granted: open a ticket for a customer, without notifying them; reply to a ticket's customer (sent to them by e-mail); change a ticket's status, priority, assigned agent or inbox; add a customer, without a welcome e-mail; log time against a ticket as the key's user; delete a ticket. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Support

• Help Scout MCP server
• Zendesk MCP server
• Intercom MCP server
• Freshdesk MCP server
• Front MCP server
• Zoho Desk MCP server