What you need first
- Access to Amino Engine Ads. It is opened by hand for now. Email support@aminoengine.com to request it.
- Your Meta accounts connected. You sign in with Facebook once and pick the ad accounts to bring in.
- Your key. It is shown once in your API keys settings, right after you connect. You can reveal, rotate or revoke it later.
- A Claude account. Anthropic says custom connectors work on every Claude plan. The entry plan is limited to one. On Team and Enterprise plans, an owner adds the connector for the whole organisation.
Step by step
1. Get access and connect Meta
Request access by email. Once your account is open, sign in with Facebook and pick the ad accounts to bring in. Leaving an account out changes nothing on Facebook.
2. Copy your key
Open your API keys settings. The key is shown once, so copy it into a password manager now. The key can make changes in your ad accounts. Treat it like a password.
3. Add the connector in claude.ai or Claude desktop
A custom connector is a URL. So for claude.ai and Claude desktop, the key goes inside the address:
https://ads-bridge.aminoengine.com/mcp?token=YOUR-KEY- In Claude, open Customize, then Connectors.
- Choose Add, then Add custom connector.
- Name it Amino Engine Ads Manager.
- Paste the address above, with your key in place of YOUR-KEY, as the remote MCP server URL.
- For sign in, choose No sign in. The key in the address does that job.
- Click Add.
Menu names come from Anthropic's help article on custom connectors with remote MCP, read on 1 October 2026. Anthropic renames menus from time to time. If yours look different, follow that article.
4. Or add it to Claude Code
Claude Code takes the key in a header, which keeps it out of the address. Run this in your terminal, with your key in place of YOUR-KEY:
claude mcp add --transport http amino-engine-ads-manager https://ads-bridge.aminoengine.com/mcp --header "Authorization: Bearer YOUR-KEY"This form matches claude mcp add --help and the Claude Code MCP docs as of 1 October 2026. By default the server is added for the current project only. Add --scope user to use it in every project. Never use --scope project with a key in the command, because that scope writes a file meant to be shared through version control.
5. Turn it on and test it
In claude.ai, start a chat, open the + menu, then Connectors, and switch Amino Engine Ads Manager on. In Claude Code, type /mcp to see it listed. Then ask: "List my ad accounts." You should see the accounts you brought in.
Ten prompts to start with
Copy these as they are, then change the names to yours. The last few make changes, so read what Claude plans before you say yes.
- "Show me spend, purchases and ROAS for each of my ad accounts over the last 7 days, highest spend first."
- "List every ad Meta rejected in the last 14 days, with the account, the ad name and Meta’s reason for each."
- "Pause the ad called “Spring video 2” on my Main account. Then read it back from Meta and tell me its status."
- "Which ad sets spent money yesterday with no purchase? Give me a short table."
- "Check every ad account for a working card. Which ones cannot run an ad today, and why?"
- "Draft a launch into my three accounts: one sales campaign each, three ad sets, these four pictures in every ad set. Write the plan as a table first and do not create anything yet."
- "The plan looks right. Create it with every campaign, ad set and ad paused. Then list the new ids by account and confirm each one is paused."
- "For each account, which pixel is in use and when did it last fire?"
- "Who changed what on the Main account in the last 3 days?"
- "Compare this week with last week by campaign. What moved the most, and what should I look at first?"
What Claude can and cannot do through it
It can read your ad accounts, campaigns, ad sets, ads, creatives, spend and results, Meta's rejection reasons, pages, pixels and audiences.
It can change things too. With your key, Claude can create, edit, pause and delete campaigns, ad sets and ads, upload pictures and videos, and change many ads in one go.
Paused first. The launcher inside Amino Engine Ads creates everything paused, so nothing spends until you switch it on. Over MCP, Claude talks to Meta directly. Keep the same rule by asking for it: "create everything paused and show me the plan first".
It cannot work outside Meta. It does nothing on its own between your messages. It cannot skip Meta's ad review. And a few tools, such as catalogs, Instagram posting and lead downloads, need Facebook permissions the brand sign-in does not ask for, so Claude will tell you the permission is missing.
Keep your key safe
- The key is a secret. Anyone who has it can change your ads.
- Do not paste it into a shared chat, a shared document or a public repository.
- If it leaks, revoke it. Rotate it in your settings, or email support@aminoengine.com and we revoke it for you.
- Disconnect Meta and your Meta data goes with it. Removing the app on Facebook deletes it too.
If something goes wrong
- Claude says the server is unauthorised. The key is wrong, revoked or still says YOUR-KEY. Paste the current one.
- An account is missing. It was left out when you connected, or your Facebook login cannot reach it. Ask Claude to list your ad accounts and compare.
- An error mentions a permission. That tool needs a Facebook permission the sign-in does not ask for.
For the full picture of the server, its tool families and how it compares with Meta's own, read the Meta ads MCP server page. For the rest of the product, see the Amino Engine Ads overview or how to launch into multiple ad accounts.