Deskpro MCP server

What the model can do

Deskpro (helpdesk): tickets by status, agent, requester, organisation, department, label, SLA and creation date, one ticket in full, a ticket's messages and internal notes, people, organisations, departments and agents; can create tickets, reply to the requester, add internal notes, change a ticket's status, agent, team, department, urgency, labels or hold, merge and delete tickets, add CCs, add notes to people and organisations, and create organisations.

Reads

• deskpro_list_ticketsDeskpro tickets: subject, status, urgency, agent, requester and organisation ids, department, labels, SLA and dates.
• deskpro_get_ticketOne Deskpro ticket by id or ref: subject, status, hold, urgency, agent, team, requester and organisation ids, department, labels, SLA…
• deskpro_list_ticket_messagesThe messages on a Deskpro ticket, oldest first: who wrote each (by name), when, whether it is an internal note, and the text without HTML…
• deskpro_list_peoplePeople in Deskpro (users and agents) by name, organisation and ticket count.
• deskpro_list_organizationsOrganisations in Deskpro: name, summary, importance, email domains, labels and ticket count.
• deskpro_list_departmentsDeskpro ticket departments: id, title, parent and whether tickets can be filed there.
• deskpro_list_agentsDeskpro agents by name and id, for assigning tickets.

Acts, when you ask

These change something in Deskpro. 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.

• deskpro_create_ticketCreates a Deskpro ticket for a requester (by email or person id) with a first message.
• deskpro_reply_to_ticketPosts a reply on a Deskpro ticket as the key's agent; it is emailed to the requester and anyone CC'd, and cannot be unsent.
• deskpro_add_ticket_noteAdds an internal note to a Deskpro ticket, visible to agents only; the requester is not emailed.
• deskpro_update_ticketChanges a Deskpro ticket's status, agent, team, department, urgency, labels, hold or subject…
• deskpro_merge_ticketsMerges merge_ticket into ticket in Deskpro, so the two become the one ticket that stays.
• deskpro_delete_ticketDeletes a Deskpro ticket, taking it out of every queue (Deskpro keeps deleted tickets under the hidden status).
• deskpro_add_ticket_ccAdds a person as a CC on a Deskpro ticket (by email or person id); they receive the ticket's replies from then on.
• deskpro_add_person_noteAdds an agent-only note to a person's profile in Deskpro.
• deskpro_add_organization_noteAdds an agent-only note to an organisation in Deskpro.
• deskpro_create_organizationCreates an organisation in Deskpro; nobody is emailed.

Connect it

First connect Deskpro on Dashboard → Connections, then add Memtro to your client once. The Deskpro 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 Deskpro 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 are awaiting an agent and breaching SLA?
• › What has the customer said on ticket ABCD-1234 so far?
• › How many open tickets does Northwind have?
• › Which tickets in the billing department are on hold?
• › Add an internal note to ticket ABCD-1234 that the refund is approved.

Questions

Is this an official Deskpro MCP server?

No. It is Memtro's MCP server with Memtro's Deskpro connector behind it: the connector reads Deskpro through its API with the credentials you connect on Dashboard → Connections, and Deskpro 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 Deskpro?

Only when you ask, and only what it has been granted: create a ticket (triggers may email the requester); reply to a ticket (emailed to the requester); add an internal note to a ticket; change a ticket's status, agent, team, department, urgency, labels or hold; merge one ticket into another (permanent); delete a ticket; add a CC to a ticket (they receive its replies); add a note to a person; add a note to an organisation; create an organisation. 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