# Ads Lighthouse MCP server

> Review saved Google and Bing brand-search ads, advertisers, affiliate findings and reports from an Ads Lighthouse workspace.

- Listing: https://mcp.tc/i/ads-lighthouse
- Connect: use the server's own URL `https://adslighthouse.com/api/v1/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Marketing & SEO](https://mcp.tc/c/marketing-seo)
- Vendor: Ads Lighthouse
- Homepage: <https://adslighthouse.com/>

## About

Connects an AI assistant to an Ads Lighthouse workspace. Ads Lighthouse monitors brand searches on Google and Bing and saves the ads that appear, so you can review who advertises on your brand, spot affiliate IDs and read reports.

The server is hosted at a Streamable HTTP endpoint and uses OAuth 2.1 with PKCE for sign-in. An Ads Lighthouse account is needed, and MCP access is stated to be included in every paid plan and trial.

## What it can do

- Review saved Google and Bing brand-search ads
- Look up advertisers appearing on brand searches
- Check affiliate findings
- Read workspace reports

## Example prompts

- "Show the latest ads that appeared on my brand searches."
- "Which advertisers bid on my brand this week?"
- "Summarize affiliate findings from my Ads Lighthouse workspace."
- "Pull the most recent Ads Lighthouse report."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

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

2. Start Claude Code, type `/mcp`, pick **ads-lighthouse** and choose **Authenticate**. A browser window opens for the Ads Lighthouse sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Ads Lighthouse** and paste this URL:

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

3. Click **Add**, then **Connect**, and sign in when Ads Lighthouse asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Ads%20Lighthouse&connectorUrl=https%3A%2F%2Fadslighthouse.com%2Fapi%2Fv1%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://adslighthouse.com/api/v1/mcp` and click **Add**.

3. Click **Connect** and sign in when Ads Lighthouse asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://adslighthouse.com/api/v1/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Ads Lighthouse to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=ads-lighthouse&config=eyJ1cmwiOiJodHRwczovL2Fkc2xpZ2h0aG91c2UuY29tL2FwaS92MS9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

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

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=ads-lighthouse&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fadslighthouse.com%2Fapi%2Fv1%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"ads-lighthouse","type":"http","url":"https://adslighthouse.com/api/v1/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

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

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

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

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

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

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.ads-lighthouse]
url = "https://adslighthouse.com/api/v1/mcp"
```

### Gemini CLI

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

Then, inside Gemini CLI, run `/mcp auth ads-lighthouse` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

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

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://adslighthouse.com/api/v1/mcp`.

## Details

- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-10-11
- Updated: 2026-10-11

---
Source: https://mcp.tc/i/ads-lighthouse (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
