Retiring a GoMarble instance: what changes when you stop hosting.

Who this page is for

This page assumes a GoMarble instance is already running somewhere and someone is asking whether to keep maintaining it. It is organised around the cost of leaving rather than around a feature scorecard. If nothing is deployed yet and you are choosing between hosted and self-hosted from scratch, read Muze vs GoMarble, which puts the two models side by side without assuming you have already built one.

If the real question is which class of tool to adopt, the roundups cover more ground. Best AI advertising tools ranks GoMarble next to the platform-native systems and the creative generators, and best PPC automation tools covers the rule engines a self-hosted server is often bought to replace.

What open source gets you, honestly

You can read every line before you point it at an ad account. For a tool that can change budgets, that is not a small thing. You can fork it, add the endpoint you need, and keep running your own version forever. There is no per-seat cost, no vendor deciding your plan tier, and no possibility of a company disappearing and taking your integration with it.

If your team already runs infrastructure and your security review requires reading source, GoMarble is the straightforward answer and no hosted product beats it on those criteria. We are not going to argue the point.

What self-hosting actually costs

Self-hosted is free until you count the hours. You supply your own Meta and Google developer credentials, which means someone files the developer application, gets the API access approved, stores the tokens somewhere safe and rotates them. Then you deploy the server, keep it patched, monitor it, and fix it the week a platform API version is deprecated. None of that is hard. All of it is someone's Thursday.

Muze takes the other side of the trade. You connect over OAuth with your normal platform login. There is no developer account, no token to mint, no server to run. In exchange you accept that the code is ours and you are trusting a vendor. That is a real trade and you should make it deliberately. What we publish instead of source is the behaviour: 149 tools documented, every write previews before it fires, and new campaigns are created paused.

Muze and GoMarble side by side

Competitor rows come from our verified competitor dataset. GoMarble is open source, so cost depends on your own infrastructure rather than a published price.

GoMarble details last verified 2026-07-24. Vendors change their products, so check their site before you decide anything on the strength of this table.

Reasons to stay on GoMarble

• Open source, so you can audit and modify the code before it touches a live ad account
• No vendor lock-in and no per-seat cost
• Your credentials never leave your infrastructure
• You can add the endpoint you need instead of filing a feature request

Reasons people move to Muze

• Nothing to deploy, patch, monitor or wake up for
• Four platforms in one connection instead of two: Meta Ads, Google Ads, Amazon Ads and Shopify
• OAuth login, so no developer application and no tokens to store or rotate
• Confirm-gated writes shipped by default rather than implemented by you
• Optimization on top of the API: analysis passes, search term mining and competitor research

The question that decides it

Who is on call when a platform deprecates an API version? If the answer is a named engineer who is happy about it, self-host. GoMarble is a good project and you will get exactly what you build.

If the answer is nobody, or it is you and you also have ads to buy, a hosted server is the honest choice. The failure mode of self-hosting is not a dramatic outage. It is a server that quietly stops working in April and gets noticed in June.

What you give up either way

With GoMarble you give up Amazon Ads and Shopify, because it covers Meta and Google. For an ecommerce brand that is the whole commerce picture missing, and no amount of code access replaces data you do not have.

With Muze you give up source access. We publish the tool inventory, the platform list and the safety model instead, and we scope access to the accounts you authorize so you can revoke it in one click. If a code audit is a hard requirement in your organization, that is a legitimate blocker and GoMarble is the better fit. See how the wider field compares in the ad MCP server roundup, or check pricing if you want the numbers first.

How to move from GoMarble to Muze

1. Leave your GoMarble instance running. There is no reason to tear anything down while you evaluate.
2. Sign up for the Muze free tier. 25 read-only tool calls a month, authorized over OAuth, no developer credentials required.
3. Connect Amazon Ads and Shopify first, since those are the two things a Meta and Google server cannot give you.
4. Compare the same analysis side by side for a week before you decide anything.
5. If you keep Muze, revoke the platform tokens your self-hosted instance was using. Do that deliberately rather than leaving credentials live.

Frequently asked questions

Is GoMarble's MCP server free?

It is open source and self-hosted, so there is no licence fee. You pay in infrastructure and maintenance instead, and you supply your own Meta and Google API credentials. Muze is hosted, with a free tier of 25 read-only tool calls per month and a paid plan for write access.

Do I need a developer account to use GoMarble?

Yes. A self-hosted server runs on your own API credentials, so someone has to get developer access approved on each platform and manage the tokens. Muze connects over OAuth with your normal platform login, so there is no developer application and nothing to rotate.

Does GoMarble support Amazon Ads or Shopify?

No. GoMarble covers Meta Ads and Google Ads. Muze covers Meta Ads, Google Ads, Amazon Ads and Shopify in one connection, which is what makes blended reporting against store revenue possible.

Is a self-hosted MCP server more secure?

It is more auditable, which is not the same thing. You can read the code and your credentials stay on your infrastructure. You also inherit responsibility for patching, monitoring and access control. Muze scopes access to the accounts you authorize, previews every write and creates campaigns paused, and you can revoke access at any time.

Can I run a self-hosted server and Muze together?

Yes. MCP clients support multiple servers, so you can keep a self-hosted instance for Meta and Google while using Muze for Amazon Ads and Shopify. Plenty of teams end up there.

What happens to my data with a hosted MCP server?

Muze reads the ad and store accounts you explicitly authorize over OAuth, and nothing else. Access is scoped, revocable, and never extends to accounts you did not connect. Muze also never touches or holds ad budget: you keep paying the platforms directly from your own accounts.

Other alternatives worth reading