Cursor's agent can call MCP servers as tools. With the VibeAds server added, you can ask it how your Google Ads campaigns are doing, which search terms are burning budget, and what to fix, without leaving the editor. Developers building landing pages and agencies keeping client notes in a repo get the most out of it.
What do I need?
- Cursor, with Node.js 20 or newer installed (Cursor starts the VibeAds package with
npx). - A VibeAds account with Google Ads connected. Reading works on every plan; drafting and publishing need Pro ($20 a month) or Max.
- A VibeAds API key from Settings, MCP Server Keys. It starts with
vba_mcp_and is shown once.
How do I add VibeAds to Cursor?
Add this to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json in one project:
{
"mcpServers": {
"vibeads": {
"command": "npx",
"args": ["-y", "@vibeads/mcp"],
"env": { "VIBEADS_API_KEY": "vba_mcp_YOUR_KEY_HERE" }
}
}
}
Open Cursor's settings, find MCP, and check that vibeads shows as running with its tools listed. Then ask the agent: "Show me my Google Ads campaigns in VibeAds."
If you put the config in a project, keep the key out of version control. Keys can be revoked one at a time in VibeAds, so give each machine its own.
What can I ask Cursor?
- "Which of my campaigns has the highest cost per lead, and what's driving it?"
- "List the search terms with spend and no conversions, as a table."
- "What does Google recommend for my account, and which of those can be applied here?"
- "Draft a campaign for a roofing company in Tampa at $60 a day." (a draft only; nothing goes live)
Is it safe to give Cursor a key to my ad account?
The key can read your campaigns, draft, and make changes that run through VibeAds' safety checks, at up to 60 calls an hour. Publishing a campaign, raising a daily budget, or raising a bid past double or $50 a click comes back as a link you approve in your browser, signed in to VibeAds; the key can't approve it. It never sees your Google login. Revoke it any time in VibeAds Settings, MCP Server Keys.
Troubleshooting
- The server shows as failed. Run
node --version; Cursor needs Node in its PATH to startnpx. - "Missing VibeAds API key". Check the
VIBEADS_API_KEYvalue starts withvba_mcp_. - Answers lack live numbers. Connect Google Ads in VibeAds Settings.
See every tool in the MCP server docs, or the npm package README for other editors.