Upfixe is the autonomous PPC engine built for AI agents. With Upfixe's Model Context Protocol (MCP) server, your AI assistant can research keywords, draft responsive search ads, structure ad groups, publish campaigns, and pull cross-network analytics across both Google Ads and Microsoft Advertising (Bing Ads). Features enterprise-grade token encryption (AES-256-GCM) and strict safety guardrails (auto-paused deployments, daily budget caps, O&O syndication filters). Create and manage Google Ads campaigns from chat. Upfixe turns natural-language briefs into budget-aware Google Ads campaigns: Keywords, ad copy, structure, and budget allocation, all drafted as paused campaigns you review in Google Ads before going live. What it does - Analyzes your homepage and landing pages to extract your value proposition - Generates keyword candidates filtered by your daily budget (no keywords you can't afford) - Drafts complete campaigns (keywords + ad copy + structure) as **paused** drafts with a direct Google Ads deep-link for review - Reports on live campaign performance and lets you pause/resume from chat Why it's different Most Google Ads MCPs are read-only analytics tools. Upfixe is write-capable and budget-aware! Built for SMBs who want to launch real campaigns from Claude, not just query existing ones. Setup Sign in with Google during the OAuth flow to connect your Google Ads account. Free 7-day trial. Learn more: https://upfixe.com/mcp
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (2510 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 34 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 55% of peers
- This listing 82 · peer median 81
- Latency
- Faster than 29% of peers
- This listing 514 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/george-mvur/upfixe-ads/mcpcurl -X POST https://server.smithery.ai/george-mvur/upfixe-ads/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'