Lazy Ads

ai.lazyadsPublished by lazyads.aiOfficial publisherv2.0.0Updated Oct 24, 2026

Hosted MCP for nine ad networks. BYOA, flat SaaS — no percent of spend, no fake ROAS.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Hosted MCP server that lets an assistant create, update, pause, and measure ad campaigns across nine advertising networks.

What you can do
Connects an MCP client to Lazy Ads ad accounts on nine networks: Meta (Facebook and Instagram), Google, TikTok, LinkedIn, Reddit, Apple, Bing, ChatGPT, and Snapchat. It exposes bridge tools to create, update, pause, and measure campaigns, including account signals, conversion events, and audience creation. Post-create edits such as update_ad and update_ad_set write to both Lazy Ads and the live platform when supported, and fail rather than silently writing only to the database. Higher plans add Lazy Ads AI tools, REST access, and outbound webhooks.
When to use it
Use it when an assistant should manage or report on paid campaigns across several ad networks from one connection, rather than logging into each platform separately. It suits teams already using Lazy Ads on a paid plan who want campaign creation, edits, and measurement driven from an MCP client.
Requirements
A remote MCP endpoint over Streamable HTTP; no local package or runtime is needed. An API key from Lazy Ads Settings, API on any paid plan, sent as an Authorization Bearer token (X-API-Key is also accepted). Client configuration differs by tool, and Claude Desktop needs a local bridge such as mcp-remote. Network access to the hosted endpoint is required.
Before you install
The Authorization header carries a secret API key; store it in client configuration or an environment variable rather than sharing it. Tools can create, update, and pause live campaigns and write to connected ad platforms, so changes may affect real ad spend. Some capabilities, including Lazy Ads AI tools, REST, and webhooks, require higher plan tiers.

Installation

In SourceWeft

  1. Open Lazy Ads in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/ai.lazyads%2Fmcp/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.

{
  "mcpServers": {
    "lazy-ads": {
      "type": "http",
      "url": "https://mcp.lazyads.ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Lazy Ads MCP

Public listing for the Lazy Ads MCP server.

Connect Claude, Cursor, Hermes, and any MCP-compatible client to your ad accounts across nine networks: Meta (Facebook + Instagram), Google, TikTok, LinkedIn, Reddit, Apple, Bing, ChatGPT, and Snapchat.

This repository is documentation only. It does not contain product source code.

Hosted endpoint

  • URL: https://mcp.lazyads.ai/mcp
  • Protocol: MCP 2026-07-28 Streamable HTTP
  • Auth: API key from Lazy Ads → Settings → API (any paid plan)

Docs: lazyads.ai/mcp

Connect your client (lazyads.ai/mcp#setup)

Cursor (.cursor/mcp.json) and Claude Code (.mcp.json):

json
{  "mcpServers": {    "lazyads": {      "url": "https://mcp.lazyads.ai/mcp",      "headers": { "Authorization": "Bearer la_your_api_key" }    }  }}

Claude Code one-liner: claude mcp add --transport http lazyads https://mcp.lazyads.ai/mcp --header "Authorization: Bearer la_your_api_key"

Windsurf uses serverUrl instead of url. Gemini CLI uses httpUrl. VS Code uses servers with "type": "http". Codex CLI reads [mcp_servers.lazyads] with url and bearer_token_env_var = "LAZY_ADS_API_KEY" from ~/.codex/config.toml. Claude Desktop only launches local processes, so bridge it with mcp-remote and put the header in env. Copy-ready blocks for every client: https://lazyads.ai/mcp#setup

X-API-Key is also accepted.

Connect (Hermes)

Store the key in ~/.hermes/.env as LAZY_ADS_API_KEY=la_..., then:

yaml
mcp_servers:  lazyads:    url: "https://mcp.lazyads.ai/mcp"    headers:      Authorization: "Bearer ${LAZY_ADS_API_KEY}"    description: "LazyAds MCP. 9-platform ad management"

Install the skill:

bash
mkdir -p ~/.hermes/skills/lazyadscurl -fsSL https://raw.githubusercontent.com/camerondwills/lazyads-mcp/main/SKILL.md \  -o ~/.hermes/skills/lazyads/SKILL.md

Hermes skill: SKILL.md in this repo, or the live guide at lazyads.ai/hermes

skills.sh

bash
npx skills add camerondwills/lazyads-mcp

What you get

  • BYOA: 39 bridge tools to create, update, pause, and measure campaigns on all nine networks — including account signals, conversion events, and audience creation
  • Starter and above: full suite (53 tools), including 14 Lazy Ads AI tools
  • Post-create edits: update_ad (copy, destination URL, Meta url_tags) and update_ad_set (name, end date) write Lazy Ads and the live platform when supported, and fail instead of a silent DB-only write

Free accounts can onboard and browse competitor ads. Lazy Ads AI tools require Starter or above. REST and outbound webhooks require Growth or above.

Pricing

See lazyads.ai/pricing. Plans: BYOA, Starter, Growth, Scale, Enterprise. Fixed monthly fee, bring your own ad accounts, not a cut of ad spend.

Links

License

Documentation in this repo is MIT. Lazy Ads the product remains a separate, private codebase.

Source: README.md at commit 84063aa

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

85% 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
  • License10 pts