AdLemur
Back to Docs

AdLemur MCP

Connect an AI client to project-scoped AdLemur advertising workflows.

AdLemur MCP

AdLemur exposes sourced competitor-ad research, paid-keyword snapshots, creative analysis, owned-performance reporting, and gated ad-account changes to MCP clients.

The hosted MCP resource currently remains:

https://app.openseo.so/mcp

That hostname is an inherited client-compatibility identifier. It is not the AdLemur product website, and changing it requires a versioned OAuth/resource migration.

Advertising tools

  • list_competitors: read the project's monitored competitors.
  • search_ads: search stored competitor ads with source coverage.
  • get_ad: inspect one ad's observations and changes.
  • list_ad_changes: read recent stored changes.
  • research_paid_keywords: read the latest stored competitor snapshot.
  • analyze_creatives: run paid creative analysis on saved evidence.
  • create_ad_brief: update a stored brief without a provider call.
  • get_owned_performance: read first-party reporting scopes.
  • get_creative_lineage: relate reviewed creative to owned results.
  • update_owned_ad: pause, activate, or change the daily budget of a supported owned ad entity.
  • create_owned_campaign: create a non-delivering traffic campaign from a stored AdLemur creative.

Every project-scoped call authorizes the requested project before reaching an application service. Responses include useful text and structured data with evidence references, classification, coverage, cost context, and inspection links where applicable. Owned-performance reads remain read-only. Provider writes support Google, Meta, TikTok, and LinkedIn when the deployment switch, project setting, aggregate budget ceiling, and provider write access are in place. AdLemur limits non-UI writes to 20 attempts per project per hour. MCP clients are instructed to obtain approval for the exact change; external MCP approval is enforced by the connected client rather than an AdLemur approval screen. Provider deletes are unsupported.

Campaign creation is also held behind the separate OWNED_AD_CAMPAIGN_CREATION_ENABLED deployment flag. Keep it disabled until controlled live-provider creation has passed for every provider you expose.

Stored reads and brief updates use no provider credits. Refresh and generation workflows may consume provider or model credits. AdLemur asks for confirmation before a planned paid batch above 2,000 credits.

Connect

Use the Connect an agent page in your own AdLemur deployment to copy its endpoint and OAuth or API-key setup. Do not copy a hosted hostname into a self-hosted setup.

For the inherited hosted resource, clients that support remote OAuth can use:

claude mcp add --transport http --scope user openads https://app.openseo.so/mcp

The first connection opens login and authorization. API keys remain available for clients that cannot complete OAuth. Existing oseo_ key prefixes remain valid as a credential compatibility detail; never place a key in a checked-in configuration file.

Report setup problems at jamalavedra/openads issues.