Connect your ad accounts to Claude Code with MCP

Claude Code can work with advertising accounts through an MCP server. Adport supplies the connection to your ad platforms, while Claude reads the results and helps you investigate them. Start by choosing where the server runs, connect the accounts you intend to use, and verify a small report before asking for a campaign change.

By Adport4 min read

Choose hosted or local MCP

With Adport Cloud, connect advertising platforms in your workspace and authorize Claude against that workspace. With the open-source CLI, run Adport on your own machine and bring your own provider application credentials. Both expose advertising tools through MCP; their setup and authorization are different.

The local path requires Node.js 22.13 or newer and provider API access. The hosted path requires an Adport account and an available provider connection in your workspace. Check the platform guide before choosing: a personal social login, an advertising login, and an approved API application can grant different access.

Connect Claude Code to Adport Cloud

  1. Create or select the project for your brand or client.
  2. Connect an advertising platform, save the ad-account selection, and enable agent access for the intended accounts.
  3. Open AI assistants in Adport and use the Claude Code setup.
claude mcp add --transport http --scope user adport https://app.adport.dev/mcp

Open Claude Code, run /mcp, select Adport, and complete browser sign-in for the intended project. Claude Code supports remote HTTP MCP connections and authentication. The command adds the server configuration; account access is verified by a successful read after sign-in.

User scope makes the server configuration available across your local Claude Code projects. Adport authorization determines which advertising project the connection can reach. Switching the project in the dashboard does not silently redirect an existing grant.

Run the open-source server on your machine

Install Adport and connect a provider before registering the local process. Here is the Google Ads example:

npm install -g adport
adport connect google
adport doctor
adport accounts --provider google
claude mcp add --transport stdio adport -- adport mcp

Use the provider identifier from its guide, such as meta, tiktok, or snapchat. Connect additional platforms with their own wizards; the same MCP server can expose the providers whose credentials are configured. Supply credentials through the connection wizard or the documented environment setup.

The local process must be available on Claude Code's PATH. If you already registered a hosted server named Adport, use a different server name for the local connection so you can tell which account source you are querying. Do not overwrite a working configuration without reviewing it.

Verify one account before reviewing the portfolio

Try this prompt
Use Adport to list the connected advertising accounts and their providers. Confirm which project this connection can access. For one account I select, report campaign spend, clicks, and available conversions for the last seven completed days. Show currency and reporting limitations. Make no changes.

Match the returned account ID to the platform dashboard. Check a known campaign and the report period. An empty account list calls for checking authorization and account selection; it does not mean the business has no campaigns. For several providers, keep currencies and conversion definitions separate rather than adding all rows into one total.

Follow the guide for your advertising platform

Use the Google Ads, Meta and Facebook Ads, TikTok Ads, Snapchat Ads, LinkedIn Ads, or Microsoft and Bing Ads guide for the next step.

The integration directory also covers Apple, Reddit, Pinterest, Spotify, and X advertising. Provider support does not mean identical reporting dimensions or campaign operations. Ask Claude to use the capabilities exposed for the connected provider and explain an unsupported request.

Use Claude web or review a campaign change

For Claude web or desktop, follow the custom connector setup in Adport's AI assistants page and use the hosted MCP URL. The local stdio command above is specifically for a client that can launch a local process. Claude documents custom remote MCP connectors; availability also depends on your Claude workspace.

When a read identifies a useful action, request a preview for one exact account and campaign. Review the values and budget effect before approving. Adport applies through a matching pending operation and checks its policy limits. A Free Cloud plan is read-only; a paid plan still follows account permissions and member roles. After applying an approved operation, read back the platform state.

Sources & further reading

Provider documentation for the setup and platform behavior described above.

Start with your own accounts.

Connect your ad accounts, ask a useful question, and review changes before applying them.

Start freeCompare plans