Skip to content

Connectors · Service desk & support

Zenduty MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Zenduty and the rest of your systems. It gives your agent 140 Zenduty actions (64 reads, 52 writes and 24 that wait for a confirmation) and holds the Zenduty credential itself, so the agent never does. It paces Zenduty's limits and records every call.

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "zenduty.teams.list",  intent: "check which Zenduty account is connected"}# List all Team objects · read · 1 upstream call
  • 140actionsin one signed file
  • 64readlook, never change
  • 52writecreate and update
  • 24wait for a yesdestructive, confirmed first

Set up

Connect Zenduty in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Zenduty.

    API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyZenduty API token (Account Settings > API Keys; account owner or admin)
    account { op: "connections.requirements", service: "zenduty" }
    # free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "zenduty.teams.list" }# list all team objects · read · 1 upstream callcheck { action: "zenduty.incidents.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Zenduty at a glance

Sign-in
API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Limits we pace to
5 calls a second, per connection
API covered
Zenduty REST API (OpenAPI 3.0.0, 1.1.0)www.zenduty.com
Built from
Zenduty's documentation, read 23 October 2026apidocs.zenduty.comapidocs.zenduty.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
58 of 64 reads, for up to 5 minutes; a write clears what it affects
Shared entities
6, so ask can line Zenduty up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Zenduty.

140 actions in 32 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 64readlook, never change
  • 52writecreate and update
  • 24destructivewait for a confirmation
  1. Integrations

    7

    3 read · 3 write · 1 destructive

    Create the Integration object · List all Integration objects · Retrieve the Integration object · Fetch metadata of the Integration object

  2. Global router rules

    6

    2 read · 3 write · 1 destructive

    Create the Global Router Rule object · List all Global Router Rule objects · Retrieve the Global Router Rule object · Update the Global Router Rule object

  3. Alert rules

    5

    2 read · 2 write · 1 destructive

    Create the Alert Rule object · List all Alert Rules objects · Retrieve the Alert Rule object · Update the Alert Rule data

  4. Custom roles

    5

    2 read · 2 write · 1 destructive

    Create the Account Custom Role object · List all Account Custom Role objects · Retrieve the Account Custom Role object · Update the Account Custom Role object

  5. Escalation policies

    5

    2 read · 2 write · 1 destructive

    Create the Escalation Policy object · List all Escalation Policy objects · Retrieve the Escalation Policy object · Update the Escalation Policy object

  6. Global routers

    5

    2 read · 2 write · 1 destructive

    Create the Global Router object · List all Global Router objects · Retrieve the Global Router object · Update the Global Router data

  7. Incident notes

    5

    2 read · 2 write · 1 destructive

    List all Incident Note objects · Create the Incident Note object · Update the Incident Note object · Delete the Incident Note object

  8. Incident roles

    5

    2 read · 2 write · 1 destructive

    Create the Incident Role object · List all Incident Role objects · Retrieve the Incident Role object · Update the Incident Role object

24 more areas · 97 actions
  • Maintenance windows 5
  • Members 5
  • Postmortems 5
  • Priorities 5
  • Schedules 5
  • Services 5
  • Slas 5
  • Tags 5
  • Task templates 5
  • Team members 5
  • Teams 5
  • Analytics 4
  • Contact methods 4
  • Forwarding rules 4
  • Incident responders 4
  • Incident tags 4
  • Incidents 4
  • Notification rules 4
  • Oncall 4
  • Events 3
  • Schedule overrides 2
  • Team permissions 2
  • User custom roles 2
  • Incident alerts 1

Top actions

The Zenduty API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 37 of Zenduty's 38 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
zenduty.teams.listList all Team objectsList all Team objects.readidentity.group.list262 connectors
zenduty.incident_notes.listList all Incident Note objectsList all Incident Note objects.readmonitoring.incident_note.list11 connectors
zenduty.team_members.listList all Team Member objectsList all Team Member objects.readidentity.group_member.list103 connectors
zenduty.incidents.createCreate the Incident objectCreate the Incident object.writemonitoring.incident.create13 connectors
zenduty.teams.createCreate the Team objectCreate the Team object.writeidentity.group.create205 connectors
zenduty.incident_notes.createCreate the Incident Note objectCreate the Incident Note object.writemonitoring.incident_note.create12 connectors
zenduty.members.listList all Account Member objectsList all Account Member objects.readwork.workspace_member.list26 connectors
zenduty.incidents.getRetrieve the Incident objectRetrieve the Incident object.readmonitoring.incident.get20 connectors
zenduty.teams.deleteDelete the Team objectDelete the Team object.destructiveidentity.group.delete181 connectors
zenduty.events.createCreate the Event objectCreate the Event object.writemonitoring.event.create12 connectors
zenduty.team_members.updateUpdate the Team Member objectUpdate the Team Member object.writeidentity.group_member.update34 connectors
zenduty.postmortems.listList all Postmortem objectsList all Postmortem objects.readmonitoring.postmortem.list6 connectors

Try it

Prompts to paste into Claude.

Each one names the Zenduty actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Which Zenduty incidents are open, and how long has each been open?

    callszenduty.incidents.query

  2. Writewrite

    Create the Incident object in Zenduty. Show me exactly what you will send before you save it.

    callszenduty.incidents.create

Governance for Zenduty

Destructive actions wait for a yes.

24 Zenduty actions are destructive. These are all of them:

  • Delete the Team objectzenduty.teams.delete
  • Delete the Incident Note objectzenduty.incident_notes.delete
  • Delete the Postmortem datazenduty.postmortems.delete
  • Delete the Schedule objectzenduty.schedules.delete
  • Delete the Escalation Policy objectzenduty.escalation_policies.delete
  • Delete the SLA objectzenduty.slas.delete
  • Delete the Tag objectzenduty.tags.delete
  • Delete Userzenduty.members.delete
  • Delete the Service objectzenduty.services.delete
  • Delete the Priority objectzenduty.priorities.delete
  • Delete the Alert Rule objectzenduty.alert_rules.delete
  • Delete the Account Custom Role objectzenduty.custom_roles.delete
  • Delete the Integration objectzenduty.integrations.delete
  • Delete the Team Member objectzenduty.team_members.delete
  • Delete the Incident Tag objectzenduty.incident_tags.delete
  • Delete the Global Router datazenduty.global_routers.delete
  • Delete the Incident Role objectzenduty.incident_roles.delete
  • Delete the Task Template objectzenduty.task_templates.delete
  • Delete the User Contact Methods objectzenduty.contact_methods.delete
  • Delete the User Forwarding Rule objectzenduty.forwarding_rules.delete
  • Delete the User Notification Rules objectzenduty.notification_rules.delete
  • Delete the Global Router Rule datazenduty.global_router_rules.delete
  • Delete an Incident Responderzenduty.incident_responders.delete
  • Delete the Team Maintenance Mode objectzenduty.maintenance_windows.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dozenduty.teams.deleteconfirm_policy: human

Delete the Team object?

intent: the user asked me to delete the Team object

run suspended · waiting for a named person · key zenduty-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "zenduty-agent",  allowed_actions: ["zenduty.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "zenduty.teams.delete", approver: "[email protected]" },    { match: "zenduty.incident_notes.delete", approver: "[email protected]" },    { match: "zenduty.postmortems.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Zenduty only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Zenduty costs on actionlake.

Every Zenduty action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Zenduty refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 140 Zenduty actions
  • 140actions pageeach page of a long list is one call
  • 58reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Zenduty action.

140 actions by area: the id your agent calls, what it does, and its effect.

Integrations7
  • zenduty.integrations.createCreate the Integration objectwrite
  • zenduty.integrations.deleteDelete the Integration objectdestructive
  • zenduty.integrations.getRetrieve the Integration objectread
  • zenduty.integrations.get_metadataFetch metadata of the Integration objectread
  • zenduty.integrations.listList all Integration objectsread
  • zenduty.integrations.regenerate_keyRegenerate the Integration keywrite
  • zenduty.integrations.updateUpdate the Integration objectwrite
Global router rules6
  • zenduty.global_router_rules.createCreate the Global Router Rule objectwrite
  • zenduty.global_router_rules.deleteDelete the Global Router Rule datadestructive
  • zenduty.global_router_rules.getRetrieve the Global Router Rule objectread
  • zenduty.global_router_rules.listList all Global Router Rule objectsread
  • zenduty.global_router_rules.reorderUpdate the Global Router Rule objectwrite
  • zenduty.global_router_rules.updateUpdate the Global Router Rule datawrite
Alert rules5
  • zenduty.alert_rules.createCreate the Alert Rule objectwrite
  • zenduty.alert_rules.deleteDelete the Alert Rule objectdestructive
  • zenduty.alert_rules.getRetrieve the Alert Rule objectread
  • zenduty.alert_rules.listList all Alert Rules objectsread
  • zenduty.alert_rules.updateUpdate the Alert Rule datawrite
Custom roles5
  • zenduty.custom_roles.createCreate the Account Custom Role objectwrite
  • zenduty.custom_roles.deleteDelete the Account Custom Role objectdestructive
  • zenduty.custom_roles.getRetrieve the Account Custom Role objectread
  • zenduty.custom_roles.listList all Account Custom Role objectsread
  • zenduty.custom_roles.updateUpdate the Account Custom Role objectwrite
Escalation policies5
  • zenduty.escalation_policies.createCreate the Escalation Policy objectwrite
  • zenduty.escalation_policies.deleteDelete the Escalation Policy objectdestructive
  • zenduty.escalation_policies.getRetrieve the Escalation Policy objectread
  • zenduty.escalation_policies.listList all Escalation Policy objectsread
  • zenduty.escalation_policies.updateUpdate the Escalation Policy objectwrite
Global routers5
  • zenduty.global_routers.createCreate the Global Router objectwrite
  • zenduty.global_routers.deleteDelete the Global Router datadestructive
  • zenduty.global_routers.getRetrieve the Global Router objectread
  • zenduty.global_routers.listList all Global Router objectsread
  • zenduty.global_routers.updateUpdate the Global Router datawrite
Incident notes5
  • zenduty.incident_notes.createCreate the Incident Note objectwrite
  • zenduty.incident_notes.deleteDelete the Incident Note objectdestructive
  • zenduty.incident_notes.getRetrieve the Incident Note objectread
  • zenduty.incident_notes.listList all Incident Note objectsread
  • zenduty.incident_notes.updateUpdate the Incident Note objectwrite
Incident roles5
  • zenduty.incident_roles.createCreate the Incident Role objectwrite
  • zenduty.incident_roles.deleteDelete the Incident Role objectdestructive
  • zenduty.incident_roles.getRetrieve the Incident Role objectread
  • zenduty.incident_roles.listList all Incident Role objectsread
  • zenduty.incident_roles.updateUpdate the Incident Role objectwrite
Maintenance windows5
  • zenduty.maintenance_windows.createCreate the Team Maintenance Mode objectwrite
  • zenduty.maintenance_windows.deleteDelete the Team Maintenance Mode objectdestructive
  • zenduty.maintenance_windows.getRetrieve the Team Maintenance Mode objectread
  • zenduty.maintenance_windows.listList all Team Maintenance Mode objectsread
  • zenduty.maintenance_windows.updateUpdate Team Maintenance Mode objectwrite
Members5
  • zenduty.members.deleteDelete Userdestructive
  • zenduty.members.getRetrieve the Account Member objectread
  • zenduty.members.inviteInvite Userwrite
  • zenduty.members.listList all Account Member objectsread
  • zenduty.members.updateUpdate the Account Member objectwrite
Postmortems5
  • zenduty.postmortems.createCreate the Postmortem objectwrite
  • zenduty.postmortems.deleteDelete the Postmortem datadestructive
  • zenduty.postmortems.getRetrieve the Postmortem objectread
  • zenduty.postmortems.listList all Postmortem objectsread
  • zenduty.postmortems.updateUpdate the Postmortem datawrite
Priorities5
  • zenduty.priorities.createCreate the Priority objectwrite
  • zenduty.priorities.deleteDelete the Priority objectdestructive
  • zenduty.priorities.getRetrieve the Priority objectread
  • zenduty.priorities.listList all Priority objectsread
  • zenduty.priorities.updateUpdate the Priority objectwrite
Schedules5
  • zenduty.schedules.createCreate the Schedule objectwrite
  • zenduty.schedules.deleteDelete the Schedule objectdestructive
  • zenduty.schedules.getRetrieve the Schedule objectread
  • zenduty.schedules.listList all Schedule objectsread
  • zenduty.schedules.updateUpdate the Schedule objectwrite
Services5
  • zenduty.services.createCreate the Service objectwrite
  • zenduty.services.deleteDelete the Service objectdestructive
  • zenduty.services.getRetrieve the Service objectread
  • zenduty.services.listList all Service objectsread
  • zenduty.services.updateUpdate the Service objectwrite
Slas5
  • zenduty.slas.createCreate the SLA objectwrite
  • zenduty.slas.deleteDelete the SLA objectdestructive
  • zenduty.slas.getRetrieve the SLA objectread
  • zenduty.slas.listList all SLA objectsread
  • zenduty.slas.updateUpdate the SLA objectwrite
Tags5
  • zenduty.tags.createCreate the Tag objectwrite
  • zenduty.tags.deleteDelete the Tag objectdestructive
  • zenduty.tags.getRetrieve the Tag objectread
  • zenduty.tags.listList all Tag objectsread
  • zenduty.tags.updateUpdate the Tag objectwrite
Task templates5
  • zenduty.task_templates.createCreate the Task Template objectwrite
  • zenduty.task_templates.deleteDelete the Task Template objectdestructive
  • zenduty.task_templates.getRetrieve the Task Template objectread
  • zenduty.task_templates.listList all Task Template objectsread
  • zenduty.task_templates.updateUpdate the Task Template objectwrite
Team members5
  • zenduty.team_members.createAdd user to Teamwrite
  • zenduty.team_members.deleteDelete the Team Member objectdestructive
  • zenduty.team_members.getRetrieve the Team Member objectread
  • zenduty.team_members.listList all Team Member objectsread
  • zenduty.team_members.updateUpdate the Team Member objectwrite
Teams5
  • zenduty.teams.createCreate the Team objectwrite
  • zenduty.teams.deleteDelete the Team objectdestructive
  • zenduty.teams.getRetrieve the Team objectread
  • zenduty.teams.listList all Team objectsread
  • zenduty.teams.updateUpdate the Team objectwrite
Analytics4
  • zenduty.analytics.incident_statsGet Incident Statsread
  • zenduty.analytics.service_analyticsGet Service Analyticsread
  • zenduty.analytics.team_analyticsGet Team Analyticsread
  • zenduty.analytics.user_analyticsGet User Analyticsread
Contact methods4
  • zenduty.contact_methods.createCreate the User Contact Methods objectwrite
  • zenduty.contact_methods.deleteDelete the User Contact Methods objectdestructive
  • zenduty.contact_methods.getRetrieve the User Contact Methods objectread
  • zenduty.contact_methods.listList all User Contact Method objectsread
Forwarding rules4
  • zenduty.forwarding_rules.createCreate the User Forwarding Rules objectwrite
  • zenduty.forwarding_rules.deleteDelete the User Forwarding Rule objectdestructive
  • zenduty.forwarding_rules.getRetrieve the User Forwarding Rules objectread
  • zenduty.forwarding_rules.listList all User Forwarding Rule objectsread
Incident responders4
  • zenduty.incident_responders.createAdd an Incident Responderwrite
  • zenduty.incident_responders.deleteDelete an Incident Responderdestructive
  • zenduty.incident_responders.getRetrieve an Incident Responderread
  • zenduty.incident_responders.listList all Incident Responders objectsread
Incident tags4
  • zenduty.incident_tags.createCreate the Incident Tag objectwrite
  • zenduty.incident_tags.deleteDelete the Incident Tag objectdestructive
  • zenduty.incident_tags.getRetrieve the Incident Tag objectread
  • zenduty.incident_tags.listList all Incident Tag objectsread
Incidents4
  • zenduty.incidents.createCreate the Incident objectwrite
  • zenduty.incidents.getRetrieve the Incident objectread
  • zenduty.incidents.queryList all Incident objects(filtered)read
  • zenduty.incidents.updateUpdate the Incident objectwrite
Notification rules4
  • zenduty.notification_rules.createCreate the User Notification Rules objectwrite
  • zenduty.notification_rules.deleteDelete the User Notification Rules objectdestructive
  • zenduty.notification_rules.getRetrieve the User Notification Rule objectread
  • zenduty.notification_rules.listList all Users' Notification Rule objectsread
Oncall4
  • zenduty.oncall.get_escalation_policyRetrieve Escalation Policy OnCall object in an Escalation Policyread
  • zenduty.oncall.get_serviceRetrieve Escalation Policy OnCall object in a Serviceread
  • zenduty.oncall.list_teamList all Escalation Policy OnCall object's in a Team V2read
  • zenduty.oncall.list_team_v1List all Escalation Policy OnCall object's in a Team V1read
Events3
  • zenduty.events.createCreate the Event objectwrite
  • zenduty.events.create_genericCreate the Event objectwrite
  • zenduty.events.get_alert_statusGet the status of an Alertread
Schedule overrides2
  • zenduty.schedule_overrides.createCreate the Schedule Override objectwrite
  • zenduty.schedule_overrides.listList all Schedule overrides objectsread
Team permissions2
  • zenduty.team_permissions.getRetrieve Team Permission objectread
  • zenduty.team_permissions.updateUpdate the Team Permission objectwrite
User custom roles2
  • zenduty.user_custom_roles.createCreate the User Custom Role objectwrite
  • zenduty.user_custom_roles.listList all User Custom Role objectsread
Incident alerts1
  • zenduty.incident_alerts.listList all Incident Alert objectsread

Questions

The Zenduty MCP server, answered.

Is there a Zenduty MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 140 Zenduty actions across integrations, global router rules, alert rules and custom roles, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Zenduty.

What do I need to connect Zenduty?

Zenduty API token (Account Settings > API Keys; account owner or admin). The free call account { op: "connections.requirements", service: "zenduty" } lists exactly what to paste.

Can an AI agent delete or change things in Zenduty?

Only if its key allows it, and only with an explicit confirmation. 24 Zenduty actions are destructive, including delete the Team object, delete the Incident Note object and delete the Postmortem data. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Zenduty API limit?

actionlake paces every call to the limits in the Zenduty service file: 5 calls a second per connection. Repeated reads are answered from cache (58 Zenduty actions can be), which never reaches Zenduty.

What does a Zenduty action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (140 Zenduty actions page). Cache hits, searches, dry runs and calls Zenduty refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Zenduty API does it cover?

The Zenduty REST API (OpenAPI 3.0.0, 1.1.0) at www.zenduty.com. It is built from Zenduty's documentation as read on 23 October 2026. 140 actions in 32 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Zenduty data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Zenduty credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Zenduty today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.