zendesk

Tools

19 tools: 16 read-only, 0 change data, 3 high risk (delete, pay, send or run code).

No tool name points to sending messages.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 3,419 tokens of tool definitions and a 739 ms handshake.

• high riskzendesk_create_ticketMUTATING: create a new support ticket. `subject` and `comment_body` are required; the comment becomes the ticket's first message. Zendesk REST: POST /tickets.json.
• high riskzendesk_update_ticketMUTATING: update an existing ticket. Provide the ticket `id` plus at least one field to change (status, priority, assignee_id, group_id, type, tags, or a comment). Zendesk REST: PUT /tickets/{id}.json.
• high riskzendesk_add_ticket_commentMUTATING: add a comment to a ticket. `public` defaults to true (a reply visible to the requester); set it false for an internal agent note. Convenience over PUT /tickets/{id}.json.
• read-onlyzendesk_searchUnified search across tickets, users, organizations and groups using Zendesk search syntax. Examples: `type:ticket status:open`, `type:user email:jane@acme.com`, `type:organization name:acme`. Zendesk REST: GET /search.json.
• read-onlyzendesk_list_ticketsList recent tickets (offset pagination). Zendesk REST: GET /tickets.json.
• read-onlyzendesk_get_ticketFetch a single ticket by id. Zendesk REST: GET /tickets/{id}.json.
• read-onlyzendesk_list_ticket_commentsList the comments (public replies and internal notes) on a ticket, oldest first. Zendesk REST: GET /tickets/{id}/comments.json.
• read-onlyzendesk_current_userReturn the currently authenticated user - a quick way to verify credentials and subdomain. Zendesk REST: GET /users/me.json.
• read-onlyzendesk_get_userFetch a single user by id. Zendesk REST: GET /users/{id}.json.
• read-onlyzendesk_search_usersFind users by name, email, phone, or other attributes. Zendesk REST: GET /users/search.json.
• read-onlyzendesk_list_organizationsList organizations (offset pagination). Zendesk REST: GET /organizations.json.
• read-onlyzendesk_get_organizationFetch a single organization by id. Zendesk REST: GET /organizations/{id}.json.
• read-onlyzendesk_list_groupsList agent groups. Zendesk REST: GET /groups.json.
• read-onlyzendesk_list_viewsList saved ticket views (curated ticket lists). Use zendesk_execute_view to run one. Zendesk REST: GET /views.json.
• read-onlyzendesk_execute_viewRun a saved view by id and return the matching tickets. Zendesk REST: GET /views/{id}/execute.json.
• read-onlyzendesk_list_macrosList macros (reusable sets of ticket actions/replies agents apply). Zendesk REST: GET /macros.json.
• read-onlyzendesk_list_ticket_fieldsList all standard and custom ticket fields - useful for discovering field ids/values before creating or updating tickets. Zendesk REST: GET /ticket_fields.json.
• read-onlyzendesk_get_ticket_metricsFetch SLA / response / resolution time metrics for a ticket. Zendesk REST: GET /tickets/{id}/metrics.json.
• read-onlyzendesk_list_satisfaction_ratingsList customer satisfaction (CSAT) ratings, optionally filtered by score. Zendesk REST: GET /satisfaction_ratings.json.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-05, 739 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-062026-10-05

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Marketing, email and messaging, ranked by days answering.

What agents looked for

This week agents asked 7Maps for marketing, email and messaging servers 1 time; this server was shown 0 times and picked 0 times.

Owners see the keywords, the servers picked instead, failure reasons and a comparison with similar servers in Owner Insights.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/zendesk.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/zendesk.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=zendesk.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/zendesk.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/zendesk.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=zendesk.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.