Ads Lighthouse MCP

The Ads Lighthouse MCP server allows AI assistants to access saved Google and Bing brand-search ad observations and reports. It provides tools to query projects, keywords, saved checks, and various reports including advertiser, Shopping, affiliate, policy, redirect, and alert data. It supports analytics with chart aggregates and active keyword counts, enabling users to monitor brand protection, affiliate compliance, and PPC competition through natural language queries.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-19Operated by Ads Lighthouse

MCP endpoint (Streamable HTTP)

https://adslighthouse.com/api/v1/mcp

Vendor documentation

What you can do with it

Identify who advertised on brand terms in a specific region and time frame
Find affiliate IDs associated with brand-search ads
Monitor changes in mobile ad performance since a specific date
Check advertiser and policy reports for brand protection

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http ads-lighthouse-mcp https://adslighthouse.com/api/v1/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add ads-lighthouse-mcp --url https://adslighthouse.com/api/v1/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable ads-lighthouse-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "ads-lighthouse-mcp": {
      "url": "https://adslighthouse.com/api/v1/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "ads-lighthouse-mcp": {
      "type": "streamableHttp",
      "url": "https://adslighthouse.com/api/v1/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start ads-lighthouse-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "ads-lighthouse-mcp": {
      "type": "http",
      "url": "https://adslighthouse.com/api/v1/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http ads-lighthouse-mcp https://adslighthouse.com/api/v1/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "ads-lighthouse-mcp": {
      "url": "https://adslighthouse.com/api/v1/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "ads-lighthouse-mcp": {
      "serverUrl": "https://adslighthouse.com/api/v1/mcp"
    }
  }
}

Ground your agent in cited data

Ads Lighthouse MCP gives your agent tools. Koskamo gives it reviewed, cited facts to check its answers against. Add it as a second MCP server; public reads need no API key.

Connect Koskamo Browse datasets

See all 1,050

Do you run Ads Lighthouse MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing