Run your ads from Codex.

What this actually is

Codex is OpenAI's coding agent, and it supports MCP servers. Muze is an MCP server for paid media rather than for software: 149 tools spanning Meta Ads at 37, Google Ads at 41, Amazon Ads at 48, Shopify at 15, and 8 cross-platform tools that read across all of them at once.

Connecting it means Codex can answer questions about spend and revenue with real numbers instead of assumptions. That is unusual for an engineering-facing agent. It can check whether the checkout change shipped last Tuesday coincided with the conversion rate move that Meta is claiming credit for, using get_blended_performance and get_shopify_orders rather than a hunch and a Slack thread.

Who this is actually for

Engineering-led teams where the same people own the product and the acquisition numbers. That is common at small ecommerce companies and rare at large ones, and it is exactly the group that finds Ads Manager the most annoying, because they are used to querying things rather than clicking through them.

There is also a defensive case. If an agent already has permission to change your codebase, giving it read access to what the traffic is doing is a small step, and it makes the agent's own reasoning better. Most bad automated decisions come from missing context rather than from bad models.

How connecting works

You need a Muze account with at least one connected ad or commerce account. Platform access is OAuth inside Muze. The Codex side is an MCP server entry.

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. No developer account, no API token to mint on the platform side, no passwords handed over.
2. Create a Muze API key if your client needs one. Developer clients authenticate with a Muze API key from your Muze API Access page. Keys begin with mz_live_ and are shown once.
3. Add Muze as a remote MCP server in Codex. Add Muze to Codex's MCP configuration as a remote server pointed at https://backend.muzecmo.com/mcp, authenticated with OAuth or with your Muze API key in the X-API-Key header. Codex's own documentation is the authority on where that configuration lives for your version.
4. Verify the connection. Ask Codex to list your connected ad accounts. It should call get_my_accounts and return them. If the tools do not appear, reconnect so the client refreshes its cached tool list.

This page describes the Codex step at a high level on purpose. Codex configuration has moved between versions, and we would rather send you to current documentation than print a path that quietly stopped being true.

The connection guide carries current per-client configuration detail.

What you can ask once it is connected

The useful Codex prompts are the ones that join what you shipped to what it did. Name the window and the metric, and let it pull both sides.

• Did conversion rate move after last Tuesday's checkout change, and did ad spend move with it? get_shopify_orders and get_shopify_revenue against get_blended_performance.
• Which Google campaigns point at URLs that no longer exist? inspect_google_campaign_ads and list_google_ads_data.
• Is the Merchant Center feed rejecting anything we are actively advertising? get_merchant_feed_health plus list_merchant_center_products.
• Summarize Meta, Google and Amazon spend for the last 30 days in one table. get_meta_performance, get_google_performance and get_amazon_performance.
• Prepare a paused Search campaign for the new product page and show me every setting first. generate_google_keywords then launch_google_search, returned as a preview.

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.

Agent frameworks are getting more autonomous. Muze deliberately is not. Every write previews and waits for a human confirmation, whatever the calling agent's own permission settings say.

Where Codex is the wrong client

Codex is built for software work, so its interface assumes you are comfortable with configuration files and sandboxed execution. If outbound network access is restricted in your setup, a remote MCP server will not reach anything until that is allowed. That is an environment question we cannot answer for you.

It is also the wrong place to hand the account to a marketer. Nothing about the tools changes between clients, but the surrounding experience is built for engineers. If the person doing the media buying is not one, Muze in ChatGPT or Muze in Claude is the same capability with a door they will actually walk through.

One connection, four platforms

Meta Ads, Google Ads, Amazon Ads and Shopify arrive through one server with one auth model. For a team that would otherwise be writing four API clients and maintaining four sets of credentials, that is the whole argument.

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

Does Codex support MCP servers?

Yes, Codex can call tools from MCP servers. Muze is added as a remote server pointed at https://backend.muzecmo.com/mcp. Because the exact configuration location has changed between Codex versions, follow Codex's current documentation for where that entry belongs.

Do I need an ad platform developer account?

No. You authorize Meta, Google, Amazon and Shopify over OAuth inside Muze with your normal logins. There is no developer application to file, no API token to mint on the platform side, and Muze never receives your platform passwords.

Can Codex change campaigns without asking?

No. Regardless of how permissive the agent's own settings are, Muze previews every write and requires an explicit confirmation before it executes. New campaigns are created paused, so nothing that Codex builds can start spending on its own.

Is the tool set smaller in developer clients?

No. All 149 tools are available in every MCP client: 8 cross-platform, 37 Meta, 41 Google, 48 Amazon and 15 Shopify. The difference between clients is the setup path and the presentation, not the capability.

What if my sandbox blocks outbound requests?

Then the MCP server is unreachable and no tools will load. Muze is a remote server, so the client needs to be able to make outbound HTTPS requests to the Muze endpoint. Allow that in your environment before troubleshooting anything else.

How much does it cost to try?

Nothing. The free plan includes 25 read-only tool calls a month across all four platforms, with no credit card. Write actions require a paid plan, and Muze never takes a percentage of your ad spend.

Muze in other AI clients