Mastodon posts with Grok Build and Bolta
Draft posts about your release without leaving Grok Build. Parts of the Grok Build route are not confirmed yet, and the note below says which. Nothing goes live on Mastodon until you say yes.
Partly confirmed, see what is and is notChecked 2026-11-21
One command to add Bolta, then a browser sign-in the first time Grok uses it. There is no key to copy.
Read the top entry in CHANGELOG.md and draft a Mastodon post about it inside my instance's limit
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 Grok Build
- Confirmed from xAI's own docs: grok mcp add --transport http adds a remote server, and a remote server that needs sign-in opens a browser on first use.
- Confirmed from the Bolta side: the server address is https://mcp.bolta.ai/mcp, and Bolta's approval rule applies to every AI app that connects.
- Not confirmed: a complete draft, review and schedule run through Grok Build. Nobody at Bolta has done one, and Claude Code remains the most tested path.
- Not confirmed: whether the Bolta plugin loads fully in Grok Build. xAI's overview says you need an xAI account or an API key, and we could not settle the plan question.
What Bolta does on Mastodon
The text limit on Mastodon is set by your own instance, and Bolta reads it for the connected account instead of using one fixed number. The usual limit is 500 characters.
- Text posts, within the limit your instance sets.
- Public posts by default, or another visibility if you set it.
Mastodon limits and format rules
Bolta's posting rules for your workspace (get-posting-rules) win if they differ from this page.
Not promised for Mastodon from Grok Build: Polls, threads and instance-specific features. None is confirmed for Bolta. Any rule from a particular instance. Each instance sets its own, so check yours.
| What to know | Mastodon's own rule | What Bolta does |
|---|---|---|
| Post length | Not stated on this page. | Set by your instance. Bolta reads it per account, and the usual limit is 500. Text over the limit is trimmed back to the last whole sentence or word that fits. |
| Visibility | Not stated on this page. | Public unless you set another visibility. |
| Formatting | Not stated on this page. | Mastodon posts are plain text here. Markdown is flattened, and #hashtags and @mentions stay as typed. |
| Finding conversations | Not stated on this page. | Hashtag-based. The query is folded into a single tag, because full-text status search is unavailable on most instances. |
Grok Build jobs for Mastodon, and how to write them
- Draft a short thread from a git log summary of what changed this sprint
- Write a founder-style build update from the notes you keep in the repo
- Ask for your instance's limit before drafting. It differs from instance to instance.
Example prompts for Mastodon
Things to type in Grok Build. Each one asks for a draft and shows you the text first.
Read the top entry in CHANGELOG.md and draft a Mastodon post about it inside my instance's limit
Which social accounts does the Acme brand have connected? Change nothing
Turn the release notes into a Mastodon post with one relevant hashtag and show it to me first
Which of my recent posts got the most replies, and what does that suggest for the next one?
Bolta saves a draft, you read the exact text, you say yes
- 01
Bolta saves a draft
Grok Build asks Bolta for the Mastodon post in your brand voice (save-post). A saved draft is never public.
- 02
You read the exact text
On Mastodon the exact text includes its visibility, because the default is public, and where the limit for your instance would cut it.
- 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 Grok Build for Mastodon
Parts of this route are not confirmed. The note above says which.
For Mastodon, Grok Build, from xAI, reaches Bolta through One grok mcp add command (hosted MCP server). Sign-in: Browser sign-in (OAuth), or a Bolta key for scripts. The Mastodon account itself is connected inside Bolta, not in Grok Build.
Grok Build is xAI's terminal coding agent, not the Grok chatbot. It suits turning a changelog or release note into a Mastodon draft without leaving the terminal.
An illustration from the Grok Build guide, not real output. You ask: I want a routine that drafts a release post each Friday. Show me the plan before saving anything. The reply goes along these lines: The plan covers what it drafts, which day, and where drafts go for review. Once active it runs on Bolta, not in this terminal. It saves switched off. Confirming the plan is one yes, switching it on is another. Plan shown. Waits for your yes.
An illustration from the Grok Build guide, not real output. You ask: Did my Friday release routine run this week, and is anything from it unreviewed? The reply goes along these lines: I checked the routine runs and your review list. Any draft a run produced is still waiting for you, and I have changed nothing. I can show the text of any of them. Read only. Nothing approved.
Grok Build is xAI's command-line agent. If a CHANGELOG.md, release notes or a git history already sit beside your code, Bolta covers the part Grok does not: writing from that material in your own voice, then holding the result for your review.
It is a poor fit if you only want a chat window. For that, use Bolta from one of the chat assistants in the agents directory.
Needs: a Bolta account with at least one brand, and a browser for the one-time sign-in
- Approve with the exact text. When you pick items, Grok shows each one first. Approval is tied to the text you saw, so an edited post is not approved by accident.
- Check what happened to your routines. Ask whether Friday's run produced drafts and what is still unreviewed, from the terminal beside your code.
- Grok finds your brand. One connection can reach several brands, so Grok lists them first and uses the one you named in your message.
- You decide. Say yes with a time to queue it, ask for a change, or reject it. Publishing only happens after that yes, and Bolta refuses it otherwise.
- Setup: Add Bolta with one command. Paste grok mcp add --transport http bolta https://mcp.bolta.ai/mcp and press Enter. The word bolta is the name Grok will use. No browser opens yet, because the command only saves the address.
- Setup: Check that it was saved. Run grok mcp list and look for a server named bolta. If it is missing, run the add command again.
- Bolta skill (npx skills add boltaai/bolta-skills --skill bolta). Teaches Grok your voice, the review list and routines. Restart grok and type /skills to see whether it loaded.
- Approving or scheduling from Grok still needs you in the session, replying yes to the exact text.
- MCP command and skill. Choose this if you want the shortest, best documented path. Run the grok mcp add command, sign in, then add the skill with npx skills add boltaai/bolta-skills --skill bolta. Every step here is in xAI's docs or the Bolta setup guide.
Connect Grok Build to Bolta
One command to add Bolta, then a browser sign-in the first time Grok uses it. There is no key to copy.
Mastodon questions, answered for Grok Build
- What is the Mastodon character limit for a post from Grok Build?
- It depends on your instance. Bolta reads the limit for the connected account, and the usual limit is 500 characters. Anything over it is trimmed back to the last whole sentence or word.
- Are Mastodon posts from Grok Build public?
- Yes, unless you set another visibility. Say who may see the post when you ask, and check it when you read the draft.
- Do I need an API key to connect Bolta to Grok Build?
- Not for the usual setup. Bolta signs you in through the browser and you copy nothing. A bolta_sk_ key is an option for scripts, passed with --header, which xAI documents for static tokens but we have not tested against Bolta.
- Will Grok post to my accounts while I am away from the terminal?
- No. Grok Build only acts during a session you started, and publishing needs your yes to the exact text. A Bolta routine can keep drafting while the terminal is closed, but its drafts wait in your review list.
- Bolta shows up twice in /mcps
- Your manual command and a plugin or Claude Code config may both have added it. Run grok mcp remove bolta to drop the manual one and check with grok mcp list.
- Grok asks which brand, or a call mentions workspace_id
- One connection can reach several brands, so each request has to name one. Say it in your message, for example: For the Acme brand, list my drafts.
- Does Grok Build publish Mastodon posts without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that Mastodon post. Whether Grok Build completes the connection is not fully confirmed, so read the note above first.
More from Grok Build
Grok Build can work with the other networks Bolta publishes to. Each page has its own limits and review notes.
Mastodon from other AI agents
The same Mastodon limits apply whichever agent asks. The connection and the setup are what change.
Try a Mastodon draft from Grok Build
Connect Grok Build, ask for a Mastodon draft and read the exact text. Nothing goes live until you say yes.