Connect
Optimize
Secure
MCP Gateway
MCP Gateway
for Zendesk AI Agents
One MCP gateway to connect Zendesk to 310+ enterprise SaaS apps. No auth hassle. Token-efficient by design. Security and governance built-in.
What is an MCP gateway?
An MCP gateway (also called an MCP aggregator) is a single endpoint that connects an AI agent to multiple
MCP servers via the open Model Context Protocol (opens in new tab).
Some gateways act as proxies, routing traffic to MCP servers customers operate themselves. Others provide the
underlying MCP servers as a managed service.
StackOne is the managed kind. We provide pre-built MCP servers for 310+ enterprise SaaS apps,
including ones with no official MCP server today. For each app you connect, StackOne provides the MCP protocol
layer, the SaaS API integration, action coverage, and the auth orchestration framework. Authentication is
configured per app per organization — your team registers OAuth credentials with the SaaS provider, links them
in StackOne, and end users then authorize access through that flow. Once set up, the agent reaches every
connected app through one URL, with token storage, refresh, and per-user scoping handled by StackOne.
StackOne's MCP gateway — SOC2, HIPAA, CCPA, and GDPR compliant — bundles 310+ pre-built SaaS integrations exposing 20,000+ actions, all reachable from your Zendesk AI agent through one URL.
Act across all your apps
from inside Zendesk
One MCP gateway, every enterprise SaaS your Zendesk AI agent
could ever need to act on.
Coverage
310+ connectors.
20,000+ tested actions.
Every action is built and maintained by StackOne, tested against the live API, and updated when vendors change their endpoints.
Browse all connectors
Trust
Auth & governance,
simplified.
StackOne handles OAuth, API keys, refresh, and scopes for every connector, giving enterprise IT full control through auth configs in a multi-tenant setup.
Agent Auth
Performance
Agent context window,
managed.
Tool Discovery and Code Mode keep the Zendesk AI agent's context lean — only relevant actions, no raw response noise. Sharper agents, lower token costs.
Tools Discovery
Security
Agent security,
built in.
Defender scans every MCP tool response for prompt injection in real time. Up to 97.44%¹ detection, 0.2% false positives. SOC2, HIPAA, CCPA, GDPR compliant.
Prompt Injection Defense¹ Jayavibhav test, 65,000 samples.
Connect Zendesk AI agents
to more apps in 4 steps
From auth config to first agent tool call in 5 minutes.
1
Connect StackOne via Zendesk's AI MCP Client.
In Admin Center → Apps and integrations → Actions → Custom actions, connect a Custom MCP server with the StackOne gateway URL and a Zendesk Connection for auth. Available where the Zendesk AI MCP Client is enabled in your workspace (Early Access).
Admin Center → Apps and integrations → Actions
Connect MCP server
Name
StackOne
Server URL
https://api.stackone.com/mcp/{...}
Connection (auth)
Bearer token
Save action
2
Connect each SaaS integration in StackOne.
OAuth or API key per app, done once in your dashboard. Tokens stay server-side.
3
Scope agent actions.
Read-only, specific objects, or per-role exposure. Toggle from the StackOne dashboard.
List tickets (enabled)
Get customer (enabled)
Read context (enabled)
Update record (disabled)
Issue refund (disabled)
4
Let your Zendesk AI agent call StackOne in plain English.
StackOne maps the agent's tool call to the right action in the right system. Done.
"Pull this customer's Salesforce account tier and file a Linear bug from this ticket."
salesforce_get_account
Completed
linear_create_issue
Completed
team: Web Platform
priority: high (Enterprise account)
result: WEB-2104 created
Customer is Enterprise tier. Filed Linear bug WEB-2104 and replied in the ticket.
Get Zendesk AI agents
to do more across your stack
Cross-app workflows your Zendesk AI agent now runs in seconds instead of click-throughs.
Customer Context
> Pull Salesforce account tier into a Zendesk ticket before the AI agent responds.
Billing & Payments
> Check this customer's Stripe refund history before approving the ticket.
Engineering & Bug Tracking
> File a Linear bug from this Zendesk ticket and return the ticket ID to the customer.
Knowledge & Internal Comms
> Search internal Notion wikis when the Help Center misses an answer.
Connect any Enterprise AI Agent
to the StackOne MCP Gateway
Same 310+ MCP servers. Same agent context. Pick yours.
Frequently Asked Questions
Zendesk AI agents consume external MCP servers via the Zendesk AI MCP Client (currently in Early Access). When your workspace has access, in Zendesk Admin Center → Apps and integrations → Actions → Custom actions, connect an MCP server with the StackOne gateway URL and an authentication Connection (Bearer token or OAuth 2.0). Once attached to an AI agent or Action Builder flow, 310+ pre-built SaaS connectors are reachable through that single MCP server. The MCP Client feature is rolling out as part of Zendesk's agentic-AI expansion to Suite and Support plans. Read the announcement in the Zendesk AI MCP Client docs.
An MCP gateway (also called an MCP aggregator) is a single endpoint that connects an AI agent to multiple MCP servers via the Model Context Protocol. Some gateways route traffic to MCP servers customers operate themselves; others provide the MCP servers as a managed service. StackOne is the managed kind — we provide pre-built MCP servers for 310+ enterprise SaaS apps, including ones with no official MCP server today. Authentication is configured per app per organization: your team registers OAuth credentials with the SaaS provider, links them in StackOne, and end users authorize access through that flow. Once set up, the agent reaches every connected app through one URL.
Zendesk AI agents can access enterprise SaaS like Salesforce, HubSpot, Attio, Stripe, Chargebee, Linear, Jira, GitHub, Notion, and Confluence through the StackOne MCP gateway — 310+ pre-built connectors in total. StackOne fills the cross-system gap that the existing Zendesk Marketplace (apps, not MCP) doesn't cover yet for AI agents. New connectors ship continuously, and you can build custom ones with AI Integration Builder. See all connectors.
Zendesk's AI MCP Client launched without a curated first-party partner directory (the existing Zendesk Marketplace is traditional app integrations, not MCP-shaped). StackOne fills the day-one gap with 310+ apps reachable through one Custom MCP server registration instead of one per app, auth managed once in the dashboard, and tool definitions loaded only when relevant to the prompt.
Credentials sit at three layers: your StackOne API token (embedded in the gateway URL stored as a Zendesk Connection, controlled by workspace admins), SaaS connector credentials (server-side in your StackOne dashboard), and per-user OAuth or session tokens (server-side, scoped per user). StackOne stores OAuth tokens and API keys, refreshes them automatically, and only exposes the actions you've authorized to the agent.
Skip the StackOne MCP gateway when any of these is true:
- Zendesk's first-party Marketplace apps (built before MCP) already cover your AI agent's cross-system needs
- You only use a handful of actions across a few apps
- You don't need multi-tenancy, per-user permissions, or per-action scoping
- Indirect prompt injection isn't a concern
- Your MCP provider already does tool discovery and server-side execution to keep the agent context lean
Connect All Your Apps to Zendesk.
One MCP gateway, 310+ pre-built SaaS connectors. Set up in 5 minutes.