How to leverage Batch connectivity via MCP?

MCP (Model Context Protocol) is a commonly used protocol to connect LLMs to solutions. It lets you connect an assistant, such as Claude or ChatGPT, to your Batch Dashboard.

What you can ask your assistant to do

An MCP wraps whatever part of the Batch API you choose to expose. Most teams start with reporting and data lookups, then add campaign management on top.

Depending on how yours is set up, that can include:

• Getting the list of your orchestrations (campaigns, automations, triggers, in-app messages), filtered by status, channel, or type.
• Getting the performance of an orchestration — sent, delivered, open, click, conversion, revenue — over a given period.
• Looking up your segments, audiences, or catalogs.
• Requesting an export of profile attributes, events, or reachability data.
• Creating, updating, or deleting a campaign.

It's up to you which endpoints you expose — the assistant can only do what your MCP setup allows it to do, nothing more.

Best practices to keep in mind

Here are a few best practices:

• Keeping campaign creation and edits limited to drafts, so a human still opens the campaign on the dashboard to check and launch it.
• Deleting a campaign, on the other hand, takes effect immediately and can't be undone, so it deserves the same care as on the dashboard.
• The same permissions and rate limits as the Batch API still apply.

How to set it up?

It is fairly easy for a technical persona to embed APIs of a solution into an MCP. A lot of Batch customers moved toward this usage.

It can be setup locally on Batch user's desktops or server side.

Batch team can support you in this effort to create an MCP leveraging Batch. You can reach your CSM to know more.