Zenduty MCP server

What the model can do

Zenduty (Xurrent IMR) incident management: incidents by status, team, service, priority, tag, assignee and creation date, one incident with its notes and tags, its alerts, teams with their tags, priorities and SLAs, services and maintenance windows, who is on call per escalation policy, on-call schedules with overrides, and account members; when you ask, can create an incident (pages on-call), acknowledge, resolve, reassign or edit one, add, edit or delete notes, tag and untag, add a responder (pages them), start or delete a maintenance window, override who is on call, invite a user and remove a user.

Reads

• zenduty_list_incidentsZenduty incidents: number, title, status, urgency, service and team, assignee, priority, SLA, tags and when created, acknowledged and resolved.
• zenduty_get_incidentOne Zenduty incident by its number, with its notes (who wrote what, when) and tags (with the ids that remove them).
• zenduty_list_incident_alertsThe alerts behind a Zenduty incident: message, alert type, when, whether suppressed, the entity id and which integration sent it.
• zenduty_list_teamsZenduty teams with their ids and member counts.
• zenduty_list_servicesA Zenduty team's services (id, name, escalation policy, whether under maintenance) and the team's maintenance windows (id, name, start, end…
• zenduty_who_is_on_callWho is on call now for a Zenduty team, per escalation policy and rule: position, delay in minutes and the people (name and username).
• zenduty_list_schedulesA Zenduty team's on-call schedules: id, name, time zone, each layer's rotation (who, in order, shift length, start and end) and overrides…
• zenduty_list_membersPeople in the Zenduty account: name, username (what assignment, responders and overrides take), account role number, time zone and when they joined.

Acts, when you ask

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

• zenduty_create_incidentCreates a Zenduty incident on a service, which triggers the service's escalation policy and pages whoever is on call (phone, SMS…
• zenduty_update_incidentChanges a Zenduty incident: acknowledge, resolve or re-trigger it, reassign it (notifies the new assignee), or change its title, summary, urgency…
• zenduty_add_incident_noteAdds a note to a Zenduty incident's timeline, visible to everyone on the incident.
• zenduty_update_incident_noteReplaces the text of a note on a Zenduty incident.
• zenduty_delete_incident_notePermanently deletes a note from a Zenduty incident.
• zenduty_tag_incidentAdds one of the team's tags to a Zenduty incident.
• zenduty_untag_incidentRemoves a tag from a Zenduty incident.
• zenduty_add_responderAdds a responder to a Zenduty incident, either a person (by username) or a whole escalation policy, and pages them.
• zenduty_create_maintenanceCreates a maintenance window for a Zenduty team: alerts on the named services are suppressed between start and end, so nobody is paged for them.
• zenduty_delete_maintenancePermanently deletes a Zenduty maintenance window, so the services page again at once if they alert.
• zenduty_override_on_callAdds an override to a Zenduty on-call schedule: the named person is on call instead of the rota between start and end, and is the one paged.
• zenduty_invite_userInvites a person to the Zenduty account and a team; Zenduty emails them an invitation.
• zenduty_remove_userRemoves a user from the Zenduty account; they lose access and stop being paged.

Connect it

First connect Zenduty on Dashboard → Connections, then add Memtro to your client once. The Zenduty 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 Zenduty 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 incidents are open right now?
• › Who is on call for the platform team?
• › What alerts are behind incident 412?
• › Which services are under maintenance this weekend?
• › Acknowledge incident 412.

Questions

Is this an official Zenduty MCP server?

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

Only when you ask, and only what it has been granted: create an incident (pages the service's on-call); acknowledge, resolve, reassign or edit an incident; add a note to an incident; edit an incident note; delete an incident note; tag an incident; remove a tag from an incident; add a responder to an incident (pages them); create a maintenance window that silences a team's services; delete a maintenance window; override who is on call on a schedule for a period; invite a user to the account and a team (emails them); remove a user from the account. 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 · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server