Connect Meta Muse to AdKit

Add AdKit to Meta Muse as a custom connector, then manage Meta, Google, TikTok, LinkedIn, Reddit, X, and Microsoft ads from a normal conversation. Muse already connects Meta ad accounts on its own; AdKit adds the other platforms, and every change it makes waits as a draft for you.

There are two ways in, depending on where you use Muse:

• The Muse app (muse.ai, iOS, Android): you connect by chatting. Muse has no MCP settings screen, so you describe the server in a message and Muse builds the connector itself.
• Muse Code (the terminal agent): you add an mcp_servers entry to its settings file and sign in from the command line.

Setup in the Muse app

1. Send Muse the setup message. Paste this into a new chat:

   Set up AdKit as a custom connector.
   Server URL: https://mcp.adkit.so
   It is a standard MCP server over HTTP that signs in with OAuth. There is no API key to enter.
   Send me the sign-in link and wait until I have approved it.
   Then run the AdKit checkin tool with agentId: "muse" and tell me which ad accounts you can see.
   

2. Answer the questions Muse asks. If it asks whether the server is a URL or a command, say it is a URL reachable over HTTP. If it asks for an API key, tell it there is none: the server uses OAuth sign-in.
3. Approve the sign-in link. Open the link Muse sends back and allow access with the AdKit account that owns your ad accounts.
4. Done. Muse saves the connector. You can turn it off later under Settings, then Connectors in the Muse app.

Setup in Muse Code

1. Add the server to your settings file. Open ~/.config/muse/settings.json and add this block (merge it if you already have mcp_servers):

   {
     "mcp_servers": {
       "adkit": {
         "transport": "streamable_http",
         "url": "https://mcp.adkit.so"
       }
     }
   }
   

   
   Muse Code treats a server as required by default and aborts the run if it can't start. Add "mode": "optional" to the entry if you'd rather it skip AdKit with a warning when the connection is down. Source: Muse Code docs, MCP servers.
2. Sign in. Run this in your terminal and finish the sign-in in the browser:

   muse mcp login adkit
   

3. Check the server shows up. In a Muse Code session, run /mcp. AdKit should be listed with its tools.

Check it worked

Send this in a new chat. It confirms Muse can actually use AdKit:

Use the AdKit connector you just added and run the AdKit checkin tool with agentId: "muse".
If sign-in is needed, send me the link and wait for me to finish.
Then tell me if AdKit is connected and ready. If not, tell me what failed.

What you can do

Once connected, Muse can pull your live campaigns, draft budget and targeting changes, generate ad creatives, and research competitors. Nothing goes live on its own: every change is saved as a draft for you to review and publish.

Muse keeps its own Meta ads connection next to AdKit. Keep both and use AdKit for the other platforms, or run every platform through AdKit so one dashboard holds all the drafts.

Troubleshooting

Muse asks for an API key. AdKit doesn't use one. Reply that the connector is a URL (https://mcp.adkit.so) with OAuth sign-in, and that it should send you the sign-in link instead.

No sign-in link arrived. Ask again in the same chat, for example: Connect to AdKit again and send me the sign-in link. Then approve it with the AdKit account that owns the ad accounts you want Muse to use.

You connected the wrong AdKit account. The sign-in step uses whoever is already logged in to AdKit in that browser. Log in to the right account at app.adkit.so first, then remove AdKit under Settings, then Connectors and run the setup message again.

Muse Code says the server failed to start or returns 401. Run muse mcp login adkit and retry. A startup or mid-session 401 prints the exact login command to run.

It worked before and stopped. The authorization expires after 90 days without use. Reset it: revoke the old connection under Devices & Keys, remove the connector in Muse, and set it up again. In Muse Code, run muse mcp logout adkit first.

This is a new path. We wrote these steps from Meta's documentation and from how other MCP servers connect to Muse. If Muse asks for something not covered here, tell us what it said and we'll update the guide.

Need a hand? Reach out and we'll help.