# Connect AdsCove to an AI agent

AdsCove is a remote Model Context Protocol server for Shopify, Meta Ads, Google Ads, and TikTok Ads operations.

## Connection

- MCP server: https://adscove.com/api/mcp
- Transport: Streamable HTTP
- Authentication: OAuth 2.1 with PKCE
- OAuth discovery: https://adscove.com/.well-known/oauth-authorization-server
- Protected resource metadata: https://adscove.com/.well-known/oauth-protected-resource/api/mcp

## Required procedure

1. Add the MCP server as a remote Streamable HTTP server named `adscove`.
2. Prefer OAuth. Do not ask the user to paste an API key, access token, refresh token, password, or platform credential into chat.
3. If the client returns an authorization URL, give that URL to the user and ask them to approve access in the browser.
4. Do not claim the connection succeeded until the MCP client reports that AdsCove is connected.
5. Call `list_connections` after installation. Summarize which Shopify, Meta, Google, or TikTok connections are ready and which still need attention.
6. If business accounts are missing, direct the user to https://adscove.com/connections after they sign in.

## Client examples

### Codex

```bash
codex mcp add adscove --url https://adscove.com/api/mcp
codex mcp login adscove
```

### Claude web or desktop with custom connectors

Add a custom connector with this URL, then choose Authenticate:

```
https://adscove.com/api/mcp
```

### Other MCP clients

Add a remote Streamable HTTP server named `adscove` with the URL above. Use the client's OAuth or Authenticate action. If the client cannot add remote MCP servers automatically, explain the exact manual UI or configuration step instead of claiming installation is complete.

## API-key fallback

Use an AdsCove API key only when the MCP client does not support OAuth. The user creates and manages keys at https://adscove.com/keys. Never ask them to paste a platform credential such as a Meta, Google, Shopify, or TikTok token.

## Safety

- Read operations can run immediately after authorization.
- Write operations remain subject to AdsCove confirmation, approval, plan, and quota controls.
- Never bypass an approval step or imply that a draft changed a live account.
- Verify the result of every write and report the final status to the user.