Using AdsCove in Gemini CLI
AdsCove Product & Engineering · Last reviewed July 10, 2026
Available · MCP
Gemini CLI supports remote MCP over HTTP. Add AdsCove to its settings with the httpUrl key and a Bearer header.
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 (option A): HTTP header Authorization: Bearer sk_live_your_key (key from console -> Keys)
Auth (option B): OAuth 2.1 (if the client supports remote-MCP OAuth; no key needed)
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
- Edit ~/.gemini/settings.json, add the block below (create the file if missing)
- Restart gemini; run /mcp to see the server and its tools
{
"mcpServers": {
"adscove": {
"httpUrl": "https://adscove.com/api/mcp",
"headers": { "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. Replace sk_live_MY_KEY with the key you generated.
Configure Gemini CLI to use the AdsCove MCP server: edit ~/.gemini/settings.json and add under mcpServers a server named 'adscove' with "httpUrl": "https://adscove.com/api/mcp" and header Authorization: Bearer sk_live_MY_KEY. Restart, then run /mcp and call list_connections.
Verify
Run /mcp to list tools, then ask: "check my platform connection status".
What you can do once connected
Check the business report, compare platform ROAS against real Shopify orders, create paused ad drafts, submit budget changes — every write needs your confirmation. Try: “Which ads lost money in the last 7 days?”
Get started