Ad Sniper
io.github.Evozim/ad-sniper is a MCP server that optimizes Google and Meta ad campaign bidding for AI-driven paid distribution.
About
io.github.Evozim/ad-sniper is a remote Model Context Protocol server branded Ad-Sniper that helps AI agents optimize bidding on Google and Meta advertising campaigns. founders launching SaaS, ecommerce, or content products use it when they are actively spending on paid channels and want Claude Code or Cursor to propose or execute bid changes through a single MCP surface rather than copying screenshots between ad managers. Register the SSE endpoint, provide the payment signature when premium settlement is required, and ground prompts with campaign IDs, budgets, and performance targets from your Launch checklist. The server compresses cross-platform bid tuning into agent tools so you can iterate faster during early distribution pushes. It is an optimization MCP layer, not creative strategy, landing-page CRO, or account provisioning inside Google or Meta.
- Ad-Sniper MCP optimizes bidding across Google and Meta campaigns
- Hosted SSE remote on Vercel with optional premium `payment-signature` header
- Agent-oriented workflow for campaign bid adjustments instead of manual Ads UI hopping
- Fits indie founders running their own performance marketing stacks
- Official listing io.github.Evozim/ad-sniper with schema version 1.0.0
Ad Sniper by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport sse ad-sniper https://ad-sniper-mcp.vercel.app/api/mcp --header "payment-signature: YOUR_PAYMENT_SIGNATURE"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | SSE |
|---|---|
| Auth | Required |
What it does
Tune Google and Meta campaign bids from the agent while you scale paid acquisition after the product is ready to promote.
Who is it for?
Best when you're shipping a product and already run Google or Meta ads and want agent-assisted bid tuning via MCP.
Skip if: Organic-only launch plans, teams without ad accounts, or developers who cannot use paid remote MCP with signature headers.
What you get
After connecting the remote MCP server, your agent can drive bid optimization workflows on Google and Meta from the same coding environment.
- Agent-invokable Google and Meta bid optimization surface
- Centralized remote MCP config for paid launch experiments
- Repeatable bid-tuning prompts tied to campaign performance goals
By the numbers
- Targets Google and Meta ad campaign bidding
- Remote SSE at ad-sniper-mcp.vercel.app/api/mcp
- Version 1.0.0 with premium EIP-3009 payment-signature support
Recommended MCP Servers
$THREE TokenPrice, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token.89
402 McpAI agents discover, pay for, and consume any Lightning-gated API autonomously
9192 Public ComputeRemote MCP for 9192 discovery, pricebook, payment rails, GET_PULSE quotes, and receipt checks.
Aarna McpAarna - 34 tools for swap quotes, liquidity pools, and trading dataAave McpAave - 6 tools for lending rates, supply, and borrow data
AbraFlexiMCP server for AbraFlexi ERP — invoices, contacts, products, bank transactions.1How it compares
Paid ads bid optimizer MCP, not an SEO content skill or creative ad generator.
FAQ
Who is io.github.Evozim/ad-sniper for?
Developers and small growth teams using MCP agents to manage Google and Meta campaign bidding during launch.
When should I use io.github.Evozim/ad-sniper?
Use it in Launch when campaigns are live and you need faster, agent-callable bid optimization across Google and Meta.
How do I add io.github.Evozim/ad-sniper to my agent?
Add SSE remote `https://ad-sniper-mcp.vercel.app/api/mcp` to MCP config and set the secret `payment-signature` header when premium settlement applies.