--- title: "Zenduty MCP server for AI agents - actionlake" description: "Give Claude 140 Zenduty actions through one MCP server: integrations, global router rules. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/zenduty updated: 2026-10-23 --- 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. [Connect Zenduty free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 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 ``` - 140 actions in one signed file - 64 read look, never change - 52 write create and update - 24 wait for a yes destructive, 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_key` Zenduty 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 call check { 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 2026[apidocs.zenduty.com](https://apidocs.zenduty.com/openapi.json) [apidocs.zenduty.com](https://apidocs.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. - **64** read look, never change - **52** write create and update - **24** destructive wait 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. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `zenduty.teams.list` List all Team objects | List all Team objects. | read | `identity.group.list` 262 connectors | | `zenduty.incident_notes.list` List all Incident Note objects | List all Incident Note objects. | read | `monitoring.incident_note.list` 11 connectors | | `zenduty.team_members.list` List all Team Member objects | List all Team Member objects. | read | `identity.group_member.list` 103 connectors | | `zenduty.incidents.create` Create the Incident object | Create the Incident object. | write | `monitoring.incident.create` 13 connectors | | `zenduty.teams.create` Create the Team object | Create the Team object. | write | `identity.group.create` 205 connectors | | `zenduty.incident_notes.create` Create the Incident Note object | Create the Incident Note object. | write | `monitoring.incident_note.create` 12 connectors | | `zenduty.members.list` List all Account Member objects | List all Account Member objects. | read | `work.workspace_member.list` 26 connectors | | `zenduty.incidents.get` Retrieve the Incident object | Retrieve the Incident object. | read | `monitoring.incident.get` 20 connectors | | `zenduty.teams.delete` Delete the Team object | Delete the Team object. | destructive | `identity.group.delete` 181 connectors | | `zenduty.events.create` Create the Event object | Create the Event object. | write | `monitoring.event.create` 12 connectors | | `zenduty.team_members.update` Update the Team Member object | Update the Team Member object. | write | `identity.group_member.update` 34 connectors | | `zenduty.postmortems.list` List all Postmortem objects | List all Postmortem objects. | read | `monitoring.postmortem.list` 6 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. Read read Which Zenduty incidents are open, and how long has each been open? calls `zenduty.incidents.query` 2. Write write Create the Incident object in Zenduty. Show me exactly what you will send before you save it. calls `zenduty.incidents.create` Governance for Zenduty ## Destructive actions wait for a yes. 24 Zenduty actions are destructive. These are all of them: - Delete the Team object `zenduty.teams.delete` - Delete the Incident Note object `zenduty.incident_notes.delete` - Delete the Postmortem data `zenduty.postmortems.delete` - Delete the Schedule object `zenduty.schedules.delete` - Delete the Escalation Policy object `zenduty.escalation_policies.delete` - Delete the SLA object `zenduty.slas.delete` - Delete the Tag object `zenduty.tags.delete` - Delete User `zenduty.members.delete` - Delete the Service object `zenduty.services.delete` - Delete the Priority object `zenduty.priorities.delete` - Delete the Alert Rule object `zenduty.alert_rules.delete` - Delete the Account Custom Role object `zenduty.custom_roles.delete` - Delete the Integration object `zenduty.integrations.delete` - Delete the Team Member object `zenduty.team_members.delete` - Delete the Incident Tag object `zenduty.incident_tags.delete` - Delete the Global Router data `zenduty.global_routers.delete` - Delete the Incident Role object `zenduty.incident_roles.delete` - Delete the Task Template object `zenduty.task_templates.delete` - Delete the User Contact Methods object `zenduty.contact_methods.delete` - Delete the User Forwarding Rule object `zenduty.forwarding_rules.delete` - Delete the User Notification Rules object `zenduty.notification_rules.delete` - Delete the Global Router Rule data `zenduty.global_router_rules.delete` - Delete an Incident Responder `zenduty.incident_responders.delete` - Delete the Team Maintenance Mode object `zenduty.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. do zenduty.teams.delete confirm_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: "lead@example.com" }, { match: "zenduty.incident_notes.delete", approver: "lead@example.com" }, { match: "zenduty.postmortems.delete", approver: "lead@example.com" } ] } ``` 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. - 1 upstream call per action all 140 Zenduty actions - 140 actions page each page of a long list is one call - 58 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Zenduty action. 140 actions by area: the id your agent calls, what it does, and its effect. **Integrations 7** - `zenduty.integrations.create` Create the Integration object write - `zenduty.integrations.delete` Delete the Integration object destructive - `zenduty.integrations.get` Retrieve the Integration object read - `zenduty.integrations.get_metadata` Fetch metadata of the Integration object read - `zenduty.integrations.list` List all Integration objects read - `zenduty.integrations.regenerate_key` Regenerate the Integration key write - `zenduty.integrations.update` Update the Integration object write **Global router rules 6** - `zenduty.global_router_rules.create` Create the Global Router Rule object write - `zenduty.global_router_rules.delete` Delete the Global Router Rule data destructive - `zenduty.global_router_rules.get` Retrieve the Global Router Rule object read - `zenduty.global_router_rules.list` List all Global Router Rule objects read - `zenduty.global_router_rules.reorder` Update the Global Router Rule object write - `zenduty.global_router_rules.update` Update the Global Router Rule data write **Alert rules 5** - `zenduty.alert_rules.create` Create the Alert Rule object write - `zenduty.alert_rules.delete` Delete the Alert Rule object destructive - `zenduty.alert_rules.get` Retrieve the Alert Rule object read - `zenduty.alert_rules.list` List all Alert Rules objects read - `zenduty.alert_rules.update` Update the Alert Rule data write **Custom roles 5** - `zenduty.custom_roles.create` Create the Account Custom Role object write - `zenduty.custom_roles.delete` Delete the Account Custom Role object destructive - `zenduty.custom_roles.get` Retrieve the Account Custom Role object read - `zenduty.custom_roles.list` List all Account Custom Role objects read - `zenduty.custom_roles.update` Update the Account Custom Role object write **Escalation policies 5** - `zenduty.escalation_policies.create` Create the Escalation Policy object write - `zenduty.escalation_policies.delete` Delete the Escalation Policy object destructive - `zenduty.escalation_policies.get` Retrieve the Escalation Policy object read - `zenduty.escalation_policies.list` List all Escalation Policy objects read - `zenduty.escalation_policies.update` Update the Escalation Policy object write **Global routers 5** - `zenduty.global_routers.create` Create the Global Router object write - `zenduty.global_routers.delete` Delete the Global Router data destructive - `zenduty.global_routers.get` Retrieve the Global Router object read - `zenduty.global_routers.list` List all Global Router objects read - `zenduty.global_routers.update` Update the Global Router data write **Incident notes 5** - `zenduty.incident_notes.create` Create the Incident Note object write - `zenduty.incident_notes.delete` Delete the Incident Note object destructive - `zenduty.incident_notes.get` Retrieve the Incident Note object read - `zenduty.incident_notes.list` List all Incident Note objects read - `zenduty.incident_notes.update` Update the Incident Note object write **Incident roles 5** - `zenduty.incident_roles.create` Create the Incident Role object write - `zenduty.incident_roles.delete` Delete the Incident Role object destructive - `zenduty.incident_roles.get` Retrieve the Incident Role object read - `zenduty.incident_roles.list` List all Incident Role objects read - `zenduty.incident_roles.update` Update the Incident Role object write **Maintenance windows 5** - `zenduty.maintenance_windows.create` Create the Team Maintenance Mode object write - `zenduty.maintenance_windows.delete` Delete the Team Maintenance Mode object destructive - `zenduty.maintenance_windows.get` Retrieve the Team Maintenance Mode object read - `zenduty.maintenance_windows.list` List all Team Maintenance Mode objects read - `zenduty.maintenance_windows.update` Update Team Maintenance Mode object write **Members 5** - `zenduty.members.delete` Delete User destructive - `zenduty.members.get` Retrieve the Account Member object read - `zenduty.members.invite` Invite User write - `zenduty.members.list` List all Account Member objects read - `zenduty.members.update` Update the Account Member object write **Postmortems 5** - `zenduty.postmortems.create` Create the Postmortem object write - `zenduty.postmortems.delete` Delete the Postmortem data destructive - `zenduty.postmortems.get` Retrieve the Postmortem object read - `zenduty.postmortems.list` List all Postmortem objects read - `zenduty.postmortems.update` Update the Postmortem data write **Priorities 5** - `zenduty.priorities.create` Create the Priority object write - `zenduty.priorities.delete` Delete the Priority object destructive - `zenduty.priorities.get` Retrieve the Priority object read - `zenduty.priorities.list` List all Priority objects read - `zenduty.priorities.update` Update the Priority object write **Schedules 5** - `zenduty.schedules.create` Create the Schedule object write - `zenduty.schedules.delete` Delete the Schedule object destructive - `zenduty.schedules.get` Retrieve the Schedule object read - `zenduty.schedules.list` List all Schedule objects read - `zenduty.schedules.update` Update the Schedule object write **Services 5** - `zenduty.services.create` Create the Service object write - `zenduty.services.delete` Delete the Service object destructive - `zenduty.services.get` Retrieve the Service object read - `zenduty.services.list` List all Service objects read - `zenduty.services.update` Update the Service object write **Slas 5** - `zenduty.slas.create` Create the SLA object write - `zenduty.slas.delete` Delete the SLA object destructive - `zenduty.slas.get` Retrieve the SLA object read - `zenduty.slas.list` List all SLA objects read - `zenduty.slas.update` Update the SLA object write **Tags 5** - `zenduty.tags.create` Create the Tag object write - `zenduty.tags.delete` Delete the Tag object destructive - `zenduty.tags.get` Retrieve the Tag object read - `zenduty.tags.list` List all Tag objects read - `zenduty.tags.update` Update the Tag object write **Task templates 5** - `zenduty.task_templates.create` Create the Task Template object write - `zenduty.task_templates.delete` Delete the Task Template object destructive - `zenduty.task_templates.get` Retrieve the Task Template object read - `zenduty.task_templates.list` List all Task Template objects read - `zenduty.task_templates.update` Update the Task Template object write **Team members 5** - `zenduty.team_members.create` Add user to Team write - `zenduty.team_members.delete` Delete the Team Member object destructive - `zenduty.team_members.get` Retrieve the Team Member object read - `zenduty.team_members.list` List all Team Member objects read - `zenduty.team_members.update` Update the Team Member object write **Teams 5** - `zenduty.teams.create` Create the Team object write - `zenduty.teams.delete` Delete the Team object destructive - `zenduty.teams.get` Retrieve the Team object read - `zenduty.teams.list` List all Team objects read - `zenduty.teams.update` Update the Team object write **Analytics 4** - `zenduty.analytics.incident_stats` Get Incident Stats read - `zenduty.analytics.service_analytics` Get Service Analytics read - `zenduty.analytics.team_analytics` Get Team Analytics read - `zenduty.analytics.user_analytics` Get User Analytics read **Contact methods 4** - `zenduty.contact_methods.create` Create the User Contact Methods object write - `zenduty.contact_methods.delete` Delete the User Contact Methods object destructive - `zenduty.contact_methods.get` Retrieve the User Contact Methods object read - `zenduty.contact_methods.list` List all User Contact Method objects read **Forwarding rules 4** - `zenduty.forwarding_rules.create` Create the User Forwarding Rules object write - `zenduty.forwarding_rules.delete` Delete the User Forwarding Rule object destructive - `zenduty.forwarding_rules.get` Retrieve the User Forwarding Rules object read - `zenduty.forwarding_rules.list` List all User Forwarding Rule objects read **Incident responders 4** - `zenduty.incident_responders.create` Add an Incident Responder write - `zenduty.incident_responders.delete` Delete an Incident Responder destructive - `zenduty.incident_responders.get` Retrieve an Incident Responder read - `zenduty.incident_responders.list` List all Incident Responders objects read **Incident tags 4** - `zenduty.incident_tags.create` Create the Incident Tag object write - `zenduty.incident_tags.delete` Delete the Incident Tag object destructive - `zenduty.incident_tags.get` Retrieve the Incident Tag object read - `zenduty.incident_tags.list` List all Incident Tag objects read **Incidents 4** - `zenduty.incidents.create` Create the Incident object write - `zenduty.incidents.get` Retrieve the Incident object read - `zenduty.incidents.query` List all Incident objects(filtered) read - `zenduty.incidents.update` Update the Incident object write **Notification rules 4** - `zenduty.notification_rules.create` Create the User Notification Rules object write - `zenduty.notification_rules.delete` Delete the User Notification Rules object destructive - `zenduty.notification_rules.get` Retrieve the User Notification Rule object read - `zenduty.notification_rules.list` List all Users' Notification Rule objects read **Oncall 4** - `zenduty.oncall.get_escalation_policy` Retrieve Escalation Policy OnCall object in an Escalation Policy read - `zenduty.oncall.get_service` Retrieve Escalation Policy OnCall object in a Service read - `zenduty.oncall.list_team` List all Escalation Policy OnCall object's in a Team V2 read - `zenduty.oncall.list_team_v1` List all Escalation Policy OnCall object's in a Team V1 read **Events 3** - `zenduty.events.create` Create the Event object write - `zenduty.events.create_generic` Create the Event object write - `zenduty.events.get_alert_status` Get the status of an Alert read **Schedule overrides 2** - `zenduty.schedule_overrides.create` Create the Schedule Override object write - `zenduty.schedule_overrides.list` List all Schedule overrides objects read **Team permissions 2** - `zenduty.team_permissions.get` Retrieve Team Permission object read - `zenduty.team_permissions.update` Update the Team Permission object write **User custom roles 2** - `zenduty.user_custom_roles.create` Create the User Custom Role object write - `zenduty.user_custom_roles.list` List all User Custom Role objects read **Incident alerts 1** - `zenduty.incident_alerts.list` List all Incident Alert objects read 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. ## More connectors like Zenduty Shares the most action names with - [FireHydrant 24](https://actionlake.com/connectors/firehydrant) - [ilert 22](https://actionlake.com/connectors/ilert) - [Squadcast 21](https://actionlake.com/connectors/squadcast) - [incident.io 18](https://actionlake.com/connectors/incident-io) - [Better Stack Uptime 17](https://actionlake.com/connectors/better-stack-uptime) - [Rootly 16](https://actionlake.com/connectors/rootly) Joins with, on shared entities - [Delinea Secret Server 2](https://actionlake.com/connectors/delinea-secret-server) - [Canvas LMS 2](https://actionlake.com/connectors/canvas-lms) - [D2L Brightspace 2](https://actionlake.com/connectors/d2l-brightspace) - [Appwrite Cloud 2](https://actionlake.com/connectors/appwrite-cloud) - [Dynatrace 2](https://actionlake.com/connectors/dynatrace) - [Tableau 2](https://actionlake.com/connectors/tableau) Browse - [All Service desk & support connectors](https://actionlake.com/connectors/category/service-desk-and-support) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Zenduty; the name is the vendor's own. Counts are from the Zenduty service file, version 1.0.0. ## Give your agent Zenduty today. [Connect Zenduty free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/zenduty More: https://actionlake.com/llms.txt