Post to Social Media from Meta's Muse

Autonomous agentsMeta

Muse is Meta's personal AI agent, working on its own cloud computer from the Muse app, muse.ai and WhatsApp. It has no settings screen for MCP servers — you ask it to build a connector, and the message below tells it exactly how to reach iHatePosting.

How do I connect iHatePosting to Muse?

It takes about a minute. Nothing here needs a download, and the only thing you carry between the two apps is a key you can revoke whenever you like.

1Step 1
Create an iHatePosting API key
Sign in, open Settings → Developers and create a key. It starts with pk_live_, and the same page can show it again whenever you need it.

2Step 2

Add iHatePosting to Muse

Paste this into a new message in the Muse app or at muse.ai. When Muse asks for your key, give it only in Muse's secure credential prompt — never in the chat — and allow it to reach ihateposting.com.

Muse — connector

Create a custom connector for iHatePosting so you can schedule and publish my social media posts.
- It is a remote MCP server over Streamable HTTP (not SSE) at https://ihateposting.com/mcp?client=muse
- It takes either route. To sign in instead of using a key, point the connector at https://ihateposting.com/mcp/oauth and it answers 401 with the sign-in address in the WWW-Authenticate header, which you open in my browser. The address above takes an API key instead, sent as the header Authorization: Bearer followed by the key — ask me for that through your secure credential prompt; I will not type it in this chat.
- Connect with the official MCP SDK, list the tools, then test by calling whoami and list_accounts.
- Save it as a skill, so every request to draft, schedule or publish my social media posts goes through iHatePosting.
When it works, show me my connected accounts.

3Step 3
Ask it to post
Tell Muse what you want to say and where. It saves a draft in iHatePosting unless you ask for the post to go out now or at a set time.

What is different about Muse

Every client reaches the same server, and then behaves like itself. These are the things that are true here and not somewhere else.

Muse writes the connector itself from the message you send, so the result can differ between attempts. The message names the address, the transport and the header, and asks Muse to prove the connection by calling whoami and listing your accounts.

The message offers Muse both routes. Signing in is the better one: iHatePosting answers Muse's first call with the sign-in address, Muse opens it in your browser, and no key exists to leak. If Muse asks for a key instead, give it only through Muse's secure credential prompt, never in the chat — the message says so, and leaves the key out on purpose.

Do the setup in the Muse app or at muse.ai. You can talk to Muse in WhatsApp too, but nothing we found shows its secure key prompt opening there.

Muse may ask before it reaches ihateposting.com, and before it schedules or changes a post. Meta says each approval covers only that type of action, and Muse picks which options to offer — once, for this task, for this site or always — so a later post may still ask. You choose how often it asks in Settings → Permissions.

To cut Muse off after a sign-in, remove its connection in Settings → Developers; that stops Muse alone. If it used a key instead, regenerate the key there — iHatePosting has one key per account, so that also stops every other tool using the old key until you give it the new one.

Limits. Muse is free with a usage limit, and Meta sells Power and Max plans for more. It needs a Meta account and is rolling out in the US on iOS, Android and muse.ai. Meta does not review custom connectors, and because Muse builds this one itself, it is a less certain route than a settings screen — we have not yet run it end to end. If it will not connect, tell us through the contact page.

Meta's own documentation: Muse help

Nothing goes out unless you say so

Every post Muse writes is saved as a draft in iHatePosting unless you ask for it to be published now or at a set time. Publishing, rescheduling, retrying and deleting are marked as actions that change things, so clients that honour those markings ask you before they run them. Deleting a post in iHatePosting never removes one that is already live on a network.

What is the iHatePosting MCP?

MCP — the Model Context Protocol — is the standard way an assistant plugs into an app it does not own. Our server exposes the accounts you have connected to Muse as tools, so it can draft, check and schedule without you opening a dashboard.

How Muse uses it

You add the connector once — by signing in, or with a key you create
Muse reads which accounts you have connected, and each network's rules
It writes a version per network and checks it against those rules before sending
It saves a draft, schedules it, or publishes — exactly as your message said
It works alongside whatever other tools Muse already has

tools Muse can call

# read and check (9)
whoami              list_accounts
list_posts          get_post
get_analytics       get_platform_rules
list_media          list_pinterest_boards
validate_post

# write (7)
create_post         update_post
reschedule_post     delete_post
retry_post          upload_media
open_upload_widget

Cost, access and what to do when it breaks

What does it cost?

The connector costs nothing on top of iHatePosting. iHatePosting has one plan: $15/month billed annually, or $19/month billed monthly, with unlimited social accounts. It is free for 90 days, no credit card needed, and everything is included during the trial: unlimited accounts, unlimited posts, every feature.

How is access secured?

Either you sign in to iHatePosting and approve access, or you create an API key in Settings → Developers. That page can show your key again whenever you need it. Whichever route you take, it reaches only the accounts you have already connected, and you can revoke it at any time without touching the accounts themselves.

Something not working?

It cannot see any accounts: connect them in iHatePosting first, then ask it to list them again.
You regenerated your key and it still fails: Regenerate revokes the old key the moment you press it, and a client that is already running keeps sending the old one until you genuinely restart it.
A post failed: open it in iHatePosting — the failure names the network and repeats what that network actually said.

Frequently asked questions

How do I add iHatePosting to Muse?

Muse has no settings screen for MCP servers. Send it the message on this page, which names the address, the transport and the header, and asks Muse to build the connector and prove it by calling whoami and listing your accounts.

Does Muse need an API key?

Not if it signs in. iHatePosting answers Muse's first call with the sign-in address, and Muse opens it in your browser. If Muse asks for a key anyway, give it only through Muse's secure credential prompt, never in the chat; do that in the Muse app or at muse.ai, because nothing we found shows that prompt opening in WhatsApp.

How do I stop Muse using my account?

If Muse signed in, remove its connection in Settings → Developers and Muse alone loses access. If it used a key, regenerate the key there — iHatePosting has one key per account, so that also stops every other tool using the old key until you give it the new one.

Is the Muse connector free?

Yes. The connector costs nothing on top of iHatePosting, and iHatePosting is free for 90 days, no credit card needed. After that it is $15/month billed annually, or $19 month-to-month, with unlimited accounts.

Which networks can Muse post to?

Any account you have connected in iHatePosting, across 15 networks: Instagram, Facebook, LinkedIn, X, Threads, TikTok, YouTube, Pinterest, Bluesky, Mastodon, Telegram, Discord, Slack, Tumblr and Google Business Profile.

Can Muse schedule posts for a specific date and time?

Yes. Put the date and time in the prompt — for example "schedule this for Friday at 9:00 AM" — and Muse schedules the post for then. iHatePosting reads the time in your account's timezone, and you can ask Muse to move a scheduled post to a new time.

One connection reaches every network

Connect your accounts in iHatePosting once. From then on Muse can post to any of them, and we publish at the time you set — even after you close the chat.