AdsCove
Log inSign up free

Claude Desktop install

Install AdsCove MCP in Claude Desktop for Ecommerce Ops

Published September 29, 2026 · AdsCove Product & Engineering

Short answer

In Claude Desktop, add a custom connector for the remote MCP—name AdsCove, URL https://adscove.com/api/mcp—then finish OAuth. Connect Shopify / Meta / Google in the AdsCove console and verify with list_connections. Reads can diagnose freely; budget and status writes stay approval-gated. If you also use Cursor, see the combined walkthrough Cursor / Claude ecommerce MCP install; this page is Desktop-first.

Why a Claude Desktop–only guide

The combined guide covers Cursor and Claude together. Desktop users often search “Claude Desktop MCP” and get stuck on the connector UI, OAuth prompts, and whether mobile can create connectors. This page isolates the Desktop path and links back to the combined guide and the approval-gated model.

Before you install

  • An AdsCove account (browser signup is enough).
  • Access to the Shopify store and/or Meta and Google ad accounts you operate.
  • Claude Desktop installed and signed in (custom connectors are usually created on desktop; mobile often reuses them).

Five Claude Desktop steps

  1. Create AdsCove — No local ads Python server, and no platform tokens pasted into chat.
  2. Connect business accounts — In the AdsCove console, connect Shopify (recommended for cash truth), Meta Ads, and Google Ads; confirm account IDs.
  3. Add the custom connector — Claude Desktop → custom connector / MCP: name AdsCove, server URL https://adscove.com/api/mcp, complete browser OAuth. Prefer OAuth; use an AdsCove API key only if the client lacks remote-MCP OAuth (Authorization header in client config—never chat or git).
  4. Verify with list_connections — In a Desktop chat, ask the agent to call list_connections and confirm the expected store and ad accounts.
  5. Read first; gate writes — Start with a 7-day spend vs Shopify or a read-only channel report. Budget/status changes must return a pending execution, then approve / reject workflow.

Desktop troubleshooting

  • OAuth popup blocked: allow the browser to finish auth, then return to Desktop; never paste callback codes into chat.
  • Connector added but tools empty: relaunch Desktop / reconnect MCP, then run list_connections.
  • Mobile: usually reuses a desktop-added connector; new custom MCP connectors generally cannot be created on mobile alone.
  • Broader Cursor + Claude troubleshooting: combined install guide.

Week-one usage

  1. Read-only: list_connections → last-7-day spend and delivery.
  2. Reconcile with weekly ecommerce diagnosis—Shopify cash as store truth.
  3. Draft writes only for objects you name; review the pending execution before approve.

FAQ

Same MCP URL for Claude Desktop and Cursor?

Yes. Both point at https://adscove.com/api/mcp; the difference is how each client adds the connector/server.

Does install mean unsupervised budget changes?

No. Risky writes return a pending execution and need approve_action (or console approval) before they run. See the approval-gated guide.

Should I paste Meta/Google tokens into Desktop?

No. Platform OAuth happens in the AdsCove browser connect flow; Desktop only connects to AdsCove MCP.

How is this different from Claude Code?

Desktop uses the custom-connector UI; Claude Code / CLI follows client docs for remote MCP + OAuth. See /clients/claude and /clients/claude-code.

Related guides