Zendesk MCP Server: Tools, Setup, and Governing Customer-Visible Writes

A Model Context Protocol server that exposes Zendesk Support as tools an AI agent can call, covering support tickets, users, organizations, and related support data. On TrueFoundry it registers as a remote OAuth2 MCP server using a Zendesk OAuth client you create in Admin Center, so each user authorizes their own account.

Tools across support tickets, users, organizations, and related support data. Exact names depend on the implementation you deploy. Once connected, the full list appears on the Tools tab, where each can be enabled, disabled, re-described, or annotated.

Create a confidential OAuth client in Zendesk with TrueFoundry’s callback as the redirect URL and register the server through Connect any Remote MCP Server with OAuth2 Authorization Code. Then do three things: mark ticket-write tools Destructive and gate them with an approval policy set to Once, turn off Enable new tools by default, and attach PII/PHI Detection on the MCP Post Tool hook.

Yes. TrueFoundry runs in your VPC, on-prem, air-gapped, or hybrid, so prompts and responses never leave your domain even as you route across many providers.

Yes. It includes an MCP Gateway, an Agent Gateway, and an MCP & Agents Registry with tool-level access control. Agents on LangGraph, CrewAI, AutoGen, or a custom framework can all be governed centrally.

Ja. Das Gateway ist OpenTelemetry-kompatibel und lässt sich in Grafana, Datadog, Prometheus oder Ihren bevorzugten Stack integrieren. Es verfolgt jede Anfrage vom Prompt bis zur Ausführung von Tools und Modellen, sodass Sie eine einheitliche Protokollierung erhalten, ohne Ihre bestehenden Systeme entfernen zu müssen.