Use Chirpie with Meta Muse
Add Chirpie to Meta Muse as a custom connector so Muse can publish and schedule posts to X, LinkedIn, Bluesky, Threads, Mastodon, Instagram, Facebook and Telegram.
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, Threads, Mastodon, Instagram, Facebook and Telegram accounts you connected to Chirpie, save drafts, and read each post's analytics and comments.
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
- A Chirpie account. Sign up free.
- 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.
- 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.
- Open Muse and start a new conversation.
- 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.- Muse replies with a Chirpie sign-in link. Open it and sign in to Chirpie (the flow is below).
- 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.
- The link Muse sends opens the Chirpie sign-in page on
chirpie.ai. Check the address before you type anything. - Sign in with your Chirpie email and password. If you are already signed in to chirpie.ai in that browser, it skips straight on.
- Chirpie asks what Muse may do: Full access (the default) or Read only. Pick one and choose Allow.
- 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.
With Read only, Muse is offered only the tools that read and Chirpie refuses anything else on that connection, naming the permission it would need. That is the read-only connection Muse's connector guidelines ask for. See Read only or full access.
A sign-in grant cannot create, list or revoke Chirpie API keys, or remove your own X developer app: those four tools are only offered to a connection that authenticates with an API key. With Full access, 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.
What each tool may do
Muse classifies every tool as a read, a write or a sensitive write, and asks before a sensitive write every time. The table is how Chirpie classes its own tools, and the read-only and destructive hints the server sends say the same thing; Muse applies its own policy to those hints, so check its connector settings for what it asks about.
| Tool | Class | What it does and what follows |
|---|---|---|
chirpie_list_accounts | Read | Lists the connected accounts and whether each can publish. |
chirpie_list_posts, chirpie_get_post | Read | Lists or reads posts, drafts and their status. Nothing changes. |
chirpie_analytics | Read | Reads engagement for a published post; refresh asks the platform now, within a per-post floor. |
chirpie_list_comments | Read | Reads the comments on a post you published; a sync may fetch from the platform. |
chirpie_get_x_keys_status | Read | Says whether your own X developer app is registered. Never returns a secret. |
chirpie_upload_media | Write | Stores a file for seven days so a post can attach it. Publishes nothing. |
chirpie_hide_post, chirpie_unhide_post | Write | Changes only what Chirpie lists. Nothing reaches a platform, and it is reversible. |
chirpie_hide_comment | Write | Hides or unhides a comment on the platform. Reversible. |
chirpie_activate_account | Write | Lets a connected account publish again. Reversible. |
chirpie_connect_x, chirpie_connect_linkedin, chirpie_connect_threads, chirpie_connect_instagram, chirpie_connect_facebook, chirpie_connect_mastodon, chirpie_connect_bluesky, chirpie_connect_telegram | Write | Starts a connection: an authorization link you open, or a credential you provide. Nothing is posted. |
chirpie_list_keys | Read | Lists your API keys by prefix. Never returns a full key. |
chirpie_create_key, chirpie_revoke_key | Sensitive write | Creates a new API key, optionally narrowed with scopes, or revokes one. A revoked key stops working at once. |
chirpie_set_x_keys, chirpie_remove_x_keys | Write | Registers or removes your own X developer app. Replaces any app already set. |
chirpie_post, chirpie_thread | Sensitive write | Publishes to a social network now, or queues it for a scheduled time, and spends quota. A thread is all or nothing. |
chirpie_update_post | Sensitive write | Edits a queued post or a draft. With publish or schedule_at it sends a draft, so it is treated as publishing. |
chirpie_reply_to_comment, chirpie_retry_first_comment | Sensitive write | Publishes a reply under a post. |
chirpie_delete_post, chirpie_delete_comment | Sensitive write | Removes a post or comment from the platform. Chirpie keeps its own record marked deleted. Cannot be undone. |
chirpie_deactivate_account, chirpie_disconnect_account | Sensitive write | Stops an account publishing and cancels its scheduled posts. Disconnect also removes the connection. |
Publishing and deletion wait for the platform: a post is reported published only once the platform returned its id, and a published post is reported deleted only once the platform confirmed it is gone. chirpie_hide_post changes only Chirpie's listings, so its result is Chirpie's own. A failed thread names what happened: upstream_error means nothing is left on the platform and a retry is safe, while thread_rollback_incomplete names the parts still live, so a retry would publish them again. A transport failure may carry only a message.
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?
Yes. Connect an Instagram professional account, a Facebook Page or a Threads account to Chirpie, and Muse can publish, schedule and thread posts there like on every other network. Chirpie publishes to X, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook 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.
Can I give Muse read-only access to Chirpie?
Yes. After you sign in, Chirpie asks whether Muse gets Full access or Read only. Read only lets Muse list your accounts and read your posts, analytics and comments, and Muse is not offered any tool that publishes, edits, deletes or connects anything. This is the read-only connection Muse's connector guidelines ask for. To switch, remove Chirpie from Muse, add it again and choose the other option.
Does Muse need my social media passwords?
No. Your social 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).
Use Chirpie with ChatGPT
Add https://chirpie.ai/mcp to ChatGPT as a developer-mode app, or to the OpenAI Responses API, and let it publish and schedule posts to X, LinkedIn and more.
n8n
Post to X, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook, and Telegram from an n8n workflow with the @chirpie/n8n-nodes-chirpie community node, covering posting, threads, scheduling, accounts, analytics, and AI Agent tool use.