Support Ticket Router

Name: Support Ticket Router
Availability: InStock
Author: Kata Team

Decides where every ticket goes — the right group, an engineering issue, or a product theme.

Customer Service Retail Conversational Support (Chatbots)Returns & Order Management Ticket Routing & Triage Sentiment & Escalation @katateam

Before you connect: what this agent would do

A preview derived from this agent’s definition — not a live run. Nothing runs and no key is sent until you connect. FindAgent runs it on the hosted connection.

Tools it can use (8)

get_ticketRead-only
Fetch a ticket's subject, status, priority, group, requester, tags, and channel.
Reaches: {subdomain}.zendesk.com
Uses your Zendesk API credential.
list_ticket_commentsRead-only
Fetch the full comment thread on a ticket, where the real problem usually appears.
Reaches: {subdomain}.zendesk.com
Uses your Zendesk API credential.
search_jira_issuesRead-only
Search Jira for an existing issue covering the same defect, before opening a new one.
Reaches: {jira_site}.atlassian.net
Uses your Jira Cloud token.
search_sentry_issuesRead-only
Look for a Sentry error matching the symptom, to attach a stack trace to the report.
Reaches: sentry.io
Uses your Sentry auth token.
update_ticket_fieldsCan change data
Set a ticket's group, priority, and type so the SLA policy and the queue can act on it.
Reaches: {subdomain}.zendesk.com
Uses your Zendesk API credential.
add_internal_noteCan change data
Record the classification and the evidence behind it as a private note on the ticket.
Reaches: {subdomain}.zendesk.com
Uses your Zendesk API credential.
create_jira_issueCan change data
Open an engineering issue for a confirmed defect, carrying reproduction detail and the Sentry link.
Reaches: {jira_site}.atlassian.net
Uses your Jira Cloud token.
link_ticket_to_issueCan change data
Tag the ticket with an existing issue key so repeat reports accumulate on one issue instead of many.
Reaches: {subdomain}.zendesk.com
Uses your Zendesk API credential.

Credentials it will ask for (3)

Zendesk API credential
Only ever sent to: zendesk.com
Format: Paste the Base64 encoding of “id:token” (e.g. your email and API token joined by a colon), not the raw token. Many tools show this ready-made as your “Basic auth” value.
Jira Cloud token
Only ever sent to: atlassian.net
Format: Paste the Base64 encoding of “id:token” (e.g. your email and API token joined by a colon), not the raw token. Many tools show this ready-made as your “Basic auth” value.
Sentry auth token· optional
Only ever sent to: sentry.io

Safety rails that guard it

Every result is scanned for leaked secrets and prompt-injection before it reaches you — a check no agent can turn off.
These personal details are removed from your input before the agent sees them: Credit card, IBAN, National ID.
These personal details are stripped from the agent’s results before you see them: Email, Phone.
A request larger than 80,000 characters is rejected before it runs.
get_ticketRate limited to 300/hour.Safe to retry automatically if a run is interrupted.
add_internal_noteRate limited to 200/hour.
create_jira_issueSensitive — it is flagged and needs an explicit confirmation before it runs.Rate limited to 20/hour.Runs only after search_jira_issues has run first.
search_jira_issuesRate limited to 240/hour.Safe to retry automatically if a run is interrupted.
link_ticket_to_issueRate limited to 200/hour.Safe to retry automatically if a run is interrupted.
list_ticket_commentsRate limited to 300/hour.Safe to retry automatically if a run is interrupted.
search_sentry_issuesRate limited to 240/hour.Safe to retry automatically if a run is interrupted.
update_ticket_fieldsRate limited to 200/hour.Safe to retry automatically if a run is interrupted.

How FindAgent keeps agents safe

Run locally

This MCP server runs on your own machine — FindAgent only points you at it. Run the command below, then add it to your MCP client. Nothing is hosted or proxied on our side.

terminal

npx -y @findagent/mcp run

Add it to your MCP client

Paste this into your client config (e.g. claude_desktop_config.json or a Cursor mcp.json), then restart the client.

mcp client config

{
  "mcpServers": {
    "support-ticket-router": {
      "command": "npx",
      "args": [
        "-y",
        "@findagent/mcp",
        "run"
      ]
    }
  }
}

What you'll need — and where to get it

This agent will ask you for the following. You enter them when you connect — they're encrypted and never shared with the creator.

Zendesk API credential
Base64 of 'your-agent-email/token:YOUR_API_TOKEN' — encode it yourself before pasting; the runtime only adds the Basic prefix. Create the token under Admin Center > Apps and integrations > Zendesk API. Needs ticket read, ticket field update, and internal comments. It does not need permission to post public replies, and should not have it.
Get this from zendesk.com's account or API settings.
Paste the value as a single line.
Only sent to: zendesk.com
Jira Cloud token
Base64 of 'your-email:your-api-token' — encode it yourself before pasting; the runtime only adds the Basic prefix. Create the token at id.atlassian.com/manage-profile/security/api-tokens. Needs Browse Projects and Create Issues on the engineering project.
Get this from atlassian.net's account or API settings.
Paste the value as a single line.
Only sent to: atlassian.net
Sentry auth token · optional
A Sentry auth token with project:read and event:read. Optional — without it the agent still routes and escalates, it just cannot attach a stack trace to a defect report.
Get this from sentry.io's account or API settings.
Paste the value as a single line.
Only sent to: sentry.io

Requirements

This server requires authentication — see the description for how to get a key.

Get this agent

Free

Add the hosted gateway to Claude, ChatGPT, Cursor or any MCP client. Nothing installs on your machine.

https://mcp.findagent.cloud/agents/support-ticket-router

View setup

What we can prove

Ships no executable code. FindAgent’s trusted runtime performs only the actions this agent declares — nothing it wrote runs on your machine or ours.
Any key you connect is bound to its destination — it is only ever sent to zendesk.com, atlassian.net, sentry.io, and is dropped if a request tries to redirect it elsewhere.
Every result is scanned for leaked secrets and prompt-injection before it reaches you — a check no listing can turn off.
Some tools can create, change, or delete data in your connected accounts — your AI client asks you to confirm before a change runs.
Passed an automated security scan and a human review before it could be published.

These are facts derived from the manifest, not a score and not a badge.

Agent details