Freshservice MCP server

What the model can do

Freshservice IT service desk: tickets by date, requester, type or a filter query, a ticket with its conversation thread and time entries, changes, requesters, agents and groups. Can create, update, reply to, note and trash tickets, add and update ticket tasks, log non-billable time, raise and update changes with notes, open problems with notes, and create requesters.

Reads

• freshservice_list_ticketsFreshservice tickets updated since a date (default the last 30 days), newest first unless asked otherwise: subject, type, status, priority, source…
• freshservice_filter_ticketsFreshservice tickets matching a filter query on ticket fields, for questions like "open urgent tickets" or "unassigned tickets in group 12".
• freshservice_get_ticketOne Freshservice ticket with its conversation thread (replies, requester messages and notes, oldest first, text trimmed) and, if asked…
• freshservice_list_changesFreshservice changes (change management) updated since a date, default the last 30 days: subject, status, priority, type, risk, impact, owner…
• freshservice_find_requestersFind Freshservice requesters (the people who raise tickets) by email: id, name, job title, departments and whether active.
• freshservice_list_agentsFreshservice agents: id, name, email, job title and whether active.
• freshservice_list_groupsFreshservice agent groups: id, name and description, for the group_id a ticket, task or change is assigned to.

Acts, when you ask

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

• freshservice_add_private_noteAdds a private note to a Freshservice ticket, written as the agent who owns the API key.
• freshservice_add_time_entryRecords a non-billable time entry on a Freshservice ticket for a named agent: how long, on what date, and what the work was.
• freshservice_create_ticketOpens a Freshservice ticket for a requester (by email or requester_id; an email Freshservice does not know becomes a new requester) with a subject…
• freshservice_update_ticketChanges a Freshservice ticket by id: status (resolve or close it), priority, assigned agent or group, category, department, due date, type or tags…
• freshservice_reply_to_ticketSends a public reply on a Freshservice ticket, written as the agent who owns the API key: the requester…
• freshservice_add_public_noteAdds a public note to a Freshservice ticket, written as the agent who owns the API key: the requester can read it on the portal.
• freshservice_create_ticket_taskAdds a task to a Freshservice ticket with a title, and optionally a description, due date and an assigned agent or group (who Freshservice notifies).
• freshservice_update_ticket_taskUpdates or completes a task on a Freshservice ticket: title, description, due date, status (completed to finish it) or the assigned agent or group.
• freshservice_delete_ticketMoves a Freshservice ticket to the trash.
• freshservice_create_changeRaises a Freshservice change request: a subject, the requester (by id or email), and its priority, impact, risk, type and status…
• freshservice_update_changeUpdates a Freshservice change by id: subject, description, status, priority, impact, risk, type, owner, group or planned window.
• freshservice_add_change_noteAdds a private note (agents only) to a Freshservice change.
• freshservice_create_problemOpens a Freshservice problem record: a subject, a description, the requester, its priority, impact and status, and the date it is due by…
• freshservice_add_problem_noteAdds a note to a Freshservice problem.
• freshservice_create_requesterCreates a Freshservice requester (a person who can raise tickets) with a first name and a primary email, and optionally a last name…

Connect it

First connect Freshservice on Dashboard → Connections, then add Memtro to your client once. The Freshservice 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 Freshservice 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 IT tickets are open for Priya Sharma?
• › Which urgent tickets have no agent assigned?
• › What changes are planned for this weekend, and what is their risk?
• › Reply to ticket 4182 that the replacement laptop arrives Thursday
• › Open a ticket for dan.fletcher@acme.com: VPN drops every hour, high priority

Questions

Is this an official Freshservice MCP server?

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

Only when you ask, and only what it has been granted: add a private note to a ticket (agents only, nobody is emailed); add a non-billable time entry to a ticket for a named agent; create a ticket for a requester; update a ticket's status, priority, assignment, category or tags; send a public reply to the requester on a ticket; add a public note the requester can see; add a task to a ticket; update or complete a ticket task; move a ticket to the trash; raise a change request; update a change; add a private note to a change; open a problem record; add a note to a problem; create a requester. 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