Connect another MCP client.

Use this guide if your AI client is not listed in the setup overview. The client must support a remote MCP server over Streamable HTTP, plus either MCP OAuth or a custom authorization header. MCP support limited to local commands is not enough for this direct connection.

Before you begin

You need an Ad Superpowers account with an active trial or paid subscription. Create an account if needed; see pricing for current access and limits.

Select the intended workspace in the dashboard and connect a platform in Integrations. Check your client's own documentation for its remote MCP and authentication settings.

1. Add the connection

In your client's MCP server settings, add a remote server with these values:

The configuration field names differ between clients. Use your client's schema; a field named url in one client may mean a different transport in another.

2. Authenticate

If your client supports MCP OAuth, choose its sign-in or authorization action. Complete the Ad Superpowers browser flow and check the workspace before approving access.

If your client supports custom HTTP headers, create an API key in the intended workspace's API Keys. Configure this header, replacing the placeholder in the client's private connection settings:

Authorization: Bearer YOUR_API_KEY

If the client asks for a Bearer token rather than a full header, enter only the key. Save the connection and reload its available tools. Keep keys out of chat messages.

3. Check the result

Ask the client:

List the advertising accounts I can access through Ad Superpowers.
Do not change anything.

Confirm the intended account appears, then ask:

For [account name and ID], show campaign spend and conversions
for the last 7 days. Include the date range and currency.
Do not change any campaigns.

Check that the response came from a tool call, then compare the account, dates and currency with the platform. Tool discovery by itself does not prove access to your advertising data.

If the connection fails

• No remote URL or header settings: check whether this client supports the required transport and authentication. Use a documented client if it does not.
• Authentication fails: repeat the OAuth flow, or check the key and header. Confirm trial or paid access in Ad Superpowers.
• Tools are missing after adding a platform: reload the server connection in your client.
• Tools work but the account is missing: check the platform connection and the workspace used for authorization. For a key connection, use a key from the intended workspace. Continue with troubleshooting.

Next steps

Browse example questions and the tool reference. For clients with their own guide, use the setup overview for the exact menu and configuration instructions.