Responded16 / 22 checks passed
Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Independent monitoring
Health & checks
Outdated check
Last connection measurement is over 24 hours old. Current availability is unknown.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Inspect individual checks 22 recorded
Core
- Pass
- Pass
- Pass
- Pass
- Pass
Performance
- Not measured
- Not measured
- Not measured
- Not measured
Access
- Pass
- Not measured
- Not measured
Tools
- Pass
- Pass
- Pass
- Pass
Publisher
- Pass
- Pass
- Pass
- Not measured
- Pass
- Not measured
Start using Zendesk MCP by usefulapi
Connect to this server
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http zendesk-mcp-by-usefulapi https://zendesk.usefulapi.io/mcpCapabilities
Tools 19
zendesk_add_ticket_comment
MUTATING: 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.
Discoveredzendesk_create_ticket
MUTATING: create a new support ticket. `subject` and `comment_body` are required; the comment becomes the ticket's first message. Zendesk REST: POST /tickets.json.
Discoveredzendesk_current_user
Return the currently authenticated user — a quick way to verify credentials and subdomain. Zendesk REST: GET /users/me.json.
Discoveredzendesk_execute_view
Run a saved view by id and return the matching tickets. Zendesk REST: GET /views/{id}/execute.json.
Discoveredzendesk_get_organization
Fetch a single organization by id. Zendesk REST: GET /organizations/{id}.json.
Discoveredzendesk_get_ticket
Fetch a single ticket by id. Zendesk REST: GET /tickets/{id}.json.
Discoveredzendesk_get_ticket_metrics
Fetch SLA / response / resolution time metrics for a ticket. Zendesk REST: GET /tickets/{id}/metrics.json.
Discoveredzendesk_get_user
Fetch a single user by id. Zendesk REST: GET /users/{id}.json.
Discoveredzendesk_list_groups
List agent groups. Zendesk REST: GET /groups.json.
Discoveredzendesk_list_macros
List macros (reusable sets of ticket actions/replies agents apply). Zendesk REST: GET /macros.json.
Discoveredzendesk_list_organizations
List organizations (offset pagination). Zendesk REST: GET /organizations.json.
Discoveredzendesk_list_satisfaction_ratings
List customer satisfaction (CSAT) ratings, optionally filtered by score. Zendesk REST: GET /satisfaction_ratings.json.
Discoveredzendesk_list_ticket_comments
List the comments (public replies and internal notes) on a ticket, oldest first. Zendesk REST: GET /tickets/{id}/comments.json.
Discoveredzendesk_list_ticket_fields
List all standard and custom ticket fields — useful for discovering field ids/values before creating or updating tickets. Zendesk REST: GET /ticket_fields.json.
Discoveredzendesk_list_tickets
List recent tickets (offset pagination). Zendesk REST: GET /tickets.json.
Discoveredzendesk_list_views
List saved ticket views (curated ticket lists). Use zendesk_execute_view to run one. Zendesk REST: GET /views.json.
Discoveredzendesk_search
Unified 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.
Discoveredzendesk_search_users
Find users by name, email, phone, or other attributes. Zendesk REST: GET /users/search.json.
Discoveredzendesk_update_ticket
MUTATING: 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.
DiscoveredRecent measurements
Probe history
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 57 ms | 19 |