NewCost control: a token allowance a month for each model choice — when one runs out, the cheaper one answers.See how it works
memtro
Start for free
MCP server · Support

Zendesk MCP server

Zendesk in any MCP client, through Memtro: Zendesk does not publish this server. Memtro's Zendesk connector reads Zendesk through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Support desk: search tickets, read ticket conversations (public replies and internal notes), look up users and organisations, and pull recently updated tickets; can also raise a ticket, reply to one, add an internal note, change its status, priority, assignee or tags, and merge duplicates into one when you ask.

Reads

  • zendesk_search_ticketsSearch Zendesk tickets.
  • zendesk_get_ticketOne ticket with requester, assignee and organisation names and its full comment thread in order (public replies and internal notes, HTML stripped).
  • zendesk_usersFind users (end users and agents) by name, email or phone, or get one by id with the tickets they requested.
  • zendesk_organizationsOrganisations: list them, find by name prefix, or get one by id with its members and recent tickets.
  • zendesk_recent_ticketsTickets changed since a point in time (incremental export), oldest change first, with a cursor to continue.

Acts, when you ask

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

  • zendesk_create_ticketRaises a new Zendesk ticket.
  • zendesk_replySends a public reply to the requester on a Zendesk ticket, from the agent this connection belongs to.
  • zendesk_add_noteAdds an internal note to a Zendesk ticket.
  • zendesk_update_ticketChanges a Zendesk ticket itself — its status, priority, type, assignee or group, and its tags.
  • zendesk_merge_ticketsMerges duplicate Zendesk tickets into one.

Connect it

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

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

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

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

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

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

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 Zendesk 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

  • › What urgent tickets are still open for Acme?
  • › Show me the full conversation on ticket 4821 including internal notes
  • › Which organisations raised the most tickets this week?
  • › What has changed in support since yesterday morning?

Questions

Is this an official Zendesk MCP server?
No. It is Memtro's MCP server with Memtro's Zendesk connector behind it: the connector reads Zendesk through its API with the credentials you connect on Dashboard → Connections, and Zendesk 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 Zendesk?
Only when you ask, and only what it has been granted: reply to the requester on a ticket; add an internal note to a ticket; change a ticket's status, priority, type, assignee, group or tags; raise a new ticket, for a customer or for the team; merge duplicate tickets into one, which cannot be undone. 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