Lazy Ads MCP
MCP serverDev toolsThis gives your AI access to nine advertising networks through one hosted connection. It works with the ad accounts you already have, and pricing is a flat fee rather than a percentage of what you spend. Once added, your AI can work across all nine networks without separate setup for each one.
Available today. Use it from your connected AI after setup.
Needs your own account with this service. Credentials stay encrypted.
After adding it, connect the ad accounts you already use so your AI can start working with the networks. The source code is available at github.com/camerondwills/lazyads-mcp.
Then ask your AI: use Lazy Ads MCP
What your AI can do with it
- Connect to nine ad networks through a single setup
- Use your existing ad accounts instead of creating new ones
- Work across all nine networks from one place
- Keep costs predictable with flat pricing and no cut of your ad spend
From the project's README
As published by camerondwills/lazyads-mcp in README.md.
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):
{
"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:
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:
mkdir -p ~/.hermes/skills/lazyads
curl -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
What you get
- BYOA: 33 bridge tools to create, update, pause, and measure campaigns on all nine networks
- Starter and above: full suite (47 tools), including 14 Lazy Ads AI tools
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. Flat SaaS, bring your own ad accounts, no percent of spend.
Links
- Site: https://lazyads.ai
- MCP docs: https://lazyads.ai/mcp
- Pricing: https://lazyads.ai/pricing
- Hermes: https://lazyads.ai/hermes
- Blog: https://lazyads.ai/blog
License
Documentation in this repo is MIT. Lazy Ads the product remains a separate, private codebase.
Signals
- Last commit
- Sep 2026
Advanced
- Delivery
- mcp MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
- Catalog kind
- mcp-server
- Gateway key
ai-lazyads-mcp- Source
- github.com/camerondwills/lazyads-mcp
- Hosted endpoint
https://mcp.lazyads.ai/mcp