Remote Model Context Protocol (MCP) server for campaign planning, research, and cross-platform ad creation. Supports Google Ads Search & Performance Max and TikTok at launch, with additional networks planned.

• MCP Remote URL (SSE): https://mcp.adspirer.com/
• Fallback URL: https://adspirer-mcp-596892545013.us-central1.run.app/
• Registry ID: com.adspirer/ads
• Authentication: OAuth 2.1 via Adspirer (paid tiers and rate limits enforced server-side)
• Website: https://www.adspirer.com/
• Support: abhi@adspirer.com

• Plan and validate campaigns using structured prompts
• Generate creative variants and assemble compliant asset bundles
• Create Google Ads Search and Performance Max campaigns, and TikTok campaigns, end-to-end from within MCP-capable clients
• Real-time progress updates for long-running operations (5-30 seconds)

• help_user_upload — Returns clear instructions for providing direct media links suitable for ingestion
• validate_and_prepare_assets — Downloads and validates media from provided URLs; returns an asset_bundle_id. Streams progress when supported by the client (typically 5-15 seconds for 5-10 images)

• create_pmax_campaign — Atomic PMax creation (uses validate-then-commit pattern). Streams progress when supported (typically 15-30 seconds)
• create_search_campaign — Text-first Search campaign creation with optional assets

1. Open Settings → Connectors → Create
2. Name: Ads MCP
3. URL: https://mcp.adspirer.com/
4. Follow OAuth 2.1 sign-in; you will see Adspirer as the application
5. Link your ad accounts on first use
6. Use tools by asking naturally (e.g., "create a PMAX campaign for...")

1. Open Settings → Connectors → Add custom
2. Name: Ads MCP
3. URL: https://mcp.adspirer.com/
4. Complete OAuth 2.1 sign-in
5. Invoke tools as needed

• Protocol version negotiation with clients
• Real-time progress updates via notifications/progress
• Deterministic progress fields: stage, current, total, message
• Works with clients that request _meta.progressToken

• HTTPS URLs only; redirect cap applied
• Private and non-routable destinations blocked
• MIME sniffing and content-type checks enforced
• OAuth 2.1 access tokens validated per request
• Least-privilege scopes applied per operation

• Server-side rate limits vary by paid tier
• Time and size limits enforced per operation
• Image download retry logic (2 attempts on 404)
• User-Agent header for CDN compatibility
• See pricing and terms at https://www.adspirer.com/

• Quickstart Guide
• ChatGPT Connector Setup
• Claude Connector Setup
• Troubleshooting
• Changelog

• Protocol: MCP 2025-03-26 (with fallback to 2024-11-05)
• Transport: HTTP+SSE with progress streaming
• OAuth: RFC 8252 (Authorization Code + PKCE) with RFC 9728 (Protected Resource Metadata)
• Progress: Sparse status messages even without progress token
• Monitoring: Comprehensive logging with token usage and duration metrics

curl -i -N https://mcp.adspirer.com/mcp/tools/call \
  -H 'Content-Type: application/json' \
  -d '{
    "jsonrpc":"2.0",
    "id":2,
    "method":"tools/call",
    "params":{
      "name":"validate_and_prepare_assets",
      "_meta":{"progressToken":"tok-123"},
      "arguments":{
        "marketing_images_square":["https://example.com/image.jpg"]
      }
    }
  }'

You should see several event: message progress frames followed by a final JSON-RPC result on the same stream.

• Email: abhi@adspirer.com
• Website: https://www.adspirer.com/
• Issues: https://github.com/adspirer/ads-mcp/issues

See SECURITY.md for vulnerability reporting and security policies.

Proprietary - See website for terms of service