> ## Documentation Index
> Fetch the complete documentation index at: https://help.getvero.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Vero with AI

> Connect Vero to AI assistants and coding agents through our MCP server to manage broadcasts and journeys in natural language.

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.

<Info>
  The Vero MCP server is in early access. [Contact us](mailto:support@getvero.com) 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.
</Info>

## 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](/api-reference/overview#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://api.getvero.com/mcp
```

It authenticates with a Bearer token: the same API secret key used for the [Campaigns API](/api-reference/overview#campaigns-api). See [Authentication](/vero-ai/authentication) for how to generate one.

## Available tools

The MCP server wraps the same [Campaigns API](/api-reference/overview#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 full graph of triggers, nodes, and edges.     |
| `journey_message_list`   | Lists all message nodes within a journey.                                               |
| `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.   |
| `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. |

### 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.       |

<Note>
  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.
</Note>

## Get started

<CardGroup cols={2}>
  <Card title="ChatGPT" icon="comment-dots" href="/vero-ai/setup/chatgpt">
    Connect Vero as a custom connector in ChatGPT.
  </Card>

  <Card title="Claude Code" icon="terminal" href="/vero-ai/setup/claude-code">
    Add Vero as an MCP server in Claude Code.
  </Card>

  <Card title="Notion" icon="book" href="/vero-ai/setup/notion">
    Add Vero as a custom MCP connection to a Notion Custom Agent.
  </Card>

  <Card title="Authentication" icon="key" href="/vero-ai/authentication">
    Learn how to generate an API secret key and authenticate the Vero MCP server.
  </Card>
</CardGroup>

## 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](/vero-ai/docs-with-ai).