Claude Desktop

Connect AdsSyncs to Claude Desktop (macOS / Windows). One command, then a restart.

Install

npx -y @adsyncs/mcp-install claude

Then fully quit Claude Desktop and reopen it. Tools prefixed google_ads_*, meta_ads_*, linkedin_ads_*, and bing_ads_* will appear in the tool picker.

Connect your ad accounts

The MCP server doesn't ship credentials. Provider OAuth happens in our dashboard:

Visit app.adsyncs.net and sign in.
Open Connections and start the OAuth flow for each provider you use (Google, Meta, LinkedIn, Bing).
Pick the ad accounts the AI is allowed to see.

Once connected, accounts show up in Claude the next time you call a tool such as linkedin_ads_list_accounts — no second restart needed.

Manual install

If npx is not available, paste this into claude_desktop_config.json:

{
  "mcpServers": {
    "adsyncs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.adsyncs.net/mcp"]
    }
  }
}

Then quit and reopen Claude Desktop.

The config file lives at:

macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
Windows — %APPDATA%\Claude\claude_desktop_config.json

Troubleshooting

No tools appear

Check Claude's MCP log (~/Library/Logs/Claude/mcp.log on macOS) and confirm an mcpServers.adsyncs entry exists in the config file. Re-run the installer with --force if the entry is stale.

auth_required from a tool — your workspace is missing a connection for that provider. Add it in app.adsyncs.net/connections.
Need a different config key — pass --name <key> to the installer.
"Refresh token expired" — re-authorize the platform in the dashboard. We don't store passwords; we can't refresh silently if the platform revoked the token.

Uninstall

npx -y @adsyncs/mcp-install claude --uninstall

Quit and reopen Claude Desktop. The MCP entry will be gone.