The Meta ads MCP server for your own ad accounts

What a Meta ads MCP server is

MCP stands for Model Context Protocol. It is an open standard that lets an AI assistant call tools that live somewhere else. A Meta ads MCP server is one of those tools. It sits between the assistant and Meta's Marketing API, the same API that Ads Manager uses.

You write a plain request, such as "show me what each ad account spent yesterday". The assistant picks the right tool, the server asks Meta, and the answer comes back as data the assistant can read, sort and explain. The same path works for changes: pause an ad, raise a budget, build a campaign.

That is why the address and the key matter so much. Whoever holds them can do what the tools allow, on every account the key reaches.

Amino Engine Ads Manager, in short

Amino Engine Ads is software for Meta ads. It connects your ad accounts, shows what they spend and earn, and launches campaigns into one or many accounts. The MCP server, named "Amino Engine Ads Manager" inside your AI client, exposes the same Meta access to your own assistant.

• One address. Every brand uses https://ads-bridge.aminoengine.com/mcp. The key decides whose accounts you reach.
• One key per brand, shown once. After you connect your Meta accounts, the key appears once. You can reveal, rotate or revoke it later.
• Two ways to send the key. In an Authorization header (Claude Code, scripts), or inside the address for claude.ai connectors, which only take a URL.
• 121 Meta tools. Grouped by job, listed below.
• Pipeboard-compatible names. Tool names and argument names match Pipeboard's, so a script written for Pipeboard runs by changing the address.
• Works with Claude. Claude Code, claude.ai and Claude desktop. Any client that speaks MCP over HTTP can connect the same way.

One warning, said plainly: the key can write. It can create, edit, pause and delete things in your ad accounts. Keep it as private as a password, and never paste it into a shared document or a public repository.

The tool families, with real tool names

The 121 tools fall into a few families. These are real names from the server's own catalogue. Your assistant sees the full list and a short description of each one.

• Accounts and health: get_ad_accounts, get_account_info, get_funding_source (is there a spendable card), get_account_activities (who changed what).
• Campaigns, ad sets and ads: get_campaigns, create_campaign, update_campaign, get_adsets, create_adset, get_ads, create_ad, update_ad, duplicate_campaign.
• Meta's verdict: get_ad_review_feedback returns why Meta rejected an ad, in Meta's own words.
• Creatives and media: create_ad_creative, create_carousel_ad_creative, upload_ad_image, bulk_upload_ad_images, upload_ad_video, wait_for_video.
• Results: get_insights for one account, campaign, ad set or ad, and bulk_get_insights for many at once.
• Audiences and targeting: get_custom_audiences, create_lookalike_audience, search_interests, search_geo_locations, estimate_audience_size.
• Pages and pixels: get_managed_pages, get_pixels, get_dataset_quality (when a pixel last fired).
• Bulk changes: bulk_update_ads, bulk_update_adsets, bulk_update_campaigns.
• Rules and tests: create_ad_rule, create_budget_schedule, create_ad_study (split tests).

A few tools, such as catalogs, Instagram posting and lead downloads, need Facebook permissions that the brand sign-in does not ask for. When a permission is missing, the tool says which one instead of failing quietly.

What it reads from Meta, and what it can change

What it reads. Your ad accounts and their state, campaigns, ad sets, ads and creatives, spend and results at every level, Meta's reasons for rejected ads, pages, pixels, audiences, and the account change log. It reads through the permissions you granted when you signed in with Facebook: manage and read ads, read your business, list your pages, run ads for your pages and read page engagement.

What it can change. Create and edit campaigns, ad sets, ads and creatives. Pause or delete them. Upload pictures and videos. Build audiences, rules, budget schedules and split tests. Apply one change to many ads at once.

The launcher inside Amino Engine Ads creates everything paused, and nothing spends until you switch it on. Over MCP, your assistant calls Meta directly, so the habit is yours to set: ask it to create new campaigns paused and to show you the plan before it builds anything.

What people ask it to do

Most days the work is reading. A media buyer asks for spend and purchases by account, sorted by whatever looks wrong. A founder asks which ads Meta turned down this week and why. Someone checks whether every account still has a working card before a launch.

Then come the small changes that are slow by hand: pause these six ads, move this budget, copy that campaign into a new ad set, tag every ad with the right URL parameters. The assistant does the clicking. You read what it plans first and say yes.

Bigger builds work too. You can ask for a sales campaign with three ad sets and four pictures in each, in several accounts, created paused. For that job, the launcher inside Amino Engine Ads is often the calmer route, because it shows the whole build on one review screen before anything is sent to Meta.

Moving from Pipeboard

If you already run prompts or scripts against Pipeboard's Meta tools, the switch is small. Tool names and argument names match, so get_campaigns, get_insights and bulk_update_ads take the same arguments here. A script changes two things: the address and the key. An argument the server does not know is refused with an error, never silently ignored, so a mismatch shows up on the first call.

Amino Engine vs Meta's own MCP, Pipeboard and Ads Uploader

You have real choices here, and some of them are good fits for people who are not us. This table uses each company's own pages, read on 1 October 2026. We leave out what each one costs, because that changes and we cannot check them for you.

Meta's own server. Meta announced its ads AI connectors on 29 April 2026, saying they are "in open beta". The setup guide says you sign in through the Facebook Login for Business dialog, and that owning a Meta app is not required. If you want a server run by Meta itself, with no company in between, it is the natural pick.

Pipeboard. Its Meta ads MCP guide gives the address meta-ads.mcp.pipeboard.co and says the code is "source-available on GitHub". Its homepage lists Meta and several other ad platforms. If you run ads on many platforms from one assistant, Pipeboard covers more ground than we do. If you are leaving it, read our Pipeboard alternative page.

Ads Uploader. Its MCP page says the agent builds the launch in their web app and "Nothing goes to Meta until you press the button". That is a careful design, and it is close to ours in spirit.

Where Amino Engine fits. Pick us if you want Pipeboard-compatible tool names, one key per brand, and a launcher that puts the same ads into up to 5 ad accounts at once, paused for your review. It was built by people who run Meta ads for brands where review is strict.

Competitor facts checked on their public pages on 1 October 2026.

What it is not

• Not for other ad platforms. For brands it is Meta only: Facebook and Instagram.
• Not a robot that runs your ads. It does nothing on its own. Your assistant acts when you ask, and only with the tools it has.
• Not a way around Meta review. Every ad still goes through Meta's review, and a rejection comes back with Meta's own reason.
• Not a look-only key. The key can write, so guard it.

How to get a key

1. Email support@aminoengine.com to request access. Amino Engine Ads is opened by hand for now.
2. Sign in with Facebook once and pick the ad accounts to bring in. Leaving one out changes nothing on Facebook.
3. Open your API keys settings. Your key is shown once. Copy it somewhere safe.
4. Add the server to Claude. Our Claude setup guide has the exact steps for claude.ai and Claude Code.

Want to see the rest of the product first? The Amino Engine Ads overview covers the launcher and the dashboard, and launching into multiple ad accounts shows how one set of creatives becomes campaigns in several accounts.