Wevion MCP & CLI · for any AI
Manage all your ads from the AI you already use.
Connect Wevion to Claude, Cursor and any MCP-capable client with a single API key, and run Meta, Google, TikTok, Taboola and Snapchat from one chat: read performance, launch campaigns and build rules.
Wavo, the AI copilot, already runs these platforms inside Wevion today. See what Wavo does today
Pause anything under 1.5 ROAS after €50 spend, across Meta and TikTok.
Your AI assistant
Here’s the plan, 3 actions across 2 platforms:
Awaiting your approval
- · Pause 4 Meta ad sets under 1.5 ROAS
- · Pause 2 TikTok ad groups under 1.5 ROAS
- · Leave budgets untouched
What the MCP server is
The Model Context Protocol (MCP) is an open standard that lets AI assistants such as Claude or Cursor connect to external tools and data. The Wevion MCP server exposes your account (campaigns, ad accounts, insights) as tools the AI can query and use: ask your assistant to analyze performance or act on your campaigns in natural language, without opening the dashboard.
- Ask the AI for the status and metrics of your campaigns.
- Query ad accounts, insights and reports in natural language.
- Have it run actions on the Wevion API, within your key’s permissions.
Works with any MCP client, for example Claude Desktop, Cursor, Cline or VS Code.
What you can do
The same agentic power that runs inside Wevion, in the AI of your choice. The available tools always reflect your API key’s permissions.
One connector, five platforms
- Spend, ROAS and conversions across all your Meta, Google, TikTok, Taboola and Snapchat accounts
- True profit per campaign and SKU, with COGS, shipping, fees and tax folded in
- Cross-channel comparison with metrics you can actually compare
“Show me every account losing money this week: spend, ROAS, profit.”
Rules & automation from a chat
- Build cross-platform rules from a single sentence
- Shift budget to the best performer, 24/7, with safeguards
- Auto-pause creatives that hit fatigue
“Pause anything under 1.5 ROAS after €50 spend, across all platforms.”
Launch & optimize by prompt
- Duplicate winners across platforms and adjust budgets in bulk
- Launch campaigns across five platforms at once
- Generate ad hooks per vertical and reuse audiences across accounts
“Duplicate my top Meta campaign into Google and TikTok at €50/day.”
Why Wevion, not just the official connector
Platform coverage
One ad network only
Automation
Rules set up per platform, by hand
Data scope
Stops at one account’s data
Get connected in three steps
- 01
Create an API key
Generate a new API key from the API keys section. Legacy keys without a team context are not supported: recreate them before using MCP.
- 02
Add the remote MCP server
In your MCP client, add a remote server using the Streamable HTTP (POST) transport and the x-api-key header with your key.
Endpointhttps://mcp.wevion.ai/mcp - 03
Example configuration
The exact format depends on your client, but conceptually:
{ "mcpServers": { "wevion": { "type": "http", "url": "https://mcp.wevion.ai/mcp", "headers": { "x-api-key": "YOUR_API_KEY" } } } }
Some AI clients require a paid plan to add remote connectors.
Built for trust
Giving an AI access to your ad accounts is a big deal. Wevion keeps you in control at the key level.
Granular, revocable keys
Each API key is scoped to specific domains and actions. Grant read-only, or read plus write, and revoke it anytime.
Bound to user & team
A key carries its own team context and permissions. The backend derives everything from the key, with no manual team setup.
Least-privilege by design
Give an integration only what it needs. The server only ever exposes the tools your key allows.
Your data stays yours
Keys are encrypted and isolated per team. We don’t train models on your campaigns.
API-key accessGranular per-domain permissionsTeam-level isolationRevoke anytimeGDPR-aligned
Frequently asked
Your ads don’t live on one channel. Neither should your AI.
Bring Meta, Google, TikTok, Taboola and Snapchat into the AI you already use.