Is this an official HelpDesk MCP server?

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

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 HelpDesk?

Only when you ask, and only what it has been granted: open a ticket for a requester (HelpDesk e-mails them the first message); reply to a ticket's requester (sent to them by e-mail); add an internal note to a ticket (agents only); change a ticket's status, priority, subject, team or assigned agent; add tags to a ticket; add agents as followers of a ticket; send the customer a request to rate the ticket (e-mails them); delete a ticket (to the trash, purged after 30 days). 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.

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.

MCP server · Support

HelpDesk MCP server

HelpDesk in any MCP client, through Memtro: HelpDesk does not publish this server. Memtro's HelpDesk connector reads HelpDesk 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

HelpDesk (HelpDesk.com) email ticketing: tickets with their subject, requester, status, priority, team, assigned agent, tags, rating and messages (text cut short, private notes marked), agents, teams and tags. Can open a ticket for a requester, reply to the requester, add an internal note, change status, priority, subject or assignment, tag a ticket, add followers, ask the customer to rate, and delete a ticket, each only when asked.

Reads

helpdesk_ticketsHelpDesk tickets: short id, subject, requester (name and e-mail), status, priority, team, assigned agent, tags, rating (good, bad…
helpdesk_ticketOne HelpDesk ticket by id: subject, requester (name and e-mail), status, priority, team, agent, tags, followers, rating…
helpdesk_agentsHelpDesk agents: name, e-mail, role (owner is Administrator, normal is Agent, viewer is Viewer), whether active or invited, job title and teams.
helpdesk_teamsHelpDesk teams: id and name, for filtering and assigning tickets.
helpdesk_tagsHelpDesk tags: id, name, its team, and how many tickets carry it.

Acts, when you ask

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

helpdesk_create_ticketOpen a HelpDesk ticket for a requester, with a subject and a first message from the key's agent.
helpdesk_replyReply on a HelpDesk ticket as the key's agent.
helpdesk_add_noteAdd a private note to a HelpDesk ticket as the key's agent.
helpdesk_update_ticketChange a HelpDesk ticket's status, priority, subject, team or assigned agent; only the fields given change.
helpdesk_tag_ticketAdd tags to a HelpDesk ticket (tag ids from helpdesk_tags).
helpdesk_add_followersAdd agents as followers of a HelpDesk ticket, so HelpDesk tells them about its activity.
helpdesk_send_rating_requestE-mail a HelpDesk ticket's requester asking them to rate the help they got.
helpdesk_delete_ticketDelete a HelpDesk ticket.

Connect it

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

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=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-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

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 HelpDesk 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 open and unassigned?
› What did BigCo's last ticket say?
› Which tickets were rated bad this month?
› How many open tickets carry the billing tag?
› Add a note to ticket 1042 saying the refund is approved

Questions

Is this an official HelpDesk MCP server?: No. It is Memtro's MCP server with Memtro's HelpDesk connector behind it: the connector reads HelpDesk through its API with the credentials you connect on Dashboard → Connections, and HelpDesk 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 HelpDesk?: Only when you ask, and only what it has been granted: open a ticket for a requester (HelpDesk e-mails them the first message); reply to a ticket's requester (sent to them by e-mail); add an internal note to a ticket (agents only); change a ticket's status, priority, subject, team or assigned agent; add tags to a ticket; add agents as followers of a ticket; send the customer a request to rate the ticket (e-mails them); delete a ticket (to the trash, purged after 30 days). 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.