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

# Connect Vero MCP to Claude Code

> Add the Vero MCP server to Claude Code so you can manage broadcasts and journeys from the CLI.

<Info>
  The Vero MCP server is in early access. Please provide feedback or issues [via email](mailto:support@getvero.com).
</Info>

## Prerequisites

* [Claude Code](https://docs.claude.com/en/docs/claude-code) installed.
* A Vero Campaigns API secret key ([see Authentication](/vero-ai/authentication)).

## Connect Vero

Add Vero as a remote MCP server with the `claude mcp add` command:

```bash theme={null}
claude mcp add vero --scope local --transport http https://api.getvero.com/mcp -H "Authorization: Bearer YOUR_VERO_API_KEY"
```

By default this adds Vero at **local** scope, available only to you in this project. We recommend keeping it there rather than switching to **project** scope. Since Vero only supports Bearer token authentication today, project scope would store your API key in `.mcp.json`, a file that's typically committed to source control and shared with your whole team.

Run `/mcp` inside Claude Code to confirm Vero shows up as connected.

## Try it out

Ask Claude Code things like:

* "List my draft broadcasts"
* "Get the details of broadcast \[id]"
* "What journeys do I have active right now?"

## Next steps

* [See available tools](/vero-ai/overview#available-tools)
* [Use our docs with AI](/vero-ai/docs-with-ai)