Use Chirpie with Meta Muse

Verified 2026-09-28. Chirpie's side (the server at https://chirpie.ai/mcp, OAuth 2.1 with PKCE and dynamic client registration, API keys) was checked against the live server. Muse's side is from Meta's launch announcement of 2026-09-08 and published setup guides for Muse custom connectors; Meta's own help text for custom connectors could not be confirmed, so the wording in the Muse app may differ.

How do I let Muse post to social media?

Add Chirpie to Muse as a custom connector: start a conversation in Muse, give it the address https://chirpie.ai/mcp, and approve the Chirpie sign-in link Muse sends back. Muse can then publish, schedule and thread posts on the X, Bluesky, LinkedIn, Mastodon and Telegram accounts you connected to Chirpie, save drafts, and read each post's analytics and comments. Threads, Instagram and Facebook are coming soon.

Muse is Meta's personal AI agent, available in the US on iOS, Android and muse.ai. Its built-in connectors for Meta's own apps read your content and messages; Chirpie is what gives it somewhere to publish.

Before you start

1. A Chirpie account. Sign up free.
2. At least one social account connected in the dashboard: X and LinkedIn connect with OAuth, Mastodon with OAuth on your own instance, Bluesky with an app password and Telegram with a bot token. You can also connect accounts later by asking Muse.
3. Muse, on the app or at muse.ai.

Add Chirpie to Muse

Muse has no settings screen for custom connectors. You add one by asking in a conversation.

1. Open Muse and start a new conversation.
2. Send this message:

Add a custom connector for Chirpie.
It is a remote MCP server over
Streamable HTTP at
https://chirpie.ai/mcp
with OAuth sign-in. Send me the
sign-in link and I will approve it.

3. Muse replies with a Chirpie sign-in link. Open it and sign in to Chirpie (the flow is below).
4. Muse confirms the connector was added. Ask it "what Chirpie tools do you have?" to check.

Only remote servers work, because Muse runs its tasks in Meta's cloud rather than on your device. https://chirpie.ai/mcp is hosted, so there is nothing to run yourself.

If Muse asks for an API key instead

Muse can also connect with a key sent as a bearer token. Create one in the Chirpie dashboard and narrow it with scopes to what Muse needs, for example posts:read, posts:write, media:write, accounts:read, analytics:read and comments:read, plus accounts:write if Muse should connect new accounts for you. Leave out keys:write, so a key held by Muse cannot create more keys.

Enter the key only in Muse's secure credential prompt rather than in the chat itself, and tell Muse it goes in the Authorization header as Bearer chirpie_sk_…. Revoke it from the dashboard whenever you like.

What the sign-in looks like

Chirpie's MCP server uses OAuth 2.1 with PKCE (S256) and registers new clients automatically, so Muse needs no client ID or secret from you.

1. The link Muse sends opens the Chirpie sign-in page on chirpie.ai. Check the address before you type anything.
2. Sign in with your Chirpie email and password. If you are already signed in to chirpie.ai in that browser, it skips straight on.
3. Chirpie returns you to Muse, which now holds an access token for the MCP server. Muse does not receive your Chirpie password or any social platform password.

A sign-in grant cannot create or revoke Chirpie API keys; everything else, from posting to connecting new accounts, works.

What can I ask Muse to do?

• "Post 'Doors open at 6pm tonight, see you there' to our X and Bluesky accounts, and use a shorter version on Bluesky."
• "Write three LinkedIn posts about our product launch and schedule them for Monday, Wednesday and Friday at 9am Eastern."
• "How did last week's Mastodon posts do? List the replies I haven't answered."

Every tool Muse can use, with its parameters, is listed on the MCP Server page. Scheduling rules are in Scheduling.

Frequently asked questions

Is Chirpie in the Muse connector directory?

No. Chirpie is not listed in Muse's directory of approved connectors. You add it yourself as a custom connector by giving Muse the address https://chirpie.ai/mcp, which works without a directory listing.

Can Muse post to Instagram, Facebook or Threads through Chirpie?

Not yet. Instagram, Facebook and Threads are coming soon to Chirpie. Today Muse can publish through Chirpie to X, Bluesky, LinkedIn, Mastodon and Telegram.

Should I connect with sign-in or with an API key?

Sign-in is simpler, because there is no key to create or store. If Muse asks for a key instead, create a Chirpie API key limited to the scopes Muse needs and enter it only in Muse's secure credential prompt, not in the chat. You can revoke it from the Chirpie dashboard at any time.

Does Muse need my social media passwords?

No. Your X, LinkedIn, Bluesky, Mastodon and Telegram accounts are connected to Chirpie, and Muse only ever holds a Chirpie credential. Chirpie publishes on your behalf and refreshes the platform tokens itself.

Does posting from Muse cost anything extra?

No. Posts made from Muse count against your Chirpie plan's monthly post quota exactly as posts made from the API or the dashboard do, and the hosted MCP server is included on every plan, including the free one.

Sources: Introducing Muse (Meta, 2026-09-08), Muse Connector Platform, Meta Muse custom integrations (Parallel).