Using AdsCove in Any MCP client

AdsCove Product & Engineering · Last reviewed August 5, 2026

Available · MCP

Any tool that speaks remote MCP (Streamable HTTP) can connect — WorkBuddy, Cline, Continue, Zed, Goose, or your own agent. There are only two facts that matter: the endpoint URL and a Bearer auth header. Everything else is client-specific config. If you don't know where your client keeps MCP servers, paste the agent block below into the client itself.

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

Generate an API key on the console Keys page
In your client's MCP config, add a Streamable HTTP server pointing at the endpoint with the Bearer header
Reload the client and call list_connections

{
  "mcpServers": {
    "adscove": {
      "url": "https://adscove.com/api/mcp",
      "headers": { "Authorization": "Bearer sk_live_your_key" }
    }
  }
}

The two facts, in case your client's format differs

URL:    https://adscove.com/api/mcp   (Streamable HTTP)
Header: Authorization: Bearer sk_live_your_key

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.

Please connect me to the AdsCove MCP server in the tool I am currently using.

Details you need:
- MCP server name: adscove
- Endpoint URL: https://adscove.com/api/mcp
- Transport: Streamable HTTP (remote MCP)
- Authentication: prefer remote MCP OAuth 2.1. Do not ask me to paste a token into chat.
- Fallback: only if this client cannot use remote MCP OAuth, direct me to create an AdsCove API key and explain where to put it securely.

Steps:
1. Find where THIS client stores its MCP server configuration (its mcp.json / settings file, or an "Add MCP server" UI).
2. Add the "adscove" server above and start its Authenticate or OAuth action.
3. Give me the authorization URL if the browser does not open automatically.
4. Reload or restart the client if needed.
5. Call the tool "list_connections" and show me the result to confirm it works.

Verify

Call the tool list_connections — it should return your platform connections.

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