AdBid
DocumentationAdBid MCP
MCP server and MCP App

Use AdBid from your AI client

Connect Codex, Claude, ChatGPT, Cursor, or another Streamable HTTP MCP client to analyze Meta Ads, perform guarded updates, and launch Meta or Google Ads AI Campaigns through guided forms.

Endpoint
Hosted Streamable HTTP MCP transport
https://adbid.me/api/mcp
No local package required

Overview

AdBid MCP gives an AI client structured tools instead of browser automation. The server authenticates an AdBid owner, uses the owner's existing Meta and Google Ads connections, validates every operation, and returns structured results the client can explain or render.

Connect a client

  1. 1. Connect an ad platform. Sign in to AdBid and connect Meta and/or the Google Ads account that owns the required customers.
  2. 2. Create a key. Open Settings → MCP API Keys and choose read-only or read-and-write access.
  3. 3. Add the server. Use the hosted URL and the one-time key in your MCP client.
  4. 4. Reload the client. Existing sessions may not discover a newly added MCP server until they are restarted.

Generic MCP client configuration

The exact settings filename depends on the host. Use the configuration shape supported by your client.

{
  "mcpServers": {
    "adbid-ads": {
      "url": "https://adbid.me/api/mcp",
      "headers": {
        "Authorization": "Bearer adbid_mcp_YOUR_KEY"
      }
    }
  }
}

What the server can do

Tools are grouped by operator job. Your key scope and connected accounts determine which results and actions are available.

Accounts and delivery
Discover accounts and inspect live Meta delivery objects.
list_ad_accounts
list_campaigns
list_adsets
list_ads
Analytics and diagnostics
Read spend, performance, activity, incidents, limits, revenue, and LTV context.
get_insights
get_account_spend
get_intraday_metrics
get_incidents
get_ltv_forecast
Assets and targeting
Find Pages, Pixels, audiences, locations, interests, forms, creatives, and previews.
list_pages
list_pixels
search_locations
search_targeting_interests
get_creative
Meta AI Campaign launch
Configure, preview, launch, monitor, and cancel a guarded Meta campaign launch group.
configure_campaign_launch
preview_campaign_launch
launch_campaign_group
get_campaign_launch_status
Google AI Campaign launch
Configure, preview, launch, and monitor Google App/UAC or Search campaigns.
configure_google_campaign_launch
preview_google_campaign_launch
launch_google_campaign_group
get_google_campaign_launch_status
Guarded writes
Pause, activate, rename, or change budgets with a write-enabled key and explicit confirmation.
update_campaign
update_adset
update_ad
Operator reviews
Run structured weekly, creative fatigue, refund risk, and payback reviews.
weekly_account_review
creative_fatigue_check
refund_risk_audit
ltv_payback_review

Launch an AI Campaign

For Meta ask: “AdBid MCP — open the Meta AI Campaign launch form.” For Google ask: “AdBid MCP — open the Google AI Campaign launch form.”The host can render the MCP App, while the same workflow remains available as structured tool calls when a host has no App UI.

1

Choose a project

The form loads the projects available to the authenticated AdBid owner.

2

Choose an ad account

Only accounts available through the selected project and Meta connection are shown.

3

Configure the launch

Select Page, Pixel, one or more GEOs, devices and operating systems, strategy, budgets, and creative mode.

4

Preview

AdBid validates access, structure, budget limits, GEO allocation, and returns a preview hash.

5

Approve and launch

The client sends the preview hash, a unique idempotency key, and confirm=true.

6

Monitor

Read the launch group status or cancel the group while cancellation is still available.

Multiple GEOs

GEO is a list, so one launch group can include several countries. The daily cap applies to the entire group; the preview rejects a cap that cannot fund at least one campaign slot per GEO.

{
  "project_ref": "app:13",
  "ad_account_id": "26746757628306575",
  "geos": ["US", "DE", "PL"],
  "strategy_id": "1-1-N",
  "campaign_start_budget_minor_units": 5000,
  "launch_group_daily_cap_minor_units": 15000
}

AdBid selects the Project Pixel automatically and falls back to the Pixel saved in Strategies settings. Manual selection appears only when the configured Pixel is missing or unavailable to the selected ad account.

Google Ads launch

Google uses a separate MCP App because its campaign structure and required assets differ from Meta. It follows the fast Google AI Launch flow: per-GEO CPA, Campaign → Ad group → Ad structure, generated formats or existing Media collections, and live pipeline progress. The same preview hash, idempotency key, owner access, and explicit confirmation safeguards apply.

1

Choose a project and account

The form lists the owner’s AdBid projects and connected Google Ads customers.

2

Choose a campaign type

Create an App/UAC campaign or a Search campaign.

3

Configure budget and GEO

Set the campaign budget, default Target CPA, multiple GEOs, and an optional CPA override for each country.

4

Choose structure and creatives

Set campaigns per GEO, ad groups per campaign, and ads per group. Generate Google formats or reuse existing AdBid Media collections with images and videos.

5

Add ads and targeting

App text is optional; Search requires a final URL, keywords, at least three headlines, and two descriptions.

6

Preview and approve

AdBid validates campaign totals, creative source, account access, and the exact launch plan before confirmation.

7

Monitor

The form automatically reads live pipeline progress and per-campaign results using the returned run ID.

Write safety

Write-enabled key
Read-only keys cannot mutate Meta objects or start a Meta or Google launch.
Required safeguard
Explicit confirmation
Write tools require confirm=true; a conversational request alone is not enough.
Required safeguard
Preview hash
A launch is tied to the exact validated preview the user approved.
Required safeguard
Idempotency key
A unique key prevents an accidental retry from creating the same launch twice.
Required safeguard

Where the interactive form appears

The form is an MCP App resource returned by the AdBid server. It appears inside a host that supports MCP Apps and allows the server's UI resource. Hosts without MCP App rendering still receive the same fields as structured data, so the assistant can ask for Project, Ad account, GEOs, and budgets step by step.

Troubleshooting

401 or authentication failed

Create a new active key, replace the placeholder, and ensure the Authorization header starts with Bearer.

The server or tools are missing

Restart the MCP client or open a new session after adding the server configuration.

The form is not visible

The active host may not support MCP Apps. Use the structured fallback or a compatible host.

No Projects, Pages, Pixels, or Google customers

Check the AdBid owner, project membership, connected advertising account, and asset permissions.

Launch preview rejects the budget

Increase the group daily cap or reduce the number of GEOs and campaign slots.