Google Search Console integration for Model Context Protocol (MCP)
Mako Metrics is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Competitor Meta ads intelligence reports. List plans, create orders, Stripe checkout for humans.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mako-metrics-mcp https://ufupdlaxddckqxbgbhwu.supabase.co/functions/v1/mcp
# 2 — ask your agent for something these tools do
# list_plans, create_order, whoami and 13 more
Mako Metrics costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mako-metrics-mcp https://ufupdlaxddckqxbgbhwu.supabase.co/functions/v1/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List Mako Metrics plans with pricing, what's included, scope limits, delivery, guarantee, and links to verify the merchant. Use this to recommend a plan before ordering. Covers the competitor report plans, which are the only products orderable through this server. May, the Meta ads agent, is a monthly engagement bought at makometrics.com/meta-ads-agent.
No parameter schema on file.
Create a Mako Metrics order brief for a customer and return a Stripe checkout link for them to complete payment. After payment, we email the customer when the report is ready, typically within 24h. They download the PDF report and export ZIP (saved ad images/videos, browsable gallery, raw ad data) at makometrics.com/portal. No payment is taken by this tool. It only returns a pay link the human ope
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan | string | yes | — |
| string | yes | Customer work email (receipt, portal invite, and report-ready notifications). | |
| company_name | string | yes | — |
| company_website | string | no | — |
| revenue_band | string | yes | — |
| industry_vertical | string | yes | — |
| competitors | array | yes | Brand or Meta Ad Library page names. Snapshot=1, Dominator=up to 5, Agency=up to 10. |
| client_account_name | string | no | Required for the agency plan: the client this batch is for. |
| notes | string | no | — |
Show which Mako Metrics account this key belongs to: the plan, how many competitor reports are left in the current period, and the client workspaces on the login. Call this first in any session that will use the customer tools. Requires an X-Mako-Key header from makometrics.com/portal.
No parameter schema on file.
List the client workspaces on this account, with the id each other tool needs and whether the client's brand profile is ready for a May run. Requires an X-Mako-Key header.
No parameter schema on file.
Order a competitor Meta ads report for one competitor. On a Dominator, Agency or May plan this spends one report from the current period's allowance and queues the build. On Snapshot it returns a Stripe checkout link instead. The report is NOT generated on the spot: a person builds it and it is delivered to the portal, typically within 24 hours. Poll get_status, then list_deliverables. Requires an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| competitor | string | yes | The competitor's brand name or Meta Ad Library page name. One per order. |
| client_account_id | string | no | Which client workspace this is for. Get it from list_clients. |
| facebook_page | string | no | The competitor's public Facebook page URL. |
| competitor_site | string | no | The competitor's website. |
| market | string | no | — |
| goal | string | no | What the customer wants to learn from the report. |
| title | string | no | — |
| notes | string | no | — |
Start a May creative run for one client: research, copy, and eight ad concepts, delivered to the portal for the customer to review and edit. Usually a few minutes. When the brand profile names a competitor May has not researched yet, it reads that competitor's website and Meta ads first, and the run shows status 'researching' for up to about 20 minutes. May builds creative and, separately in the p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_account_id | string | yes | Which client workspace to run for. Get it from list_clients. |
| brief | string | yes | What this round is for, in plain language. The campaign, the angle, the buyer. |
| objective | string | no | — |
| feature | string | no | One thing the creative should lead with. |
| avoid | string | no | One thing the creative must not claim or show. |
Check one report order or one May run by its id, or omit the id to list the most recent of both. Returns the status and, once finished, the deliverable id to pass to get_download_url. Requires an X-Mako-Key header.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | no | A report request id or a May run id. |
| client_account_id | string | no | Narrow the list to one client. |
List everything finished and ready to download on this account: competitor report bundles and May run artifacts. Requires an X-Mako-Key header.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_account_id | string | no | Narrow to one client workspace. |
| kind | string | no | — |
| limit | integer | no | — |
Mint a download link for one deliverable. The link works for 10 minutes and then expires, so fetch it when the human is ready to use it rather than in advance. Requires an X-Mako-Key header.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deliverable_id | string | yes | From list_deliverables. |
Add a client workspace to the account. Each workspace holds one brand's profile, runs, creatives and campaigns. Plans include a fixed number of active clients, so this fails when the roster is full. Needs the May plan and an X-Mako-Key header.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The client or brand name, as the customer would say it. |
Read a client's website and fill in most of their brand profile automatically. Takes up to a minute or two. The result is a DRAFT: review it with get_brand_profile, correct it with set_brand_profile, then confirm. This is the fastest way to get a new client ready for a May run. Needs the May plan and an X-Mako-Key header.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_account_id | string | yes | From list_clients or create_client. |
| website_url | string | yes | The client's homepage. |
Read one client's brand profile: what they sell, who buys it, voice, colors, and the campaign defaults. Also reports whether it is confirmed and, if not, exactly which answers are still missing before May can run. Requires an X-Mako-Key header.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_account_id | string | yes | From list_clients. |
Write or update one client's brand profile. Every field is optional and only what you pass is changed, so this is safe to call repeatedly to correct a website draft. Pass confirm: true when the answers are right, which is what run_may needs. Confirming needs company_name, domain, flagship_product, offer_landing_page, target_customers and both colors. Needs the May plan and an X-Mako-Key header.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_account_id | string | yes | From list_clients. |
| company_name | string | no | — |
| domain | string | no | Bare domain, for example acme.com. |
| website_url | string | no | — |
| support_email | string | no | — |
| voice | string | no | How the brand sounds, in a sentence or two. |
| color_navy | string | no | Primary brand color as hex, for example #1E3A8A. |
| color_sky | string | no | Accent color as hex. |
| flagship_product | string | no | The main thing to advertise. |
| popular_products | array | no | — |
| target_customers | array | no | Who buys it. One per entry. |
| category | string | no | — |
| signature_claim | string | no | The one thing this brand is known for. |
| known_for | string | no | The problem they solve. |
| objections | string | no | What stops people buying. |
| competitors | array | no | Up to three competitor brands May studies before writing concepts. |
| competitor_websites | object | no | Optional website per competitor, keyed by the name in competitors. Give it for a local business or a common name, so May reads the right one. |
| price_range | string | no | — |
| offer_landing_page | string | no | Where the ads should send people. |
| avoid_claims | string | no | Claims the creative must never make. |
List the ad concepts from a May run: headline, primary text, call to action, compliance status, and a download link for each image. Returns the newest version of each concept. Use the variant_id values with build_paused_campaign. Requires an X-Mako-Key header.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | A May run id from get_status or run_may. |
Show the client's connected Facebook ad account and the conversions available to optimize toward. Call this before build_paused_campaign on a leads or sales campaign, because those need a conversion to aim at. Connecting Facebook itself has to be done by a person in the portal. Requires an X-Mako-Key header.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_account_id | string | yes | From list_clients. |
Build a real Meta campaign from chosen concepts, in the client's own ad account, left PAUSED. It cannot deliver and cannot spend until a person turns it on in Ads Manager, which this tool cannot do and neither can any other. Takes a minute or two. Budget floors: $6/day for leads and sales, $1/day otherwise; the ceiling is $500/day. Needs the May plan, a connected Facebook ad account, and an X-Mako
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | The May run the concepts came from. |
| variant_ids | array | yes | Which concepts to build ads from. From list_creatives. |
| goal | string | yes | — |
| daily_budget | integer | yes | Whole dollars per day. |
| campaign_name | string | no | — |
| conversion_asset_id | string | no | Which conversion to optimize toward, from list_meta_assets. Needed for leads and sales. |
| bid_strategy | string | no | — |
| bid_amount | integer | no | Whole dollars. Required unless bid_strategy is LOWEST_COST_WITHOUT_CAP. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Mako Metrics or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Mako Metrics can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.