MCP connectors

To connect any of these, open the in-app Connections settings.

Dispatch speaks the Model Context Protocol (MCP), an open standard for exposing an app's tools to an agent. When you connect an MCP server, Dispatch discovers the tools that server publishes and makes them available to the agent. There are two ways to connect: a pre-configured integration where Dispatch already knows the server, or a custom server you point Dispatch at yourself.

Pre-configured MCP integrations

These connect with one click from the Connections settings. Dispatch already holds the server address, so you only authorize access.

• Notion: read and update pages and databases in Notion.
• Linear: track issues and projects in Linear.
• Asana: track tasks and projects in Asana.
• Monday.com: manage boards, items, and workflows in Monday.com.
• Quo: work with Quo communications.
• JustCall: manage calls and SMS in JustCall.
• HighLevel: manage leads and automations in HighLevel. HighLevel authenticates with a Private Integration Token and a location id rather than a sign-in flow, so you paste those in when connecting.
• ActiveCampaign: manage contacts and automations in ActiveCampaign. ActiveCampaign does not have a shared server address, so you supply your own MCP URL from your ActiveCampaign account settings.

Custom MCP servers

You can connect any MCP server, not just the ones above. From the Connections settings, add a server with:

• A name (used to label its tools).
• The server URL.
• Optional authentication: a bearer token and custom headers, or an OAuth sign-in flow if the server supports it.

Once connected, Dispatch discovers the server's tools and any resources it publishes, and the agent can use them by name. You can enable, disable, edit, or remove a custom server at any time.

What automations can use

• Scheduled actions that read or write through an MCP server's tools.
• Trigger automations using the same dispatched-from-event model as other automations.

Limits and behavior

• Tools are discovered at run time. When a connection is active, Dispatch fetches the server's tool list during agent setup. Tools the server does not publish are not available.
• Writes are not gated. Unlike native connectors (Gmail, Calendar, Slack), MCP tools do not currently route through the permission gate. Treat MCP writes with the same care you would the underlying app's API.
• The server controls capabilities. What Dispatch can read or write depends entirely on the tools the MCP server exposes and the access its credentials grant.
• One connection per server. Each MCP server you add is a separate connection with its own credentials.

Related

• Integrations: the full list of apps Dispatch connects to.
• Composio: another way to reach third-party apps, brokered through Composio.
• Permission gate: how native connector writes are gated.