Skip to main content
The Vero MCP server authenticates with OAuth. When you add https://mcp.getvero.com/mcp to a client without an authentication header, the client sends you to Vero to sign in and approve the connection, then manages tokens itself: there’s no key to generate, paste, or rotate. The setup guide for each client shows where this happens.
The Campaigns API, and the MCP server built on it, is in public preview. Contact us to request access.

​
Legacy: bearer token authentication

Bearer token authentication is deprecated and may be removed in a future release. It predates OAuth support. Existing integrations that pass a Campaigns API secret key in the Authorization header keep working for now, but don’t set up new connections this way.
To migrate an existing integration to OAuth:
  1. Remove the Vero server from your client, or delete its Authorization header.
  2. Add https://mcp.getvero.com/mcp again without an authentication header, following the setup guide for your client.
  3. Sign in to Vero and approve the connection when your client prompts you.
  4. Revoke the API key in your Vero account settings once nothing else uses it.
Integrations that still use an API key can keep pointing at the old address, https://api.getvero.com/mcp. OAuth only works at https://mcp.getvero.com/mcp.

​
Rate limits

MCP requests have dedicated rate limits:
  • 600 requests per minute per IP address
  • 300 requests per minute per credential
Clients should handle 429 Too Many Requests responses by honoring the Retry-After header and retrying with exponential backoff.