Use Vero with AI - Vero Help Documentation

Vero’s Model Context Protocol (MCP) server connects your broadcasts and journeys to AI assistants like Notion, ChatGPT and Claude Code, so you can create, review, and manage campaigns in natural language instead of clicking through the UI or writing API calls by hand.

The Vero MCP server is in early access. Contact us for access. The tools listed below reflect what’s shipped to date. Please get in touch to share which tools you’d like to see next: we’ll be prioritising releases based on requests.

Why MCP

One integration, many assistants. MCP is an open standard: connect once and use Vero from any MCP-compatible client, not just the ones we document here.
Your data stays in Vero. The server calls the same Campaigns API that powers the dashboard, so nothing about your account changes: it’s just a new way to manage it.
Built for the workflows you already have. Ask your assistant to draft a broadcast, check a journey’s status, or list what’s scheduled this week, in plain language.

Server

The Vero MCP server is available at:

https://mcp.getvero.com/mcp

It authenticates with a Bearer token: the same API secret key used for the Campaigns API. See Authentication for how to generate one.

We previously supported https://api.getvero.com/mcp. This is backwards-compatible for MCP integrations using an API secret key. Integrations using OAuth must use https://mcp.getvero.com/mcp.

Available tools

The MCP server wraps the same Campaigns API endpoints that power broadcasts and journeys in the dashboard.

Read tools

Tool	What it does
`journey_list`	Lists the journeys in your project.
`journey_get`	Retrieves a single journey, including its graph of triggers, nodes and edges. Per-node message details are available on request but are omitted for large journeys with more than 100 messaging nodes: use `journey_message_list` to page through message metadata in that case.
`journey_message_list`	Lists all message nodes within a journey. Results are paginated.
`journey_message_get`	Reads a single message in a journey.
`journey_content_list`	Lists active localized content records for a journey message.
`journey_content_get`	Reads one localized content record for a journey message, including the message body.
`journey_metrics_get`	Returns lifetime Journey funnel counters plus aggregate per-message engagement metrics. See Journey metrics for inputs and response details.
`broadcast_list`	Lists broadcasts in your project, newest first.
`broadcast_get`	Returns a single broadcast.
`broadcast_message_list`	Lists a broadcast’s messages (A/B test arms).
`broadcast_message_get`	Reads one message (A/B test arm) of a broadcast.
`broadcast_content_list`	Lists active localized content records for a broadcast message.
`broadcast_content_get`	Reads one localized content record for a broadcast message, including the message body.
`broadcast_metrics_get`	Returns delivery and engagement metrics for up to 100 broadcasts. See Broadcast metrics for inputs and response details.
`campaign_search`	Searches broadcast and journey names and message subjects. Supports type and status filters, and returns grouped matches with links to the relevant campaign in Vero. See Campaign search for inputs and response details.
`topic_list`	Lists preference-centre topics in your project.
`topic_get`	Retrieves a single preference-centre topic.

Write tools

Tool	What it does
`broadcast_create`	Creates an unscheduled broadcast draft.
`broadcast_update`	Updates a broadcast’s metadata, such as its name or schedule.
`broadcast_message_create`	Creates an additional message (A/B test arm) on a draft broadcast.
`broadcast_message_update`	Updates a message’s sender or active flag on a draft broadcast.
`broadcast_content_create`	Creates localized content for a broadcast message.
`broadcast_content_update`	Partially updates localized content for a broadcast message.
`topic_create`	Creates a preference-centre topic.
`topic_update`	Updates a preference-centre topic.

Journeys are currently read-only in the Vero MCP: there’s no journey_create or journey_update tool yet. Broadcasts support full read and write.

Get started

ChatGPT

Connect Vero as a custom connector in ChatGPT.

Claude Code

Add Vero as an MCP server in Claude Code.

Notion

Add Vero as a custom MCP connection to a Notion Custom Agent.

Authentication

Learn how to generate an API secret key and authenticate the Vero MCP server.

Broadcast metrics

Use broadcast_metrics_get to retrieve sends, deliveries, opens, clicks, and unsubscribes for one or more broadcasts. It is read-only. This tool returns absolute counts rather than percentage rates. Derive a rate as metric / sends * 100, rounded to two decimal places. A null metric means the count is inconsistent with sends—the UI displays a dash, not zero. Date filters apply to the date a message was sent, not the date of an engagement. A window excluding the send date returns zeroes even when an open or click occurred during the window.

Journey metrics

The journey_metrics_get tool returns lifetime Journey counters (entered, here_now, exited, and messages_sent) plus aggregate per-message engagement metrics (sends, deliveries, opens, clicks, and unsubscribes). Use start_date and end_date for an inclusive reporting window. The date window applies only to engagement metrics and filters by message send date. Not by engagement date. Journey counters remain lifetime totals. Rates are derived from sends. A null metric indicates inconsistent data and should be displayed as unavailable, not zero.

Campaign search

The campaign_search tool uses case-insensitive substring matching across broadcast and journey names and message subjects, including active localized subjects. Queries must be 3–200 characters. Results can be filtered by campaign type or status and limited to 1–25 matches per type. Message bodies aren’t searched. Use the relevant content tool to read a matching message’s body. Archived campaigns are excluded unless you explicitly ask to filter for the archived status.

Prefer working with raw docs?

If you’d rather point an LLM at our documentation directly instead of connecting to your Vero data, see Use our docs with AI.

​Why MCP

​Server

​Available tools

​Read tools

​Write tools

​Get started

ChatGPT

Claude Code

Notion

Authentication

​Broadcast metrics

​Journey metrics

​Campaign search

​Prefer working with raw docs?

Why MCP

Server

Available tools

Read tools

Write tools

Get started

Broadcast metrics

Journey metrics

Campaign search

Prefer working with raw docs?