Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.michaelrice/zendesk-mcp

PYPI · ZENDESK-MCP

Zendesk MCP server for Claude Code and other MCP clients

Available components

+4 this week 74 Trust /100

Last scanned (59 minutes ago)

Scores higher than 70% of PyPI servers

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 47 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to michaelrice/zendesk-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 27 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1807 tokens (~62/item across 29 items; 29 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "zendesk_remove_tag" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 3 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 1 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 30 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 28 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
  • 27 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 25 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/zendesk-mcp@0.1.6

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo michaelrice/zendesk-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/michaelrice/zendesk-mcp/.github/workflows/release.yml@refs/tags/v0.1.6
Rekor log index 3151416141
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:a2a6555732e342f1d368db4977b0d68dbc453097b05f69645b96855d7d3e78cd

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 47 packages
Packages resolved 47
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 29 exposed · ~1,807 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
zendesk_add_tag ~61

Add a tag to a Zendesk ticket. Idempotent: adding an existing tag returns the current tag list without modifying the ticket. Returns JSON with ticket_id and current tags.

NameTypeReqDescription
tagstringyes–
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_apply_macro ~69

Apply a macro to a Zendesk ticket. Fetches the macro preview, applies field changes, and posts any comment included in the macro. Returns JSON with id, status, tags, applied_changes, comment_added.

NameTypeReqDescription
macro_idintegeryes–
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_assign_ticket ~59

Assign a Zendesk ticket to an agent by their email address. Pass 'me' as assignee_email to assign the ticket to yourself (the authenticated user).

NameTypeReqDescription
assignee_emailstringyes–
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_create_ticket ~122

Create a new Zendesk ticket. subject and description are required. priority: low/normal/high/urgent. type: problem/incident/question/task. requester_id/assignee_id are user IDs (integers). custom_fields is a list of {id, value} dicts. Returns JSON of the created ticket.

NameTypeReqDescription
assignee_id–––
custom_fields–––
descriptionstringyes–
priority–––
requester_id–––
subjectstringyes–
tags–––
type–––
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_download_attachment ~145

Download a Zendesk attachment. Obtain attachment_url and filename from zendesk_list_attachments. ticket_id is required for cache organization. Optional dest_dir overrides the default cache location (it must be inside the cache or a directory listed in 'attachment_allowed_dest_dirs' in the config); the file is written there and (for archives) extracted alongside it. Archives return a file list and unpack_dir — read individual files with your normal file tools. PDFs return up to ~500KB of extracted text. Images are base64-encoded.

NameTypeReqDescription
attachment_urlstringyes–
dest_dir–––
filenamestringyes–
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_get_comments ~43

Get all comments (public replies and internal notes) for a Zendesk ticket. Includes attachment metadata but does not download files.

NameTypeReqDescription
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_get_git_zen_links ~60

Get linked GitLab issues, merge requests, and commits for a Zendesk ticket via the Git-Zen integration. Returns structured lists with state, labels, weight, and direct GitLab links.

NameTypeReqDescription
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_get_group_users ~39

List the members of a Zendesk group. Returns JSON array of {id, name, email}.

NameTypeReqDescription
group_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_get_groups ~29

List all active Zendesk groups (excluding deleted). Returns JSON array of {id, name}.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_get_organization ~49

Fetch a Zendesk organization including its custom fields and tags. Returns JSON with id, name, organization_fields, tags, created_at, updated_at.

NameTypeReqDescription
organization_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_get_ticket ~44

Get a Zendesk ticket by ID. Returns ticket fields including status, priority, requester, assignee, tags, and description.

NameTypeReqDescription
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_get_tickets ~91

List Zendesk tickets with pagination. page: 1-based page number. per_page: max 100. sort_by: created_at, updated_at, priority, or status. sort_order: asc or desc. Returns tickets plus pagination metadata.

NameTypeReqDescription
pageinteger––
per_pageinteger––
sort_bystring––
sort_orderstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_get_time_tracking ~59

Get time tracking data for a Zendesk ticket. Returns total time spent and time spent on the last update, in both seconds and human-readable format (e.g. '2h 15m').

NameTypeReqDescription
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_get_view ~45

Get a Zendesk view's definition including filter conditions and execution settings. Returns JSON with id, title, active, conditions, execution.

NameTypeReqDescription
view_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_get_view_tickets ~39

Get the tickets currently matching a Zendesk view. Returns JSON array of tickets with essential fields.

NameTypeReqDescription
view_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_list_attachments ~55

List all attachments across all comments for a Zendesk ticket. Returns filename, content type, size, and download URL for each. Use zendesk_download_attachment to fetch file contents.

NameTypeReqDescription
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_list_custom_statuses ~55

List all custom ticket statuses defined in Zendesk. Returns JSON array of {id, agent_label, end_user_label, status_category, active, default}. Use the id when setting custom_status_id on a ticket.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_list_macros ~41

List all active Zendesk macros with their actions. Returns JSON array of {id, title, description, actions: [{field, value}]}.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_list_views ~26

List all active Zendesk views. Returns JSON array of {id, title}.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_log_time ~62

Log time spent on a Zendesk ticket. Adds seconds to the running total and records it as the last-update time. Returns logged amount and new total in seconds and human-readable format.

NameTypeReqDescription
secondsintegeryes–
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_post_comment ~49

Post a public reply on a Zendesk ticket. The reply is visible to the requester. Use for customer-facing responses.

NameTypeReqDescription
bodystringyes–
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_post_internal_note ~51

Post an internal note on a Zendesk ticket. Internal notes are only visible to agents and are not sent to the requester.

NameTypeReqDescription
bodystringyes–
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_preview_macro ~42

Preview the effect a macro would have (without applying it). Returns the result payload from Zendesk's apply preview endpoint.

NameTypeReqDescription
macro_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_remove_tag ~63

Remove a tag from a Zendesk ticket. Idempotent: removing a tag that isn't present returns the current tag list without modifying the ticket. Returns JSON with ticket_id and current tags.

NameTypeReqDescription
tagstringyes–
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_search_tickets ~91

Search Zendesk tickets by keyword and/or status. keywords: free-text search (e.g. 'login failure LDAP'). status: new, open, pending, hold, solved, closed — leave empty for all statuses. Returns id, subject, status, requester, assignee, and dates.

NameTypeReqDescription
keywordsstring––
limitinteger––
statusstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_search_users ~39

Search Zendesk users by name or email. Returns JSON array of {id, name, email, role}.

NameTypeReqDescription
querystringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_set_ticket_status ~50

Set the status of a Zendesk ticket. Valid statuses: new, open, pending, hold, solved, closed.

NameTypeReqDescription
statusstringyes–
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_ticket_to_gitlab_context ~66

Format a Zendesk ticket and its comments as an issue draft. Returns Markdown with ticket metadata, full conversation, and an empty Steps to Reproduce section. Use this output as the description when creating an issue in your tracker.

NameTypeReqDescription
ticket_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

zendesk_update_ticket ~163

Update one or more fields on a Zendesk ticket. Pass only the fields you want to change. status: new/open/pending/hold/solved/closed. priority: low/normal/high/urgent. type: problem/incident/question/task. assignee_id, requester_id, group_id, custom_status_id are integer IDs. due_at is ISO8601. Returns JSON of the refreshed ticket.

NameTypeReqDescription
assignee_id–––
custom_fields–––
custom_status_id–––
due_at–––
group_id–––
priority–––
requester_id–––
status–––
subject–––
tags–––
ticket_idintegeryes–
type–––
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the io.github.michaelrice/zendesk-mcp server?

io.github.michaelrice/zendesk-mcp runs locally as a PyPI package, launched with uvx zendesk-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · zendesk-mcp

# add to Claude Code
claude mcp add michaelrice-zendesk-mcp -- uvx zendesk-mcp
Common questions

What is the io.github.michaelrice/zendesk-mcp server?

io.github.michaelrice/zendesk-mcp is listed in the public MCP registry as io.github.michaelrice/zendesk-mcp. Zendesk MCP server for Claude Code and other MCP clients. This page covers its PyPI package (zendesk-mcp).

Is the io.github.michaelrice/zendesk-mcp server safe to use?

io.github.michaelrice/zendesk-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.michaelrice/zendesk-mcp server expose?

io.github.michaelrice/zendesk-mcp exposes 29 tools: zendesk_get_ticket, zendesk_search_tickets, zendesk_get_comments, zendesk_list_attachments, zendesk_download_attachment, and 24 more. Their descriptions and schemas cost roughly 1,807 tokens of context every time the server is loaded.

Is the io.github.michaelrice/zendesk-mcp server still maintained?

io.github.michaelrice/zendesk-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.michaelrice/zendesk-mcp server under?

io.github.michaelrice/zendesk-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.