Solutions

Multi-Brand Support Agency & Client Management E-commerce Support SaaS Customer Support

Developers

Documentation Quickstart Core Concepts API Reference SDK & Open Source
Integrations Pricing Articles
Login Schedule a Demo
Back to Integrations
Claude
Available now

Dispatch Tickets for Claude

Our official connector lets Claude read, triage, update, and reply to your support tickets — directly in the conversation, over the Model Context Protocol.

What it is

The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and data. The Dispatch Tickets MCP connector is a hosted server that exposes your ticketing workspace to Claude as a set of safe, well-described tools.

Once connected, you can ask Claude to work your support queue in plain language. Claude decides which tools to call, runs them against your workspace, and shows you the results — no dashboard-hopping, no copy-paste. Because Dispatch Tickets is API-first and multi-tenant, one connector serves every brand your API key can access.

Server URL

https://mcp.dispatchtickets.com/mcp

What it can do

The connector ships with ten tools, split between reading your tickets and taking action on them.

Read your tickets

list_brands

List the brands (workspaces) your key can access.

list_tickets

List tickets, filtered by status, priority, assignee, or date.

search_tickets

Full-text search across a brand's tickets.

get_ticket

Fetch a single ticket and its details.

list_comments

Read a ticket's comments — public replies and internal notes.

get_ticket_stats

Get ticket counts per status for a brand.

Take action

create_ticket

Open a new ticket in a brand.

update_ticket

Change status, priority, assignee, category, tags, or fields.

add_internal_note

Add a private note for your team. Sends nothing to the customer.

reply_to_customer

Post a public reply that emails the customer.

One tool sends email. reply_to_customer posts a public reply that is emailed to the customer. Everything else is either read-only or internal to your team — add_internal_note sends nothing. Claude asks before it acts, so you stay in control of anything customer-facing.

Example prompts

Once connected, try asking Claude things like:

  • "Show me all open, high-priority tickets in the Acme brand."
  • "What's the ticket backlog look like this week? Break it down by status."
  • "Find the ticket where a customer reported a failed checkout and summarize it."
  • "Draft a reply to ticket 1042 apologizing for the delay and offering a refund — but don't send it yet."
  • "Add an internal note to that ticket flagging it for the billing team."
  • "Create a ticket for a bug a customer just emailed me about."

How to get it

You'll need a Dispatch Tickets account. If you don't have one yet, it's free to start — create an account and add a brand first.

Option 1 — Connect from Claude (recommended)

The easiest path uses OAuth, so you never handle an API key.

  1. In Claude, open Settings → Connectors.
  2. Find Dispatch Tickets in the connector directory, or add it as a custom connector using the server URL above.
  3. Click Connect and sign in with your Dispatch Tickets account.
  4. Authorize the workspace you want Claude to access. That's it — the tools appear in your next conversation.

Option 2 — Custom connector with an API key

Prefer a static key (for Claude Code or a self-managed setup)? Grab an sk_live_… key from API Keys in your Dispatch Tickets dashboard, then add the connector with an Authorization header.

Claude Desktop / Claude.ai: Settings → Connectors → Add custom connector. Use the server URL above and add a header Authorization: Bearer sk_live_….

Claude Code:

Add the connector in Claude Code
claude mcp add --transport http dispatch \
  https://mcp.dispatchtickets.com/mcp \
  --header "Authorization: Bearer sk_live_..."

Then confirm the tools are wired up:

claude mcp list

Security & permissions

  • Scoped to your access. The connector can only touch the brands and tickets your account or API key already has access to — nothing more.
  • Nothing sends silently. The only customer-facing action is reply_to_customer, and Claude surfaces it for your confirmation. Internal notes and all reads never email anyone.
  • Per-request auth. One hosted server serves many tenants; your credentials arrive per request and are never shared across workspaces.
  • Revoke anytime. Disconnect the connector in Claude, or revoke the API key in your dashboard, and access stops immediately.

Other AI hosts

The same MCP server works beyond Claude. Point any MCP-capable host at the server URL:

  • ChatGPT / OpenAI — pass the server URL and header as an MCP tool in the Responses API.
  • n8n — use the MCP Client node.
  • Make — add it as an MCP module.

See the integrations overview for the full list.

Next steps

Quickstart

Create your account and first ticket in minutes.

API Reference

The REST API the connector is built on.