X (Twitter) posts with Muse and Bolta
Queue social posts from Muse Code, Meta's terminal agent. Parts of the Muse route are not confirmed yet, and the note below says which. Nothing goes live on X until you say yes.
Partly confirmed, see what is and is notChecked 2026-11-21
This is the Muse Code path. We have not confirmed a way to add Bolta in the Muse app or from WhatsApp.
Write three X posts about the feature we just shipped and save them as drafts
Illustration of the reply: Bolta returns a draft showing the connected account and the scheduled time, with Approve, Edit and Reject actions.
What is and is not confirmed
Read this before you set up Muse
- Confirmed in Meta's Muse Code docs: remote MCP servers over streamable_http, an mcp_servers block in ~/.config/muse/settings.json, and OAuth sign-in with muse mcp login.
- Not confirmed: that the Muse app (phone, desktop or WhatsApp) accepts a Bolta MCP link. Meta says the app has custom connectors, but we could not read the steps.
- Not tested end to end: nobody has run a full draft, review and schedule round trip through Muse Code with Bolta yet.
- Not confirmed: how to send an API key in the headers field, and whether the optional Bolta skill shows up in muse skills list.
What Bolta does on X
Bolta reads the limit for each connected X account, so a Premium account and a free account get different ceilings. Text that is too long does not get trimmed on X: the post fails, so the draft has to fit first.
- Single posts and threads. In a thread, Bolta posts every part after the first as a reply to the one before.
- Images. A post needs text: an image with no text is not supported on X.
X limits and format rules
Network rules last checked 2026-07-28. Bolta's posting rules for your workspace (get-posting-rules) win if they differ from this page.
Not promised for X from Muse: Polls and Spaces announcements. Neither is confirmed for Bolta. How many hashtags work best. Bolta checks none, and this page makes no claim about it.
| What to know | X's own rule | What Bolta does |
|---|---|---|
| Post length | Accounts without a paid subscription are limited to 280 characters. X Premium subscribers can publish up to 25,000. | Bolta reads the limit per account. Longer text makes the post fail, so shorten it first. The 25,000 limit is a ceiling for Premium accounts, and X can still refuse a long post. |
| Links and media | A pasted link counts as 23 characters however long it is. Photos, videos and GIFs count as zero characters. | Bolta does not check how many hashtags you use or their format. They are kept as typed. |
| Threads | Posts can be chained into a thread, and each post carries its own separate character limit. | Each X thread part after the first is posted as a reply to the one before it. |
| Who can reply | Replies can be limited to everyone, accounts you follow, verified accounts, or only the accounts you mention. It is chosen before you post. | The default is that anyone can reply unless you limit it. |
| Video | Not stated on this page. | Video on X is checked on X's side for duration, format and posting eligibility, so a successful upload does not guarantee publication. Ask for the posting rules before you attach one. |
Muse jobs for X, and how to write them
- Have Muse Code read a README or docs page in your repo and draft posts that explain it
- Pull recent post results into the terminal before you plan the next batch
- Write to 280 unless the account has X Premium. Check the count, because a post over the limit fails instead of being cut.
Example prompts for X
Things to type in Muse. Each one asks for a draft and shows you the text first.
Write three X posts about the feature we just shipped and save them as drafts
Plan a weekly Friday recap post for the engineering blog, drafts only.
Read the top entry in CHANGELOG.md and draft an X post about it that fits in 280 characters
Look at the newest tagged release and draft an X post with a link to it
Bolta saves a draft, you read the exact text, you say yes
- 01
Bolta saves a draft
Muse asks Bolta for the X post in your brand voice (save-post). A saved draft is never public.
- 02
You read the exact text
On X the exact text includes the character count with links counted at 23, and, for a thread, every part in order.
- 03
You say yes
Only then does Bolta schedule or publish (publish-post), in your workspace's timezone. Safe Mode, client sign-off and brand approval rules still apply.
Using Muse for X
Parts of this route are not confirmed. The note above says which.
For X, Muse, from Meta, reaches Bolta through mcp_servers entry in the Muse Code settings file (streamable HTTP). Sign-in: Sign in (OAuth) with muse mcp login. The X account itself is connected inside Bolta, not in Muse.
Muse Code is Meta's terminal agent and the route this page covers. An X draft from the Muse app on phones, desktop or WhatsApp is not confirmed, so this page does not promise it.
An illustration from the Muse guide, not real output. You ask: How did my last five posts do? Suggest what to post next. The reply goes along these lines: Here are the results for your last five posts, with the strongest one first. I suggest a follow-up on that topic. I have not drafted or scheduled anything. Read only. Nothing changed.
Meta lists a headers field for streamable_http servers, and Bolta accepts a Bearer bolta_sk_ API key, so a header may work for a headless machine. We have not confirmed the exact format Muse Code expects, so check Meta's configuration page before you rely on it.
Muse Code suits people who already keep a repo open. The release notes, the docs and the commit history are one folder away, so a draft can start from the thing you just shipped instead of a blank box.
A saved draft appears in Bolta's review queue with the text you saw in the terminal.
- Draft from what is in your repo. Muse Code can read a changelog, README or docs page in your working folder and hand the text to Bolta as a draft in your voice.
- Approve after your yes. Once you say yes to named drafts, Muse Code passes the content fingerprint back, so a post that changed in between is not approved by mistake.
- Muse Code lists Bolta's tools. Over streamable HTTP at https://mcp.bolta.ai/mcp, Muse Code asks Bolta what it offers. /mcp shows the result as a live list.
- Your request becomes a read of your brand. For a post, Muse Code first checks your brand and voice before writing anything.
- Setup: Optional: add the Bolta skill. Run npx skills add boltaai/bolta-skills --skill bolta, then muse skills list. Muse Code reads ~/.agents/skills and ~/.claude/skills. If Bolta does not appear, skip it, because the connection works without it.
- Setup: Run a read-only check first. Ask: List my Bolta brands and the accounts connected to each. Do not change anything. Then ask for one draft and read the exact text back before you approve it in Bolta.
- Muse Code: mcp_servers entry plus muse mcp login. Documented by Meta, not run with Bolta (streamable_http, OAuth sign-in). Not yet run as a full draft-to-schedule round trip with Bolta.
- A routine saves switched off. Turning it on takes its own yes from you.
- Muse Code. Choose this if you work in a terminal and want Bolta connected today. Meta documents mcp_servers in the settings file, the streamable_http transport and OAuth sign-in with muse mcp login. That is the path this page walks through.
Connect Muse to Bolta
This is the Muse Code path. We have not confirmed a way to add Bolta in the Muse app or from WhatsApp.
X questions, answered for Muse
- What happens if Muse writes an X post that is too long?
- The post fails. Bolta does not trim X text, so Muse has to shorten it first. The limit is 280 characters for accounts without a paid subscription, and X Premium accounts can post up to 25,000, though X can still refuse a long post.
- Can Muse write an X thread?
- Yes. Ask for several parts, and Bolta posts each part after the first as a reply to the one before it, so they read as one thread. Each part carries its own limit. You read all of the parts in Muse and say yes before any of them goes out.
- Does Muse need an API key for Bolta?
- Not for the normal route. muse mcp login bolta signs you in through the browser and there is no key to copy. A Bearer bolta_sk_ key is an option for machines with no browser, but we have not confirmed the exact headers format in Muse Code.
- Does the Bolta skill work in Muse Code?
- It may. Meta documents ~/.agents/skills and ~/.claude/skills as skill folders for Muse Code. We have not checked where the skills command puts Bolta, so if muse skills list does not show Bolta, skip it. The connection works without a skill.
- Has this been tested end to end?
- No. The settings format and sign-in command come from Meta's documentation, but nobody has run a full draft, review and schedule through Muse Code with Bolta. Claude Code and Codex have their own Bolta pages if you want another terminal agent.
- bolta is missing from /mcp
- Check the entry sits inside mcp_servers, the transport is streamable_http and the url is https://mcp.bolta.ai/mcp. Close Muse Code and reopen it.
- Does Muse publish X posts without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that X post. Whether Muse completes the connection is not fully confirmed, so read the note above first.
More from Muse
Muse can work with the other networks Bolta publishes to. Each page has its own limits and review notes.
X from other AI agents
The same X limits apply whichever agent asks. The connection and the setup are what change.
Try an X draft from Muse
Connect Muse, ask for an X draft and read the exact text. Nothing goes live until you say yes.