Growomat runs a hosted MCP server. Connect it once and the assistant you already work in can draft campaigns, read what they actually cost, and stage changes across every platform on your account. Nothing reaches a live ad account until you push it.
Server endpointhttps://mcp.growomat.com/mcpThe same server covers every platform your account is connected to. There is no per-platform server to install and no second credential to manage. Each platform has its own page describing what an assistant can do there.
The server speaks OAuth 2.1 over streamable HTTP, so a client that supports remote MCP servers connects by asking you to approve it. There is no key to paste into a config file and no separate developer account to create.
Add the server URL in your client, or pick Growomat from its connector list.
Approve the connection. It is scoped to the permissions on your account, and you can revoke it from either side.
Ask for what you want. Reads answer immediately; anything that changes a live ad account is staged for you to push.
An assistant connected to an ad platform can only repeat what that platform says about itself: clicks, impressions, and the conversions the platform managed to observe. Growomat imports your own conversions, matches them back to the campaign that produced them, and answers from that. Ask what last month cost and you get spend. Ask what it earned and you get an answer built from your data, not the platform's estimate of it.
This is also why the reports an assistant reads here are worth reading. The same matched data drives budget decisions, the waste it reports, and the record of what changed.
These are the clients the connector has been run in and verified. It is a standard remote MCP server, so any client that supports remote servers over OAuth should connect the same way. We name a client here once somebody has actually completed the flow in it, because a setup instruction that does not work is worse than none.
Every capability is its own tool with its own arguments, and every tool is annotated read-only or destructive. A client can show you what a call will do before it runs, and a token can be scoped so some of them are unavailable.
The alternative is a single tool that forwards any request to the underlying API. It looks larger on a directory listing and it removes the only place a guardrail can sit: a client cannot tell a report from a deletion if both arrive as the same call. One tool per capability is a design decision, and it is the reason a connector can be reviewed at all.
Changes are created and edited inside Growomat and stay paused there. Sending them to a live ad platform is a separate, explicit call, so a conversation cannot spend money by accident.
Every call is scoped to the permissions on your token, rate-limited, and logged. A read-only token cannot write, whatever it is asked.
Destructive tools are marked as destructive, so a client can ask you first rather than discovering it afterwards.
Autopilot manages daily budgets and campaign status across Google Ads, Microsoft Advertising, Reddit Ads and Meta Ads. Keyword bids, negative keywords and bid modifiers are available on Google Ads and Microsoft Advertising only.
No. Connecting is an approval inside your client. The REST API and the SDKs exist for people who would rather build than ask, and they reach the same data with the same limits.
Not on its own. Edits are made inside Growomat and stay paused until you push them to the platform, which is a separate call you make deliberately.
Every platform your account is connected to, through the same server. Each platform page above lists what an assistant can do there and where the differences are.
Two things. One connection covers every platform instead of one each, and the answers are built from your own conversion data rather than from what each platform reports about itself.
The first month is free and includes the connector. No waitlist, no configuration.
Start free