Freshdesk MCP server
Freshdesk in any MCP client, through Memtro: Freshdesk does not publish this server. Memtro's Freshdesk connector reads Freshdesk 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: search and list tickets, read full ticket conversations, and look up contacts, companies, agents and groups; can also raise a ticket, reply to the requester by email, add a note to a ticket, change its status, priority, assigned agent, group or tags, and merge duplicates into one ticket when you ask.
Reads
freshdesk_search_ticketsSearch Freshdesk tickets with its filter query language.freshdesk_list_ticketsList tickets newest-updated first, filtered by requester email, requester/company id, status and updated_since.freshdesk_get_ticketOne ticket with its description and the full conversation (customer messages, agent replies, notes) in chronological order, HTML stripped.freshdesk_contactsFind contacts (requesters) by email or name, list a company's contacts, or get one contact by id with their recent tickets.freshdesk_companiesFind companies by name, list them, or get one by id with its contacts.freshdesk_agentsAgents and groups, to translate responder_id / agent_id and group_id into names.
Acts, when you ask
These change something in Freshdesk. 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.
freshdesk_reply_ticketSends a public reply on a Freshdesk ticket, which Freshdesk EMAILS to the requester, under the name of the agent this API key belongs to.freshdesk_add_noteAdds a note to a Freshdesk ticket.freshdesk_update_ticketChanges a Freshdesk ticket itself — its status, priority, the agent it is assigned to, its group, its type or its tags.freshdesk_create_ticketRaises a new Freshdesk ticket.freshdesk_merge_ticketsMerges duplicate Freshdesk tickets into one.
Connect it
First connect Freshdesk on Dashboard → Connections, then add Memtro to your client once. The Freshdesk 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 Freshdesk 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 urgent tickets are still open?
- › What did we tell Acme about the billing bug last week?
- › Show me every ticket from jane@acme.com
- › Who is handling the escalated tickets in the Enterprise group?
Questions
- Is this an official Freshdesk MCP server?
- No. It is Memtro's MCP server with Memtro's Freshdesk connector behind it: the connector reads Freshdesk through its API with the credentials you connect on Dashboard → Connections, and Freshdesk 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 Freshdesk?
- Only when you ask, and only what it has been granted: raise a new ticket for a requester; reply to the requester on a ticket, which Freshdesk emails them; add a note to a ticket, for colleagues or for the requester; change a ticket's status, priority, assigned agent, group, type or tags; 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.