Hosting

Remote, hosted

Transport

Streamable HTTP

Endpoint

https://mcp.adspirer.com/mcp

Authentication

OAuth 2.1 with PKCE, as documented by the maintained Ads MCP project.

Requirements

• A compatible MCP client
• Adspirer account and OAuth sign-in
• Connected advertising accounts for platform-specific operations

Setup steps

1. Add https://mcp.adspirer.com/mcp as a remote MCP server.
2. Complete OAuth sign-in in the browser.
3. Connect the relevant ad platforms in the Adspirer account.

Crawl4AI verified these three identifiers in the maintainer connection guide. The repository advertises 100+ tools and the guide references a 341-tool catalog, so this is a partial helper-tool list, not a full inventory.

• list_connected_accounts

  List connected advertising accounts; Adspirer connection guidance instructs the client to call this first and use returned account IDs.

  01
• get_connections_status

  Check whether Adspirer advertising platform connections are working.

  02
• echo_test

  Run a lightweight connectivity test for the Adspirer tool layer.

  03

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Legacy Adspirer MCP repository is superseded. Current Ads MCP documentation lists Google Ads and TikTok Ads features; do not conflate this entry with Adspirer’s separately marketed paid-media agent product.

• official publisher documentation

  Maintainer connection guide documents hosted URL and supported clients/auth setup.

• official publisher documentation

  Legacy repository explicitly says it is superseded by Ads MCP.

• maintainer documentation

  Publisher or maintainer documentation reviewed 2026-10-28T19:30:00.000Z; capability and connection information recorded, with exact protocol tool identifiers added only when the source publishes them.

Documentation checked 2026-10-29T00:00:00Z. Connection has not been runtime tested.