Meta Ads MCP Server Setup for AI Clients

Install

Pick your client

The same hosted URL works for all of them. OAuth sign-in uses your Adship account, so no Meta access token is copied into the AI client.

Claude Desktop Recommended

Open Settings → Connectors → Add custom connector and paste:

Name: Adship URL: https://mcp.adship.ai/mcp

Claude Code

One command. After install, run /mcp in Claude Code to trigger OAuth.

claude mcp add --transport http adship https://mcp.adship.ai/mcp

Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):

{ "mcpServers": { "adship": { "type": "streamable-http", "url": "https://mcp.adship.ai/mcp" } } }

ChatGPT connectors

Add a remote MCP connector, paste the hosted endpoint, and authenticate with Adship OAuth.

Name: Adship URL: https://mcp.adship.ai/mcp

Claude Desktop (legacy / corp proxy)

For older builds without Custom Connectors. Edit claude_desktop_config.json:

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

First-run authentication

Sign in once, tokens refresh

The first tool call opens an OAuth window. You sign in to Adship, pick the workspace the agent can access, and approve scopes. Tokens last 24 hours and refresh automatically.

Agent makes its first tool call → server returns 401 with OAuth metadata.

Agent opens the Adship authorize page in your browser.

You sign in (Google / Facebook / email), pick a workspace, click Allow.

Agent receives an audience-bound JWT (24h, refreshable, PKCE).

Tools work immediately.

Scopes & permissions

Granular, per-platform, revocable

The agent requests scopes; you approve them on the consent screen. Revoke access at any time from Adship → Settings → AI Agents.

read:meta

List Meta campaigns, ad sets, ads, creatives & read metrics.

write:meta

Pause / enable / budget / publish ads on Meta.

read:tiktok

List TikTok campaigns, ad groups, ads & read metrics.

write:tiktok

Pause / enable / budget ads on TikTok.

🔒

An agent can never widen its own access. The token is minted with only the scopes you approve, intersected with what the client registered.

Every tool re-checks its scope server-side on each call. A read:meta token cannot pause an ad, touch TikTok, or read your Google Drive. Viewer team members can only obtain read:*; write scopes are stripped at mint, even if requested.

Write and destructive annotations let compatible clients surface approval. Adship also checks the workspace and ad account boundary. Creative edits default to dry-run and deletion needs a second confirmation, but not every write defaults to dry-run.

Tools (v1)

Registered tools across the ad workflow

The MCP server manages Meta and TikTok ad accounts. Google Drive and Sheets can provide source material, but Google Ads account management is not supported.

🏢 Account overview

get_account_overview
list_ad_accounts
get_workspace_settings

📋 Campaigns, ad sets, ads

list_campaigns
list_ad_sets
list_ads
create_campaign
duplicate_campaign
delete_entities

📊 Insights and audits

get_ad_metrics
get_insights_breakdown
get_budget_pacing
run_full_account_audit

🛡️ Budget and status changes with approval

update_budget
update_status
pause_ad
enable_ad

🎨 Creatives and bulk publish

get_creative_brief
generate_ad_copy
edit_ad_creative
upload_creative
bulk_publish

💬 Comments

list_comments
get_comment_analytics
reply_to_comment
hide_comment
list_conversations

🔭 Competitor and Ad Spy

scrape_meta_ads_library
analyze_competitor
discover_competitors
compare_competitors

⚙️ Automation rules

list_ad_rules
create_ad_rule
delete_ad_rule
list_recommendations

🎵 TikTok Ads

list_tiktok_identities
create_tiktok_campaign
bulk_publish_tiktok
update_budget
update_status

Adship Meta Ads MCP Server