Skip to content
Get MCP AdsGet MCP Ads, home
Start free
guides/setup/muse.md

How to connect your ad accounts to Muse by Meta

Connect Get MCP Ads to Muse by Meta through a conversation: paste one setup prompt, approve the OAuth consent, and read your advertising accounts from Muse.

Get MCP AdsMuse
Connection URL
https://mcp.getmcpads.com/mcp

The same URL in every client. Sign in once when Muse asks; nothing is installed and no key is issued.

For you

What the answer looks like, and what to type to get it.

Muse by Meta connects through a conversation. You paste a setup prompt, Muse prepares its own MCP connection to Get MCP Ads, and you approve the access once in your browser. Nothing is installed on your computer and no token is ever pasted into the chat.

SetupLink to this section

Before you startLink to this section

  • Access to Muse. Meta decides where and to whom Muse is available: check muse.ai for your country and account.
  • A Get MCP Ads account, on any plan.
  • At least one advertising platform connected in the dashboard, with the accounts you want ticked. Muse can only reach what you ticked.

1. Copy the setup promptLink to this section

textPaste this into a conversation in Muse
Connect my Get MCP Ads account to Muse using this remote MCP server: https://mcp.getmcpads.com/mcp

Read https://www.getmcpads.com/docs/authentication and https://www.getmcpads.com/llms.txt, then configure a reusable MCP connection using Streamable HTTP.

Use your supported secure OAuth connection flow with PKCE and dynamic client registration. Use a callback supported by your environment and keep credentials in your secure credential system. Never ask me to paste an access token, refresh token or API key into this conversation.

Show me the authorization link so I can sign in and approve access. If I need to connect an advertising platform or select accounts, guide me to the Get MCP Ads dashboard at https://app.getmcpads.com/dashboard/sources and let me make those choices.

After authorization, initialize the MCP connection, discover the available tools and show which accounts I have authorized with list_accounts. Use get_capabilities when additional tool discovery is needed.

Start with read-only operations. Do not change campaigns, budgets, platform connections or account selections during setup. Ask which account I want to use before retrieving a performance report.

Keep the connection instructions reusable for future conversations. If your environment cannot complete a step, explain the exact blocker without exposing credentials or claiming the setup succeeded.

The same prompt is in the dashboard, under Agents, then Muse, with a button that copies it.

2. Paste it into Muse and approveLink to this section

  1. Open a conversation in Muse and paste the prompt.
  2. Muse reads the authentication document, registers itself and shows you an authorization link.
  3. Open the link, sign in to Get MCP Ads and approve. The consent screen is ours, on mcp.getmcpads.com.
  4. Return to Muse. It finishes the connection and discovers the tools.

3. Check the connectionLink to this section

Ask Muse: "Show which advertising accounts I have authorized Get MCP Ads to access." It should answer with the accounts you ticked, grouped by workspace. An empty list means the platform is connected but no account is ticked yet.

4. Ask for a first reportLink to this section

Start with a read: "Summarize my Meta Ads performance for the last seven complete days and compare it with the previous seven days. Include spend, impressions, clicks, CTR, CPC and CPM, and tell missing conversion data apart from zero." Muse asks which account to use when you have more than one.

What has been tested, and what has notLink to this section

Tested from a real Muse account on 20 September 2026: the OAuth consent, the MCP initialization, tool discovery, and a seven-day Meta Ads performance read. Not tested in Muse yet: campaign changes, revoking the access, and token renewal. They work the same way in every MCP client on our side, but we have not watched them run in Muse.

This is a compatibility, not a listing. Get MCP Ads is not in Muse's connector directory, and Meta has neither reviewed nor endorsed this setup.

If something goes wrongLink to this section

  • Muse says it cannot add an MCP server. Ask it to explain the exact step that blocks. Muse builds the connection itself, so the wording of the blocker is what tells us what to fix. Send it to us from the contact page.
  • The authorization link fails or expires. Ask Muse for a fresh link and open it in the browser where you are signed in to Get MCP Ads.
  • Muse sees no account. Open Sources in the dashboard, connect the platform and tick the accounts, then ask Muse to list accounts again.
  • Muse asks you to paste a token or an API key. Do not. Tell it to use its OAuth flow; the setup prompt already says so.
  • A later conversation does not find the connection. Paste the setup prompt again. We cannot promise that Muse carries a connection from one conversation to the next.
  • You want to remove the access. Remove the connection in Muse, and un-tick the accounts or disconnect the platform under Sources in the dashboard. An account that is not ticked is refused on the very next call, from any client.

Before it can answer anythingLink to this section

Connecting the client is one half. The other is connecting at least one advertising platform in the dashboard and ticking which accounts to expose. Both need you, not the assistant: one is a consent screen at Google or Meta, the other is a decision about which accounts a machine may read.

For your agent

The tool sequence, the parameters that matter, and what will be refused.

Both readings as Markdown: /guides/setup/muse.md

Setting up Muse against this gateway. The endpoint is https://mcp.getmcpads.com/mcp, and each source also has its own endpoint if a narrower tool list is wanted.

What is specific to MuseLink to this section

  • There are two pieces: the remote Get MCP Ads server, which does not change, and the MCP client that Muse prepares in its own environment to call it.
  • Use the shared endpoint. Per-source endpoints are not supported from Muse at this time.
  • Keep credentials in Muse's own credential system. Never print, log or ask for an access token, a refresh token or an API key.
  • Stay read only during setup. Do not change campaigns, budgets, platform connections or account selections.
  • If a step cannot be completed, say which one and why, and do not claim the setup succeeded.

What the client does on its ownLink to this section

  1. It requests https://mcp.getmcpads.com/mcp and receives a 401 with a WWW-Authenticate header.
  2. It reads the protected resource metadata named in that header.
  3. It registers itself through dynamic client registration. No key is issued or pasted.
  4. It opens the authorisation page with PKCE and waits for the person to approve.
  5. It calls tools/list and receives the tools for the connected sources, plus four routing tools.

Checking it workedLink to this section

Call list_accounts. It answers without touching any advertising API, so it separates a connection problem from an account problem. An empty list means the platform is connected but nothing was ticked.