Ask your agent what your site earned.
Vero hosts an MCP server at mcp.getvero.dev. Give your AI client its URL and sign in to Vero: your agent reads your traffic and revenue and answers with your real figures. No key to copy, no server to run.
Already have an account? Connect your AI from the dashboard
Copy a command or a URL, then sign in.
Pick your client and copy the command or the URL. Your client opens Vero to sign in. If it cannot, use a read-only key instead.
Claude Code
Run this in your terminal.
claude mcp add --transport http vero https://mcp.getvero.dev/mcpThen type /mcp in Claude Code, pick vero and sign in.
Your client opens Vero in your browser. Sign in, pick a site and allow read-only access. You can also let it read every other site you see. There is no key to copy.
Use an API key instead
Run this in your terminal.
claude mcp add --transport http vero https://mcp.getvero.dev/mcp \
--header "Authorization: Bearer vk_your_key"Replace vk_your_key with the read-only key you create in the dashboard.
Claude
Paste this URL into your client.
https://mcp.getvero.dev/mcpIn Claude, open Connectors in Settings, add a custom connector and paste this URL. It works on claude.ai and in Claude Desktop.
Your client opens Vero in your browser. Sign in, pick a site and allow read-only access. You can also let it read every other site you see. There is no key to copy.
Use an API key instead
Add this to claude_desktop_config.json.
{
"mcpServers": {
"vero": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.getvero.dev/mcp",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer vk_your_key"
}
}
}
}With a key, Claude Desktop connects through the mcp-remote bridge, which needs Node.js.
Replace vk_your_key with the read-only key you create in the dashboard.
ChatGPT
Paste this URL into your client.
https://mcp.getvero.dev/mcpIn ChatGPT, add a custom MCP server and paste this URL. Whether you can depends on your ChatGPT plan and workspace settings.
Your client opens Vero in your browser. Sign in, pick a site and allow read-only access. You can also let it read every other site you see. There is no key to copy.
Cursor
Add this to ~/.cursor/mcp.json.
{
"mcpServers": {
"vero": {
"url": "https://mcp.getvero.dev/mcp"
}
}
}Your client opens Vero in your browser. Sign in, pick a site and allow read-only access. You can also let it read every other site you see. There is no key to copy.
Use an API key instead
Add this to ~/.cursor/mcp.json.
{
"mcpServers": {
"vero": {
"url": "https://mcp.getvero.dev/mcp",
"headers": {
"Authorization": "Bearer vk_your_key"
}
}
}
}Replace vk_your_key with the read-only key you create in the dashboard.
VS Code
Add this to .vscode/mcp.json.
{
"servers": {
"vero": {
"type": "http",
"url": "https://mcp.getvero.dev/mcp"
}
}
}Your client opens Vero in your browser. Sign in, pick a site and allow read-only access. You can also let it read every other site you see. There is no key to copy.
Use an API key instead
Add this to .vscode/mcp.json.
{
"inputs": [
{
"type": "promptString",
"id": "vero-key",
"description": "Vero API key",
"password": true
}
],
"servers": {
"vero": {
"type": "http",
"url": "https://mcp.getvero.dev/mcp",
"headers": {
"Authorization": "Bearer ${input:vero-key}"
}
}
}
}VS Code asks for the key the first time and stores it for you, so it is never written in the file.
Codex
Run this in your terminal.
codex mcp add vero --url https://mcp.getvero.dev/mcpcodex mcp login veroYour client opens Vero in your browser. Sign in, pick a site and allow read-only access. You can also let it read every other site you see. There is no key to copy.
Use an API key instead
Add this to ~/.codex/config.toml.
[mcp_servers.vero]
url = "https://mcp.getvero.dev/mcp"
bearer_token_env_var = "VERO_API_KEY"Codex reads the key from an environment variable. Set it with the line below.
export VERO_API_KEY="vk_your_key"Replace vk_your_key with the read-only key you create in the dashboard.
Windsurf
Add this to mcp_config.json.
{
"mcpServers": {
"vero": {
"serverUrl": "https://mcp.getvero.dev/mcp",
"headers": {
"Authorization": "Bearer vk_your_key"
}
}
}
}Open the file from Cascade, with its "Open MCP config file" action.
Replace vk_your_key with the read-only key you create in the dashboard.
This client connects with a read-only API key.
Other client
Add this to your client's MCP configuration.
{
"mcpServers": {
"vero": {
"url": "https://mcp.getvero.dev/mcp"
}
}
}An MCP client that signs in with OAuth needs only this URL. One that can only send a bearer header uses the API key.
Your client opens Vero in your browser. Sign in, pick a site and allow read-only access. You can also let it read every other site you see. There is no key to copy.
Use an API key instead
Add this to your client's MCP configuration.
{
"mcpServers": {
"vero": {
"url": "https://mcp.getvero.dev/mcp",
"headers": {
"Authorization": "Bearer vk_your_key"
}
}
}
}Replace vk_your_key with the read-only key you create in the dashboard.
According to Vero, which source brought the most revenue this week?
verovero_get_attribution(period: "7d")
news.ycombinator.com brought the most: €7,124 from 3,420 visitors, 39% of the week's €18,423.
Three steps to your first answer.
- 1
Add Vero to your client
Run the command, or paste the URL or the config for your client. No key goes in it.
- 2
Sign in and pick a site
Your client opens Vero in the browser. Sign in, pick a site and allow read-only access. To compare sites, also let it read every other site you see.
- 3
Ask in plain words
Your agent calls Vero when a question needs your data, and answers with the figures it read.
Questions about your site, answered with its own data.
It reads traffic, revenue, attribution by source and campaign, goals, cohorts, live visitors and anomalies. The answers below use the public demo data.
You ask: Which campaign made money this week?
You get: Revenue by campaign: launch_week brought €6,666, and €9,492 came with no campaign tag.
You ask: Has anything unusual happened with revenue lately?
You get: The anomalies Vero found: a recent drop in revenue, €2,640 against a typical €3,500 (-24.6%).
You ask: How is the newsletter signup converting?
You get: Your goals and their rates: 934 signups, 5.7% of sessions.
You ask: How many people are on the site right now?
You get: Live visitors, with the pages they are on.
You ask: Do customers from launch week keep paying?
You get: Revenue cohorts by the week of their first payment.
You ask: Where does my traffic come from?
You get: Visitors, pageviews, top pages, referrers and countries for the period you name.
It reads. It never writes.
- It cannot send events or change anything. Settings, goals and data stay as they are.
- It reads the site you pick, or every site you see if you allow it. Each call checks that you still see that site and that its workspace is on Pro.
- Revoke a connection from Connect your AI in the dashboard and it stops at once. One unused for 90 days expires on its own.
- Windsurf connects with a read-only API key, because its sign-in is not documented. With a key, Claude Desktop needs Node.js for the mcp-remote bridge.
Part of Pro.
The MCP server is a Pro feature. Pro starts at €9 + VAT a month.
Common questions
What can my AI see, and what can it not?
The site you pick when you connect, plus every other site you see if you allow it, and only to read them. Each connection can be revoked, and it stops working within 10 seconds.
Do I need to install or host anything?
No server to host: it runs at https://mcp.getvero.dev/mcp. Your client connects with that URL and you sign in to Vero in the browser. Only Claude Desktop with an API key needs something installed: Node.js, for the mcp-remote bridge.
Can my agent change my data?
No. Sign-in and key alike give read-only access. It cannot send events or change anything.
Which clients work?
By sign-in: Claude Code, Claude (claude.ai and Claude Desktop), Cursor, VS Code, Codex and any MCP client that signs in with OAuth. ChatGPT too, if your ChatGPT plan and workspace let you add a custom MCP server. By API key: Windsurf, and any client that sends a bearer header.
Can one connection read all my sites?
Yes, if you allow it. When you sign in, or when you create a read-only key in Connect your AI, tick the box to let it read every other site you see, in every workspace. The site you set it up on stays the default. Name another site, by its domain, and your agent reads that one; ask which sites it can read and it lists them. A key with write access reads its own site only.
Keep reading
- DocumentationInstall the tracker, fire events, attribute revenue, use the API.
- IntegrationsConnect Stripe, Lemon Squeezy and Paddle.
- See which source brings money, and which brings profit.See which source brings revenue and which brings profit, who found each customer, who closed the sale and how long people take to pay. No cookies. Pro.
- Hear when a number moves, without opening the dashboard.Hear when traffic or revenue leaves a typical day, with where the change came from. New-sale alerts, watches and a Monday digest that leads with revenue.
- A 1.2 KB tracker. You pick the rest.The script that measures your site: 1.2 KB core, 2.7 KB with all 9 modules, gzipped. No cookies, nothing stored on the device. Pick your modules.
- PricingPay for pageviews and custom events. Every Pro tier has every feature.