Available now

Dispatch Tickets for Make

Let your Make (formerly Integromat) AI-agent scenarios work your support queue — read, triage, create, update, and reply to tickets, over the Model Context Protocol.

What it is

Make can talk to Dispatch Tickets over the Model Context Protocol (MCP) — an open standard for connecting AI assistants and automation platforms to external tools. Our hosted MCP server exposes your ticketing workspace as a set of safe, well-described tools that Make's AI agents can call.

There's nothing to install and nothing to publish. You point Make's MCP client module at our server URL, authenticate with a Dispatch Tickets API key, and the ticketing tools become available to your agent. Because the key is multi-tenant, one connection can reach every brand it has access to.

Server URL

https://mcp.dispatchtickets.com/mcp

Transport: Streamable HTTP · Auth: Authorization: Bearer sk_live_…

What it can do

The server 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. In automated flows, gate reply_to_customer behind a human-approval step if you don't want the agent emailing customers on its own.

What to build

A few things teams wire up with Make and Dispatch Tickets:

Route inbound: when a ticket is created, have the agent classify it and update its category and priority.
Enrich and note: look up a customer in another system and add an internal note with the context.
Escalation watch: on a schedule, check ticket stats and open a task in your PM tool when a backlog threshold is crossed.
Omnichannel intake: turn a new email, form entry, or chat message from anywhere in Make into a Dispatch ticket.

How to connect

You'll need a Dispatch Tickets account and an API key. If you don't have one yet, it's free to start — create an account, add a brand, then grab a key from API Keys in your dashboard.

Make consumes MCP inside its AI-agent flows. A standalone Make app with individual REST modules (for non-agent scenarios) is on our roadmap — until then, the MCP client is the way in.

Create or open a scenario that uses Make's AI agent (Agents).
Add the MCP client to the agent as a tools source.
Set the server URL to the address below and the transport to HTTP streaming.
Add an Authorization header with the value Bearer sk_live_… (your Dispatch Tickets API key).
Pick the tools the agent may call, then run the scenario — the ticketing tools are now wired in.

Server URL

https://mcp.dispatchtickets.com/mcp

Security & permissions

Scoped to your key. The connection can only touch the brands and tickets your API key already has access to — nothing more.
Nothing sends silently. The only customer-facing action is reply_to_customer. In automated flows, put a human-approval step in front of it if you want the final say.
Per-request auth. One hosted server serves many tenants; your key travels with each request and is never shared across workspaces.
Revoke anytime. Remove the credential in Make, or revoke the API key in your dashboard, and access stops immediately.

Other hosts

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

Claude — Desktop, Claude.ai, and Claude Code — our featured connector.
ChatGPT / OpenAI — Pass the server URL and header as an MCP tool in the Responses API.
n8n — MCP Client Tool node inside an AI Agent workflow.