Ads Lighthouse MCP

io.github.estevecastellsPublished by GitHub account estevecastellsv1.0.0Updated Oct 24, 2026

Access saved Google and Bing brand-search ad observations and reports through Ads Lighthouse.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that gives an assistant access to saved Google and Bing brand-search ad observations and reports from Ads Lighthouse.

What you can do
  • Retrieve saved brand-search ad observations collected from Google and Bing.
  • Access reports built from those observations.
  • No tool list is published, so the exact operations are not documented in the provided material.
When to use it
Useful when you already work with Ads Lighthouse and want an assistant to pull your saved brand-search ad observations and reports into a conversation, for example to review or discuss them.
Requirements
A remote endpoint at adslighthouse.com over streamable HTTP; no local package or runtime is needed. Authentication is OAuth and is required, so an Ads Lighthouse account is implied.
Before you install
The server requires OAuth sign-in, so the assistant will act with the permissions you grant to your Ads Lighthouse account. No tool list is published, so what it can read or change cannot be verified from the provided material; review the granted scopes before connecting.

Installation

In SourceWeft

  1. Open Ads Lighthouse MCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.estevecastells%2Fads-lighthouse/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 12, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.