Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://mcp.lazyads.ai/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http ai.lazyads-mcp https://mcp.lazyads.ai/mcpRun in a terminal.
{ "mcpServers": { "ai.lazyads-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.lazyads.ai/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
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 MCP for nine ad networks. BYOA, flat SaaS — no percent of spend, no fake ROAS.
https://mcp.lazyads.ai/mcpDocs: lazyads.ai/mcp
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.
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
skills.sh
npx skills add camerondwills/lazyads-mcp
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 writeFree accounts can onboard and browse competitor ads. Lazy Ads AI tools require Starter or above. REST and outbound webhooks require Growth or above.
See lazyads.ai/pricing. Plans: BYOA, Starter, Growth, Scale, Enterprise. Fixed monthly fee, bring your own ad accounts, not a cut of ad spend.
Documentation in this repo is MIT. Lazy Ads the product remains a separate, private codebase.
© 2026 MCP Directory.
Hosted MCP for nine ad networks. BYOA, flat SaaS — no percent of spend, no fake ROAS.
{ "mcpServers": { "ai.lazyads-mcp": { "url": "https://mcp.lazyads.ai/mcp", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Lazy Ads is reached over HTTP.
Last checked 2026-11-07. Hosted MCP for nine ad networks. BYOA, flat SaaS — no percent of spend, no fake ROAS.