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/mcpOvaideu runs a Model Context Protocol (MCP) server, so an AI agent such as Claude, ChatGPT, Codex or Gemini can run your Google Ads, GA4, Search Console, Tag Manager, Business Profile and Meta Ads work in plain language — inside the same tenant-scoped, user-bound access as the dashboard. Add one connector URL, authenticate with your own API key, and you are set.
MCP connector URL
https://ovaideu.com/api/mcpAlso reachable at https://ovaideu.com/mcp — same server.
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 workflowsGoogle 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
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.
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/mcpSend 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_KEYSign 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 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.
Paste this into either client:
https://ovaideu.com/api/mcpUse 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.
Go to Settings, open Connectors or Plugins, then choose Add custom connector.
Use https://ovaideu.com/api/mcp as the MCP server URL. Remove any old api.ovaideu.com connector first.
Click Sign in with OVAIDEU, use your own OVAIDEU account, then approve connector access.
Inside OVAIDEU, connect the Google, Meta, Shopify, WordPress, social, email or CRM providers you want this user to manage.
Open the OVAIDEU connector settings, refresh actions, and set permissions to allow all actions when you want ChatGPT to execute user-approved work directly.
Ask ChatGPT to list connected Google Ads accounts, GA4 properties, and active campaigns. No account changes are made.
Ask for a supported action in normal language. The tools returned for your key, your role, resource assignments and provider permissions determine what can run. Expanded lifecycle workflows remain Planned until live acceptance.
Use the public hosts only. Do not use localhost for ChatGPT web.
https://ovaideu.com/mcphttps://ovaideu.com/api/mcpOVAIDEU 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.
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.
Sign in to the dashboard, open MCP Management, activate your MCP access, and create one scoped key bound to your own user email.
Download the installer zip, run the numbered Windows or Mac installer, and let it place the bridge on your computer.
Paste the Claude JSON or Codex TOML below into your client and set the bridge path. Requires Node.js on the machine.
Paste the MCP key created from your signed-in OVAIDEU account. The key carries your workspace, role, subscription, client map and provider permissions.
{
"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"
}
}
}
}[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"
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.
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.
Use View to inspect a file in the browser, or Download to save the package locally.
Give this PDF to your AI assistant. It includes the connector URL, the authentication step and the shortest path through account authorization.
Recommended. One zip with numbered Windows and Mac double-click installers.
Start here. A short setup path for desktop MCP users and AI assistants.
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.
The primary surface. One remote server, user-bound scoped access, and the same tenant-scoped access as the dashboard.
The same endpoint answers direct HTTPS calls for authorized server-to-server workflows in your own workspace.
A public installer command is planned after MCP/API verification. Until then, use the bridge package and PDF.
Ovaideu workspaces include scoped keys, MCP connectors, usage controls and audit logs after account setup.
No card required · White-label for agencies