Using AdsCove in Codex (Desktop / CLI)

AdsCove Product & Engineering · Last reviewed August 5, 2026

Available · OAuth

Codex natively supports remote MCP and OAuth. Recommended: add the server via CLI, then log in — no API key needed; authorization opens a browser, the same OAuth flow as Claude.

Connection details

Everything the connection needs, in one place — copy any line into your client or your agent:

Endpoint (MCP):  https://adscove.com/api/mcp
Transport:       Streamable HTTP
Auth (recommended): OAuth 2.1 (no key needed)
Auth (fallback):    HTTP header Authorization: Bearer sk_live_your_key (only if OAuth is unavailable)
REST fallback:   POST https://adscove.com/api/v1/tools/{tool_name}   with the same Bearer header
Full catalog:    https://adscove.com/api/mcp?tools=full   (optional; default endpoint is faster and includes run_adscove_tool)
Verify tool:     list_connections   (free, read-only)

Setup steps

Run the commands below
A browser opens the AdsCove authorization page → sign in → click Authorize
Optional Codex Skills add local Meta Ad Library capture and image generation workflows

codex mcp add adscove --url https://adscove.com/api/mcp
codex mcp login adscove

mkdir -p ~/.codex/skills/adscove-meta-ad-library-capture ~/.codex/skills/adscove-ad-image-generation
curl -fsSL https://adscove.com/api/codex-skills/adscove-meta-ad-library-capture \
  -o ~/.codex/skills/adscove-meta-ad-library-capture/SKILL.md
curl -fsSL https://adscove.com/api/codex-skills/adscove-ad-image-generation \
  -o ~/.codex/skills/adscove-ad-image-generation/SKILL.md

Or: add to ~/.codex/config.toml manually

[mcp_servers.adscove]
url = "https://adscove.com/api/mcp"
http_headers = { Authorization = "Bearer sk_live_your_key" }

# Optional: list every low-level tool separately instead of the compact catalog.
# url = "https://adscove.com/api/mcp?tools=full"

Or: hand it to your AI agent

Don't want to configure it yourself? Paste the block below into the AI agent you're using (Claude, Cursor, an MCP agent, etc.) — it contains everything needed to set up the connection.

In Codex, run: codex mcp add adscove --url https://adscove.com/api/mcp && codex mcp login adscove — this opens a browser for OAuth. Then install AdsCove Codex Skills from /docs/skills if you want local Ad Library capture and image-generation workflows. Finally call list_connections to confirm.

Verify

Say: "check my platform connection status".

Connect Meta Ads and Google Ads to Codex

How do I connect Meta Ads to Codex?

Run codex mcp add adscove --url https://adscove.com/api/mcp, then codex mcp login adscove to finish OAuth in the browser. Connect your Meta ad account in AdsCove, and Codex reaches it through the same AdsCove server. Ask Codex to check your platform connection status to confirm.

Is there a Google Ads MCP for Codex?

Yes, through the same AdsCove server. There is no second URL to add: connect your Google Ads account in AdsCove and Codex can read campaigns and search terms, including Merchant Center accounts linked to that Google Ads customer.

Do I need an API key to use AdsCove in Codex?

No. codex mcp login adscove uses OAuth, so there is nothing to paste. An AdsCove API key is only for the manual ~/.codex/config.toml fallback shown above, where it goes in http_headers.

Can Codex change my ads once Meta or Google Ads is connected?

Reads run directly. Writes such as budgets, status changes, or new drafts come back as pending actions that you approve or reject, and new campaigns are created paused, so nothing goes live silently.

What you can do once connected

Check the business report, compare platform ROAS against real Shopify orders, create paused ad drafts, and submit budget changes. Direct writes need confirmation; separately enabled guardrails can only auto-pause within your limits. Try: “Which ads lost money in the last 7 days?”

Get started