Zendesk Admin MCP Server
Local MCP server for Zendesk admin/config: manage business rules, ticketing config, schedules/holidays, skills routing, and read inventory/audit logs, with guarded destructive writes.
Full CRUD for triggers, automations, macros, views, SLA policies, groups, ticket fields, ticket forms, webhooks, schedules, and holidays.
Reorder trigger precedence, set weekly schedule hours, and bulk-apply holidays to multiple schedules.
Skills-based routing: list skill types/skills/agent skills, find agents with a skill, assess coverage, and bulk add/remove agent skills (up to 100).
Read-only audit logs, filterable by type/actor/time, and per-object audit history (Enterprise).
Read-only inventory: account settings, installed apps, brands, agent roles, tags, and locales.
Guarded operations: deletes and updates to triggers/automations/SLAs/schedules, trigger reorder, schedule hours/holidays, and agent skills require preview then
require_confirm: true.Lower-risk creates/updates (macros, views, groups, fields, forms, webhooks) execute directly.
Credentials come from shared
~/.config/zendesk-mcp/config.jsonor env vars; Enterprise/plan limitations apply for audit logs, business hours, and skills routing.
Provides tools for administering Zendesk configuration, including full CRUD on triggers, automations, macros, views, SLA policies, groups, ticket fields, ticket forms, and webhooks; read-only audit logs; and read-only inventory of account settings, installed apps, brands, agent roles, tags, and locales.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Zendesk Admin MCP Server list all active triggers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@sniebauer/zendesk-admin-mcp
Local MCP server for Zendesk admin/config work — the companion to @sniebauer/zendesk-mcp (day-to-day support).
73 tools: full CRUD on triggers, automations, macros, views, SLA policies, groups, ticket fields, ticket forms, webhooks, and schedules (business hours) with their holidays; skills-based routing (who holds which skills, coverage if an agent is out, and guarded agent skill changes); a read-only audit log; and a read-only inventory of account settings, installed apps, brands, agent roles, tags, and locales.
Destructive and live-routing writes (deletes, and updates to triggers/automations/SLAs/trigger-order) are guarded with a preview-then-confirm step.
Install
Claude Desktop
Open your Claude Desktop config:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add a
zendesk-adminentry undermcpServers:{ "mcpServers": { "zendesk-admin": { "command": "npx", "args": ["-y", "@sniebauer/zendesk-admin-mcp"] } } }Capture credentials (skip if you already ran setup for
@sniebauer/zendesk-mcp— they share the same config file):npx -y @sniebauer/zendesk-admin-mcp setupYou'll be prompted for your Zendesk subdomain, email, and an API token (generate at
https://<your-subdomain>.zendesk.com/admin/apps-integrations/apis/api-tokens). Stored at~/.config/zendesk-mcp/config.json(mode 0600).Restart Claude Desktop.
Claude Code
Same, but the config file is ~/.claude.json.
Related MCP server: zendesk-mcp
Shared credentials
This package reads the same ~/.config/zendesk-mcp/config.json as @sniebauer/zendesk-mcp. Run setup once (from either package) and both servers are authenticated. Env vars (ZENDESK_SUBDOMAIN / ZENDESK_EMAIL / ZENDESK_API_TOKEN) override the file.
Heads up: a Zendesk API token carries your full account permissions. This server can modify live business rules. The
require_confirmguard (below) is the safety net — there is no read-only token scope in Zendesk.
The require_confirm guard
Guarded operations — every delete, every update to triggers / automations / SLA policies / schedules, plus zda_reorder_triggers, zda_set_schedule_hours, zda_set_holidays, and zda_update_agent_skills — do not execute on the first call. Instead they return the object's current state (and, for updates, the proposed change) and ask you to re-invoke with require_confirm: true. This forces a deliberate two-step on anything that can break live ticket flow.
Creates and updates to lower-risk objects (macros, views, groups, fields, forms, webhooks) execute directly.
Tools (73)
Business rules — full CRUD (list / get / create / update / delete each)
zda_*_trigger(s)·zda_*_automation(s)·zda_*_macro(s)·zda_*_view(s)·zda_*_sla_policy/policieszda_reorder_triggers— reorder trigger evaluation precedence (guarded)
Ticketing config — full CRUD
zda_*_group(s)·zda_*_ticket_field(s)·zda_*_ticket_form(s)·zda_*_webhook(s)
Schedules & holidays — full CRUD
zda_*_schedule(s)·zda_*_holiday(s)— holiday tools take aschedule_id;zda_list_holidaysalso acceptsstart_date/end_datefor a server-side filterzda_set_schedule_hours— set weekly business hours with day names andHH:MMinstead of Zendesk's minute offsets (guarded)zda_set_holidays— apply a holiday calendar to several schedules at once; idempotent, skips holidays already present (guarded)
Skills-based routing (Enterprise) — Zendesk's API calls skill types attributes and skills attribute values
zda_list_routing_attributes— skill types with their skills ·zda_get_routing_attribute·zda_list_attribute_valueszda_list_agent_skills— the skills one agent holds, with priorityzda_list_skill_agents— every agent who holds one skillzda_skill_coverage— for each skill an agent holds, who else holds it, thinnest first ("what's thin if they're out?")zda_update_agent_skills— add/remove skills for up to 100 agents at once; leaves unlisted skills and existing priorities alone (guarded)
Audit (read-only, Enterprise)
zda_audit_logs— who changed what, filterable by type/actor/timezda_audit_logs_for_object— all events for one object
Inventory (read-only)
zda_account_settings·zda_list_apps·zda_list_brands·zda_list_agent_roles·zda_list_tags·zda_list_locales
Verify
npm test # unit tests (schemas, error wrapper, guard, URL builders, routing helpers)
npm run smoke # reads-only end-to-end (requires credentials)Caveats
Guarded writes need two calls. First call previews; second call with
require_confirm: trueapplies.Audit logs need Zendesk Enterprise. Non-Enterprise accounts get a 403 with a clear message.
Conditions DSL is passthrough. Create/update accept the object's full structure (e.g.
conditions: {all,any}); Zendesk validates semantics.Credentials precedence. Env vars override the shared config file.
Smoke test is reads-only. It never creates or deletes config.
Business hours are plan-gated. Schedules need a Zendesk plan that includes business hours; accounts without one get a clear message rather than a bare 403.
Skills-based routing is plan- and permission-gated. It needs Zendesk Enterprise, and the caller must be an admin or hold a custom role that can manage skills; otherwise you get a clear message rather than a bare 403.
zda_list_skill_agentsandzda_skill_coverageuse an undocumented endpoint.GET /routing/attributes/{id}/values/{value_id}/agentsbacks the admin "Agents with skill" panel but isn't in the public API reference, so it carries no stability guarantee. Coverage fails soft per skill if it ever stops answering.Skill changes run as a background job.
zda_update_agent_skillswaits up to ~10s per job and returns the job status; a job stillworkingafter that hasn't failed, it just hasn't finished.Routing data has no region, timezone, or group. Coverage returns holder identities only — join location yourself (or model it as a skill type).
Schedule hours can't be set at create time. Zendesk accepts only
nameandtime_zoneon create — usezda_set_schedule_hoursafterward.
License
MIT — see LICENSE.
Available Tools
54 toolszda_account_settingsA
Read the Zendesk account settings (branding, tickets, agents, etc.). Read-only.
Inputs: no named parameters.
zda_audit_logsA
Read the Zendesk audit log (who changed what, when). Filter by source_type, actor_id, and time window. Read-only. Requires Zendesk Enterprise. Use this to verify a change landed or to detect config drift.
Inputs: actor_id, source_type, created_after, created_before.
zda_audit_logs_for_objectA
Read all audit-log events for a specific object (by source_type + source_id). Read-only. Requires Zendesk Enterprise. The natural 'did my change land / what happened to this trigger' lookup.
Inputs: source_id (required), source_type (required).
zda_create_automationC
Create a new Zendesk automation. Common fields: title, conditions {all,any}, actions, active. Automations are time-based.
Inputs: data (required).
zda_create_groupA
Create a new Zendesk group. Common fields: name, description, default, is_public.
Inputs: data (required).
zda_create_macroB
Create a new Zendesk macro. Common fields: title, actions, active, restriction.
Inputs: data (required).
zda_create_sla_policyA
Create a new Zendesk sla_policy. Common fields: title, description, filter {all,any}, policy_metrics (priority/metric/target/business_hours).
Inputs: data (required).
zda_create_ticket_fieldA
Create a new Zendesk ticket_field. Common fields: type, title, description, required, active, custom_field_options (for dropdowns).
Inputs: data (required).
zda_create_ticket_formA
Create a new Zendesk ticket_form. Common fields: name, display_name, ticket_field_ids (ordered), active, end_user_visible.
Inputs: data (required).
zda_create_triggerB
Create a new Zendesk trigger. Common fields: title, conditions {all,any}, actions, active, category_id.
Inputs: data (required).
zda_create_viewA
Create a new Zendesk view. Common fields: title, conditions {all,any}, execution (columns/sorting), active, restriction.
Inputs: data (required).
zda_create_webhookB
Create a new Zendesk webhook. Common fields: name, endpoint, http_method, request_format, status, subscriptions, authentication.
Inputs: data (required).
zda_delete_automationA
Delete a Zendesk automation. GUARDED: call without require_confirm to preview the object that would be deleted; re-call with require_confirm: true to apply.
Inputs: id (required), require_confirm.
zda_delete_groupA
Delete a Zendesk group. GUARDED: call without require_confirm to preview the object that would be deleted; re-call with require_confirm: true to apply.
Inputs: id (required), require_confirm.
zda_delete_macroA
Delete a Zendesk macro. GUARDED: call without require_confirm to preview the object that would be deleted; re-call with require_confirm: true to apply.
Inputs: id (required), require_confirm.
zda_delete_sla_policyA
Delete a Zendesk sla_policy. GUARDED: call without require_confirm to preview the object that would be deleted; re-call with require_confirm: true to apply.
Inputs: id (required), require_confirm.
zda_delete_ticket_fieldA
Delete a Zendesk ticket_field. GUARDED: call without require_confirm to preview the object that would be deleted; re-call with require_confirm: true to apply.
Inputs: id (required), require_confirm.
zda_delete_ticket_formA
Delete a Zendesk ticket_form. GUARDED: call without require_confirm to preview the object that would be deleted; re-call with require_confirm: true to apply.
Inputs: id (required), require_confirm.
zda_delete_triggerA
Delete a Zendesk trigger. GUARDED: call without require_confirm to preview the object that would be deleted; re-call with require_confirm: true to apply.
Inputs: id (required), require_confirm.
zda_delete_viewA
Delete a Zendesk view. GUARDED: call without require_confirm to preview the object that would be deleted; re-call with require_confirm: true to apply.
Inputs: id (required), require_confirm.
zda_delete_webhookA
Delete a Zendesk webhook. GUARDED: call without require_confirm to preview the object that would be deleted; re-call with require_confirm: true to apply.
Inputs: id (required), require_confirm.
zda_get_automationA
Fetch a single Zendesk automation by ID, including its full definition.
Inputs: id (required).
zda_get_groupA
Fetch a single Zendesk group by ID, including its full definition.
Inputs: id (required).
zda_get_macroA
Fetch a single Zendesk macro by ID, including its full definition.
Inputs: id (required).
zda_get_sla_policyA
Fetch a single Zendesk sla_policy by ID, including its full definition.
Inputs: id (required).
zda_get_ticket_fieldB
Fetch a single Zendesk ticket_field by ID, including its full definition.
Inputs: id (required).
zda_get_ticket_formA
Fetch a single Zendesk ticket_form by ID, including its full definition.
Inputs: id (required).
zda_get_triggerA
Fetch a single Zendesk trigger by ID, including its full definition.
Inputs: id (required).
zda_get_viewA
Fetch a single Zendesk view by ID, including its full definition.
Inputs: id (required).
zda_get_webhookA
Fetch a single Zendesk webhook by ID, including its full definition.
Inputs: id (required).
zda_list_agent_rolesA
List the custom agent roles defined on this account (Enterprise). Read-only.
Inputs: no named parameters.
zda_list_appsA
List installed Zendesk Marketplace apps (installations) and their settings. Read-only.
Inputs: no named parameters.
zda_list_automationsB
List all Zendesk automations.
Inputs: no named parameters.
zda_list_brandsA
List the brands configured on this Zendesk account. Read-only.
Inputs: no named parameters.
zda_list_groupsA
List all Zendesk groups.
Inputs: no named parameters.
zda_list_localesA
List the locales available/enabled on this account. Read-only.
Inputs: no named parameters.
zda_list_macrosA
List all Zendesk macros.
Inputs: no named parameters.
zda_list_sla_policiesB
List all Zendesk sla_policies.
Inputs: no named parameters.
zda_list_tagsA
List the most-used tags across the account. Read-only.
Inputs: no named parameters.
zda_list_ticket_fieldsA
List all Zendesk ticket_fields.
Inputs: no named parameters.
zda_list_ticket_formsB
List all Zendesk ticket_forms.
Inputs: no named parameters.
zda_list_triggersA
List all Zendesk triggers.
Inputs: no named parameters.
zda_list_viewsA
List all Zendesk views.
Inputs: no named parameters.
zda_list_webhooksA
List all Zendesk webhooks.
Inputs: no named parameters.
zda_reorder_triggersA
Reorder triggers. Trigger order determines evaluation precedence and is a common source of silent routing bugs. GUARDED: call without require_confirm to preview the current order; re-call with require_confirm: true to apply. Provide the COMPLETE ordered list of trigger IDs.
Inputs: trigger_ids (required), require_confirm.
zda_update_automationA
Update an existing Zendesk automation. GUARDED: this object affects live ticket flow. Call without require_confirm to preview the current state; re-call with require_confirm: true to apply. Common fields: title, conditions {all,any}, actions, active. Automations are time-based.
Inputs: id (required), data (required), require_confirm.
zda_update_groupC
Update an existing Zendesk group. Common fields: name, description, default, is_public.
Inputs: id (required), data (required), require_confirm.
zda_update_macroB
Update an existing Zendesk macro. Common fields: title, actions, active, restriction.
Inputs: id (required), data (required), require_confirm.
zda_update_sla_policyA
Update an existing Zendesk sla_policy. GUARDED: this object affects live ticket flow. Call without require_confirm to preview the current state; re-call with require_confirm: true to apply. Common fields: title, description, filter {all,any}, policy_metrics (priority/metric/target/business_hours).
Inputs: id (required), data (required), require_confirm.
zda_update_ticket_fieldB
Update an existing Zendesk ticket_field. Common fields: type, title, description, required, active, custom_field_options (for dropdowns).
Inputs: id (required), data (required), require_confirm.
zda_update_ticket_formA
Update an existing Zendesk ticket_form. Common fields: name, display_name, ticket_field_ids (ordered), active, end_user_visible.
Inputs: id (required), data (required), require_confirm.
zda_update_triggerA
Update an existing Zendesk trigger. GUARDED: this object affects live ticket flow. Call without require_confirm to preview the current state; re-call with require_confirm: true to apply. Common fields: title, conditions {all,any}, actions, active, category_id.
Inputs: id (required), data (required), require_confirm.
zda_update_viewA
Update an existing Zendesk view. Common fields: title, conditions {all,any}, execution (columns/sorting), active, restriction.
Inputs: id (required), data (required), require_confirm.
zda_update_webhookB
Update an existing Zendesk webhook. Common fields: name, endpoint, http_method, request_format, status, subscriptions, authentication.
Inputs: id (required), data (required), require_confirm.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 54 tools
Each tool targets a distinct resource and action (e.g., list, get, create, update, delete for automations, groups, etc.). The only overlapping pair is audit_logs vs audit_logs_for_object, but their descriptions clearly differentiate scope. Agent can reliably select the correct tool.
Most tools follow a consistent 'zda_verb_noun' pattern (e.g., zda_list_automations, zda_create_trigger). However, a few read-only tools are simply noun phrases (zda_account_settings, zda_audit_logs) without a verb, breaking the pattern. Overall, the naming is predictable with minor deviations.
With 54 tools, this is a large surface area for a single server. While each tool covers a distinct admin operation (CRUD for 9 object types plus read-only tools), the count is on the higher end. It may overwhelm agents but is justifiable for a comprehensive admin interface.
The toolset provides full CRUD coverage for major Zendesk admin objects (automations, triggers, views, etc.) and includes key read-only resources (audit logs, brands, locales). Missing operations like creating agent roles or managing custom role definitions are minor gaps, but the core admin workflow is well-covered.
Maintenance
Related MCP Connectors
Zendesk configuration management for AI agents: propose, review, apply and roll back changes.
Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets.
Read tickets, contacts, companies, agents and groups; create, update and reply to tickets.
Manage Chili Piper scheduling links, meetings, routing rules, and teams. Admin only. Experimental.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search tickets, manage tags, create tickets, inspect automations, and more in Zendesk.MIT
- AlicenseAqualityDmaintenanceConnects AI assistants to your Zendesk account with 14 curated tools for managing tickets, users, organizations, and help center articles, running locally with no third-party services.14MIT
- AlicenseNot gradedqualityDmaintenanceComprehensive MCP server providing 89 tools and 13 React UI apps for complete Zendesk Support API integration, enabling ticket, user, organization, and automation management.MIT
- AlicenseAqualityCmaintenanceEnables Zendesk admins to audit business rules, monitor backlog and SLAs, review security, and manage user offboarding through natural language.132MIT