Ovaideu

npx add-mcp 'https://ovaideu.com/api/mcp'

One connector, your enabled marketing tools.

Once connected, your agent can read from and make authorized changes across the accounts you authorize — nothing wider. Enabled writes remain scoped to your key and resource permissions. A successful request is not a claim of complete lifecycle or attribution acceptance.

See available and Planned workflows

Google Ads — build, edit and optimize real campaigns

Google Analytics 4 — key events and conversions

Google Search Console — queries and top pages

Google Tag Manager — tags and triggers

Google Business Profile — profile and locations

Meta Ads — campaigns, ad sets and reporting

The three things every client needs.

Whatever client you use, the connection is always the same URL, the same header, and a key you create yourself. Get these right first — the per-client steps below just plug them in.

1. The endpoint

Point your client at the MCP server below. It speaks the Model Context Protocol over HTTPS (JSON-RPC 2.0), protocol version 2025-06-18.

https://ovaideu.com/api/mcp

2. Authentication

Send your Ovaideu API key as a Bearer token. Web connectors and the desktop bridge do this for you; for direct API calls, add the header yourself.

Authorization: Bearer YOUR_OVAIDEU_API_KEY

3. Your MCP key

Sign in to Ovaideu, activate your own MCP access, and create a user-bound key in the dashboard. Workspace admins can also manage internal users from the same page.

Claude and ChatGPT on the web — no install.

Claude and ChatGPT can connect to the remote MCP server directly. Add it once as a custom connector and authorize your own Google or Meta account in your browser.

Claude

Add Ovaideu in Claude

1. On a Claude Pro, Max, Team or Enterprise plan, open Settings → Connectors.
2. Click Add custom connector and paste the MCP connector URL.
3. When prompted, authenticate with your Ovaideu API key (Bearer) or complete the guided sign-in.
4. Start a chat and ask Ovaideu to build, review or optimize a campaign in plain language.

ChatGPT

Add Ovaideu in ChatGPT

1. Open Settings → Connectors → Add custom connector.
2. Paste the MCP connector URL.
3. Authenticate with your Ovaideu API key (Bearer), then complete the Google or Meta sign-in in your own browser.
4. Ask ChatGPT to run your ads work — it calls Ovaideu behind the scenes.

Connector URL

Paste this into either client:

https://ovaideu.com/api/mcp

Connect ChatGPT to the full OVAIDEU workspace.

Use one connector for the full read, create, update, delete and optimize lifecycle across every OVAIDEU surface already available to your account: Paid Media, GA4, GTM, Search Console, Business Profile, Merchant Center, Meta, Shopify, WordPress, CRM, social posting, email, reports, billing, support and orchestration.

Live connector URLs

Use the public hosts only. Do not use localhost for ChatGPT web.

https://ovaideu.com/mcp https://ovaideu.com/api/mcp

How account selection works

OVAIDEU uses the signed-in user's own provider connection together with the workspace role and assigned resources. Select the intended account when more than one is available. A provider-visible account is not permission to cross a workspace or client boundary; server-side resource assignments still apply.

Assigned-resource boundaries applyAgents can ask, confirm, then attach

Codex, Claude Desktop, Cursor and local agents.

Clients that speak MCP over stdio reach the server through the bundled Node bridge. It forwards each call to the same URL with your key as a Bearer token — you never paste a secret into a web form.

01

Create your MCP key

Sign in to the dashboard, open MCP Management, activate your MCP access, and create one scoped key bound to your own user email.

02

Install the bridge

Download the installer zip, run the numbered Windows or Mac installer, and let it place the bridge on your computer.

03

Add the config

Paste the Claude JSON or Codex TOML below into your client and set the bridge path. Requires Node.js on the machine.

04

Paste your own key

Paste the MCP key created from your signed-in OVAIDEU account. The key carries your workspace, role, subscription, client map and provider permissions.

Claude Desktop config

{
  "mcpServers": {
    "ovaideu": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/ovaideu-desktop-mcp-bridge.mjs"],
      "env": {
        "OVAIDEU_MCP_URL": "https://ovaideu.com/api/mcp",
        "OVAIDEU_MCP_ORIGIN": "https://claude.ai",
        "OVAIDEU_MCP_TOKEN": "PASTE_YOUR_OWN_OVAIDEU_MCP_KEY_HERE"
      }
    }
  }
}

Codex config (config.toml)

[mcp_servers.ovaideu]
command = "node"
args = ["/ABSOLUTE/PATH/TO/ovaideu-desktop-mcp-bridge.mjs"]

[mcp_servers.ovaideu.env]
OVAIDEU_MCP_URL = "https://ovaideu.com/api/mcp"
OVAIDEU_MCP_ORIGIN = "https://chatgpt.com"
OVAIDEU_MCP_TOKEN = "PASTE_YOUR_OWN_OVAIDEU_MCP_KEY_HERE"

Test the connection from a terminal.

The same endpoint answers direct HTTP calls. Run a tools/list request with your key to confirm access before wiring up a client. A valid key returns the tools it is allowed to see.

Connection test

curl -s https://ovaideu.com/api/mcp \
  -H "Authorization: Bearer YOUR_OVAIDEU_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A 401 means the key is missing or wrong; a 403 means your signed-in user does not have active MCP access yet — open API & MCP and activate your access.

Any MCP-compatible AI client.

Ovaideu follows the open Model Context Protocol, so it works with any client that speaks MCP. Web clients use the connector URL directly; desktop and CLI clients use the bridge.

ClaudeChatGPTCodexGeminiCursorKimi

MCP

The primary surface. One remote server, user-bound scoped access, and the same tenant-scoped access as the dashboard.

API

The same endpoint answers direct HTTPS calls for authorized server-to-server workflows in your own workspace.

CLI

A public installer command is planned after MCP/API verification. Until then, use the bridge package and PDF.

Free during the opening period

Ovaideu workspaces include scoped keys, MCP connectors, usage controls and audit logs after account setup.

No card required · White-label for agencies