Run Veya from your AI tool with MCP
Connect Claude Code, Codex, Cursor or Claude Desktop to Veya over MCP, then build, review, target, publish and test popups from your AI tool.
MCP (Model Context Protocol) lets an AI tool work in your Veya account directly. Once it's connected, you can ask it to create a form, look at the design, change the targeting, publish it and read the results, without opening the dashboard.
Make a spin-to-win for returning visitors on /collections with 10% off, show me it on mobile, then publish it.
What you need
- A Veya account with an active plan or trial.
- An AI tool that supports remote MCP servers.
Every connection uses this address:
https://app.veyapopups.com/mcp
Choose how to connect
- Sign in (OAuth): your tool opens the browser once, and you approve it in Veya. Tokens refresh on their own.
- An API key: best for tools you set up with a file. Keys start with
vk_.
Create an API key
Skip this if you're signing in.
- Open Settings > Agents & API.
- Under API keys, enter a Name.
- Choose the Access: Full access or Read only. A read-only key can read, run reports, check the install and make previews, but can't change anything.
- Choose when it Expires, then click Create key.
- Click Copy key. You won't see it again.
Connect an agent on the same page shows the exact setup for your tool, with your key filled in.
Connect your tool
Claude Code, signing in
claude mcp add --transport http veya https://app.veyapopups.com/mcp
Then run /mcp in Claude Code to sign in.
Claude Code, with a key
claude mcp add --transport http veya https://app.veyapopups.com/mcp --header "Authorization: Bearer vk_..."
Codex
In ~/.codex/config.toml, then set VEYA_API_KEY in your environment:
[mcp_servers.veya]
url = "https://app.veyapopups.com/mcp"
bearer_token_env_var = "VEYA_API_KEY"
Cursor or Claude Desktop
{
"mcpServers": {
"veya": {
"url": "https://app.veyapopups.com/mcp",
"headers": { "Authorization": "Bearer vk_..." }
}
}
}
What it can do
- Build: create a form from a brief, start a build, request changes, leave comments.
- Review: see pictures of the design on a computer and a phone, and get share links for both. A tool with a browser, such as Playwright MCP, can also try the design itself.
- Launch: publish, pause and archive; set targeting, schedule, display, style, side tab, consent and offers.
- Test: run A/B tests and the autopilot, and approve or promote challengers.
- Connect: Klaviyo lists and webhooks.
- Measure: analytics, attribution, reports and survey answers.
What still needs a person
Your tool gives you a link for each of these:
- Creating the API key, or approving the sign-in
- Paying for a plan
- Approving Klaviyo's connection
- Installing the Shopify app
Stay in control
- Everything is logged. Recent agent activity in Settings > Agents & API shows changes by key or app name.
- You're told. Changes that reach your storefront notify you in the bell and by email, such as "Claude Code published Spring sale".
- You can cut it off. Revoke a key, or Disconnect an app under Signed-in apps.
- Keys can't make keys. A leaked key can't create a longer-lived one.
A full-access key or app acts as the store owner, including publishing, so only connect tools you trust. Limits are 120 requests a minute per key or app, and 10 builds a minute per store.
For agencies
An agency key works across approved client stores. The tool lists them and names the store on each call. See Agency access.
Your next popup?
We’ll build it for you.
14-day free trial on every plan. Custom design and revisions included.