Run your ads from Cursor.

What this actually is

Cursor speaks MCP, so it can call tools from outside servers the same way it calls its own. Muze is an MCP server for paid media. Once it is added, the tool list Cursor can reach grows by 149: Meta Ads at 37, Google Ads at 41, Amazon Ads at 48, Shopify at 15, and 8 cross-platform tools.

This is not a coding feature that happens to touch ads. The tools are account operations: create_meta_campaign, launch_google_search, update_amazon_keyword_bid, list_amazon_search_terms, get_blended_performance. What Cursor adds is that the ad account becomes queryable from the same window as the landing page you are editing, which is where a surprising amount of growth work already happens.

Who this is actually for

Technical founders and growth engineers, mostly. The person who ships the pricing page change and then wants to know within the hour whether the Google Search campaign pointed at it is converting any better. Switching to Ads Manager for that is a context switch with a tab-hunt attached.

It also suits anyone who wants Muze to be checkable rather than magical. Cursor shows you the tool call and its arguments before it runs. You can watch it decide to call get_google_performance with a specific customer ID and date range, and you can tell when it has picked the wrong account. That transparency matters more when the tool has write access than when it is generating a component.

How connecting works

You need a Muze account with at least one connected ad or commerce account. Cursor can be pointed at Muze with a one-click install link or by adding the server yourself in settings.

1. Create a Muze account and authorize your accounts. Sign up for Muze and connect Meta Ads, Google Ads, Amazon Ads or Shopify over OAuth. Muze never asks for platform passwords and there is no developer application to file.
2. Add Muze to Cursor. Use the Add to Cursor install link on the Muze MCP page, which hands the connector straight to Cursor's MCP configuration. Alternatively open Cursor Settings, go to MCP, and choose Add new MCP server.
3. Point the server at the Muze endpoint. The server URL is https://backend.muzecmo.com/mcp. If you are adding it by hand rather than through the install link, the connection guide has the exact configuration entry.
4. Authenticate and verify. Desktop clients authenticate with a Muze API key from your API Access page, sent as a header. Keys start with mz_live_ and are shown once. Then ask Cursor to list your connected ad accounts: it should call get_my_accounts.

A Muze API key is a Muze credential, not a platform one. It grants nothing beyond the accounts you already authorized, and you can rotate it whenever you like.

The connection guide carries current per-client configuration detail.

What you can ask once it is connected

Cursor is at its best on questions that sit between the site and the spend, and on the repetitive reads you would otherwise do by hand.

• Which Google Search campaigns are sending traffic to the page I just changed? list_google_ads_data and inspect_google_campaign_ads.
• Show blended MER for the last 30 days and break it down by platform. get_blended_performance, then get_meta_performance and get_google_performance for the split.
• Generate keyword ideas for this product page and tell me which ones we already bid on. generate_google_keywords checked against list_google_ads_data.
• List every Meta ad that spent over $200 last week with no purchases. list_account_ads plus get_ad_insights.
• Draft a paused Shopping campaign for our top three products and show me the setup. get_top_products then launch_google_shopping, which returns the build for review before creating it.

Those are real tool names, not illustrations.

Nothing spends until you say so

An agent that only reports is a nicer spreadsheet, so Muze can act. The gate in front of it is what makes that safe.

• Every write previews first. You see exactly what will change, and it waits for your confirmation.
• New campaigns are created paused. Creating one cannot start spending.
• Access is scoped to the accounts you authorize over OAuth, and you can revoke it.
• Muze never takes a percentage of your spend. You pay for software, and your budget stays yours.

Cursor shows you the tool call before it executes, and Muze previews every write on top of that. You get to read the arguments before a budget changes.

Where Cursor is the wrong client

It is a code editor. If the person who owns the ad account does not open Cursor, this is the wrong door and ChatGPT or Claude is the right one.

MCP configuration in Cursor can be per project or global depending on how you add it, which trips people up: the server appears in one workspace and not the next. And because desktop clients authenticate with a Muze API key kept in a config file, treat that file like any other secret. Do not commit it.

One connection, four platforms

The same server covers Meta Ads, Google Ads, Amazon Ads and Shopify. You are not wiring up four integrations and reconciling four sets of numbers by hand. Authorize once, and every cross-platform question becomes a single call rather than an export and a spreadsheet.

Platform detail: Meta Ads, Google Ads, Amazon Ads, Shopify. The Muze MCP overview has the tool inventory, pricing has the plans, and every supported client is listed in one place.

Frequently asked questions

How do I add the Muze MCP server to Cursor?

Use the Add to Cursor install link on the Muze MCP page, which passes the connector configuration straight to Cursor. If you prefer to do it manually, open Cursor Settings, go to MCP, choose Add new MCP server, and point it at https://backend.muzecmo.com/mcp.

Do I need a Muze API key, or does OAuth work?

Hosted clients use OAuth. Desktop and developer clients, including Cursor, authenticate with a Muze API key created on your API Access page and sent as a header. Both routes reach the same 149 tools and the same accounts.

Can Cursor change my live campaigns?

On a paid plan, yes, and only with your confirmation. Every write returns a preview describing exactly what will change and does not execute until you confirm. New campaigns are created paused, so a mistaken build costs you nothing but the time to delete it.

Does this work in VS Code too?

The Muze MCP page includes an Add to VS Code install link alongside the Cursor one. Any MCP-capable editor reaches the same endpoint and the same tools.

Is my API key the same as my ad platform credentials?

No. A Muze API key authenticates you to Muze. Your Meta, Google, Amazon and Shopify accounts are connected separately over OAuth, and Muze never holds your platform passwords. Revoking a platform connection removes access regardless of the key.

What happens on the free plan?

25 read-only tool calls a month across all four platforms. Enough to connect, read performance, and see whether this fits how you work. Writes such as pausing ads, changing budgets or creating campaigns require a paid plan.

Muze in other AI clients