AdsCove
Log inSign up free

Install guide

Install AdsCove MCP in Cursor or Claude for Ecommerce Ops

Published September 23, 2026 · Last reviewed September 29, 2026 · AdsCove Product & Engineering

Short answer

Install AdsCove’s remote MCP once (https://adscove.com/api/mcp), finish OAuth in Cursor or Claude, then connect Shopify / Meta / Google in the AdsCove console. Reads can diagnose freely; budget and status writes stay approval-gated. You do not paste platform tokens into chat, and install ≠ unsupervised budget changes. Concepts: MCP for ecommerce agents.

What you are installing

AdsCove is a hosted remote MCP—not a local Python ads server you have to run yourself. Your AI client points at one endpoint; Shopify, Meta, and Google are authorized in the browser. Cursor and Claude (web / Desktop / compatible Code-style clients) use the same URL. Prefer OAuth; use an AdsCove API key only as a fallback for clients without remote-MCP OAuth (Authorization header in client config—never paste secrets into chat).

Before you install

  • An AdsCove account (browser signup is enough).
  • Access to the Shopify store and/or Meta and Google ad accounts you actually operate.
  • Cursor installed, or Claude web / Desktop (mobile can reuse a connector added on desktop; new custom MCP connectors usually cannot be created on Claude mobile).

Shared five steps (any client)

  1. Create AdsCove — No repo clone, and no Meta/Google access tokens inside the AI client.
  2. Connect business accounts — In the AdsCove console, connect Shopify (optional but recommended for cash truth), Meta Ads, and Google Ads. Confirm account IDs match the platform UIs.
  3. Add the remote MCP — Endpoint: https://adscove.com/api/mcp. Complete OAuth (see Cursor / Claude sections below).
  4. Verify with list_connections — Ask the agent to call list_connections and confirm the expected store and ad accounts before any report.
  5. Read first; gate writes — Start with a 7-day spend vs Shopify reconcile or a read-only channel report. Budget/status changes must return a pending execution you approve. Model: approval-gated ad changes.

Add AdsCove MCP in Cursor

High level (no secrets): open Cursor MCP / tools settings, add a remote server named AdsCove, set the URL to https://adscove.com/api/mcp, then choose Authenticate / OAuth and finish in the browser. After it connects, ask the agent to call list_connections. Client detail: /clients/cursor. Or paste the agent connect prompt into Cursor Agent and let it follow agent.md to add the server.

  • Config shape is usually remote MCP URL + OAuth—not long-lived platform tokens in mcp.json.
  • If the client only supports API keys: create a key in the AdsCove console, put it only in the client Authorization header; rotate keys and never commit them.

Add in Claude (web / Desktop / Code-style)

Claude web or Desktop: add a custom connector for the remote MCP—name AdsCove, server URL https://adscove.com/api/mcp—then finish OAuth. Once added on desktop/web, the same tools are usually available in Claude mobile; new custom connectors generally cannot be created from mobile alone. Claude Code / compatible CLI: follow the client docs to add the remote MCP endpoint and complete OAuth (or the client’s auth subcommand)—never put keys in prompts. Client pages: /clients/claude, /clients/claude-code.

What to do in week one

  1. Read-only: list_connections → last-7-day spend and delivery.
  2. Reconcile with weekly ecommerce diagnosis workflow—line up Shopify cash with paid spend and name attribution-gap evidence; do not invent ROAS cutoffs.
  3. Draft pause/budget changes only for objects you name; review the pending execution before approve.

How this relates to Meta-only MCP setup

If you mainly searched “how to set up meta mcp / adsmanager mcp,” channel-focused steps live in Meta Ads MCP setup. This page targets Cursor/Claude ecommerce install intent: one MCP, multi-platform connects, approval-gated writes. Google side: Google Ads MCP setup.

FAQ

Do Cursor and Claude need different MCP URLs?

No. Both use https://adscove.com/api/mcp. The difference is how each client adds a remote server and finishes OAuth.

Do I have to connect Shopify first?

Not a hard prerequisite—you can connect Meta or Google first for read-only work. Without store cash you cannot finish cash-vs-channel reconciliation; ecommerce ops usually connect Shopify soon.

Will the agent auto-change budgets after install?

By default, no. Protected writes return a pending execution; you approve (or reject) before run. See the approval-gated guide.

Should I paste an API key into the chat?

No. Prefer OAuth. If a key is required, keep it in local client MCP config Authorization only—scope tightly and rotate.

list_connections is empty or my shop is missing—what now?

Confirm Shopify / Meta / Google show active in the AdsCove browser console first, then re-run list_connections in Cursor / Claude. If the wrong shop connected, reconnect using the Shopify-returned authorized shop as source of truth—not a pasted admin alias. For one-agent workspace framing see Shopify+Meta+Google single MCP workspace.

Is falling back to an API key safe when OAuth fails?

Yes as a fallback—never paste it into chat. Keep it in local client MCP Authorization only, scope tightly, and rotate. Prefer OAuth whenever the client supports remote-MCP OAuth.

Why do writes stay pending / need approve_action?

By design: budget, status, and publish writes return an execution_id you review before approve. Install ≠ unsupervised budget changes. See approval-gated ad changes.

Related guides

MCP for ecommerce agents · Meta Ads MCP setup · Approval-gated ad changes · Weekly ecommerce diagnosis workflow · Google Ads MCP setup · Single MCP workspace

Next step

Install MCP today and pass list_connections; run a read-only weekly diagnosis this week before your first approval-gated write.

Connect your agent · Pricing · Quickstart docs