Using AdsCove in Windsurf
AdsCove Product & Engineering · Last reviewed August 5, 2026
Available · MCP
Windsurf's Cascade Agent connects via the same standard MCP config. Note Windsurf uses the key serverUrl.
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
- Edit ~/.codeium/windsurf/mcp_config.json, add the block below
- Restart Windsurf
{
"mcpServers": {
"adscove": {
"serverUrl": "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.
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
In Cascade, say: "check my platform connection status".
Windsurf MCP config troubleshooting
Where is the Windsurf MCP config file?
Windsurf reads MCP servers from ~/.codeium/windsurf/mcp_config.json. You can edit that file directly or open it from Windsurf's MCP settings in Cascade; menu labels can change between Windsurf versions.
Should the key be url or serverUrl?
Use serverUrl for AdsCove in Windsurf, as in the block above. A block copied from Cursor or another client that uses url may not connect in Windsurf.
Windsurf is stuck connecting to the server. How do I fix it?
Check that mcp_config.json is valid JSON (no trailing commas), that serverUrl is exactly https://adscove.com/api/mcp, and that the Authorization header contains the full key after Bearer. Save the file, refresh the MCP servers in Cascade or restart Windsurf, and confirm your network or proxy allows adscove.com.
How do I check that the AdsCove MCP server works in Windsurf?
In Cascade, ask it to check your platform connection status. That calls list_connections, which is free and read-only, and lists the platforms you have connected.
Is it safe to keep my API key in mcp_config.json?
The file is stored on your computer in plain text, so do not commit it to a repository or share it. If a key is exposed, revoke it on the AdsCove Keys page and create a new one.
Can Cascade change my ads through AdsCove?
Reads run directly. Writes such as budget or status changes come back as pending actions that you approve or reject, so nothing is published 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