Draft posts about your release without leaving Grok Build

Schedule social media posts with Grok Build

Grok Build is xAI's terminal agent. Add Bolta to it with one command and it can draft posts in your brand voice from a changelog or release note, show what is waiting for review, and read your analytics. Nothing is approved, scheduled or published until you say yes to the exact text.

  • Paste one command in a terminal, then sign in once in the browser
  • Ask for posts from CHANGELOG.md or your release notes
  • Drafts save and wait. Nothing goes out until you say yes

Nothing is approved, scheduled or published 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.

GrokBolta connected

Reply to today's comments on our posts. Skip the trolls.

Thinking…

Calling bolta/list-engagements → done

Calling bolta/draft-engagement-reply → done

9 of the 23 comments were worth answering. The replies are drafted in your voice and waiting in your Bolta inbox. Nothing posts until you say yes.

Two steps

Connect, then ask

  1. 01

    Paste one command

    In any terminal run grok mcp add --transport http bolta https://mcp.bolta.ai/mcp. It only saves the address. Then start grok and ask about Bolta, and a browser opens for sign-in.

  2. 02

    Ask for your first drafts

    Try: Summarize what changed in this repo today as one LinkedIn draft for my brand. Save it as a draft and do not schedule it.

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.
Behind the prompt

How Grok Build uses Bolta

Grok Build does the reading and writing in your terminal. Bolta holds your voice, your rules, your review list and your accounts. Each step below names the Bolta tool involved.

  1. 01

    Grok finds your brand

    One connection can reach several brands, so Grok lists them first and uses the one you named in your message.

    list-workspaces

  2. 02

    It checks which accounts can be posted to

    Only accounts you connected in Bolta are available. If a network is missing, Grok asks Bolta for a connect link instead of guessing.

    list-accounts

  3. 03

    It loads your voice

    Before writing, Grok reads how your brand sounds from Bolta, so a launch post from CHANGELOG.md does not read like generic release-note copy.

    get-voice-context

  4. 04

    It reads the posting rules

    Length limits and approval rules for the network are fetched so the draft fits and Grok knows what needs a person's yes.

    get-posting-rules

  5. 05

    It saves a draft and shows you the text

    The post is saved as a draft in Bolta. Grok prints the exact words in the terminal and stops there.

    save-post

  6. 06

    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.

    publish-post

Setup

Set up Grok Build

Connect once. Everything below works from Grok Build afterwards.

  1. 01

    Install Grok Build if you do not have it

    On macOS or Linux run curl -fsSL https://x.ai/cli/install.sh | bash. On Windows PowerShell run irm https://x.ai/cli/install.ps1 | iex. Then run grok --version. If it prints a version, you are ready.

  2. 02

    Open a terminal

    You do not need to be inside a project folder. By default the connection is saved to your user config, so Bolta works from any folder.

  3. 03

    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.

  4. 04

    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.

  5. 05

    Sign in the first time Grok uses Bolta

    Start grok and ask anything about Bolta. A browser opens on bolta.ai. Sign in, tick the brands this app may reach (one connection is one organization), and approve. If no window opens, type /mcps inside Grok, select Bolta and press i.

  6. 06

    Run the doctor check

    Back in the terminal, outside Grok, run grok mcp doctor bolta. It checks the configuration and the connection. If it reports a problem, fix that before going on.

  7. 07

    Add the Bolta skill

    The connection lets Grok reach Bolta. The skill teaches it your voice, the review list and routines. Run npx skills add boltaai/bolta-skills --skill bolta, or use the plugin route in the section below. Restart grok afterwards and type /skills to check that it is listed.

  8. 08

    Avoid a double install

    If you used the plugin and /mcps now shows Bolta twice, run grok mcp remove bolta to drop the one you added by hand, then grok mcp list to check.

  9. 09

    Run a read-only check, then a real task

    Ask: List my Bolta brands and the accounts connected to each one. Do not change anything. Then try: Write three draft posts for next week and save them as drafts. Do not schedule them.

Connect

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.

Connection methods

Ways to connect Grok Build to Bolta

Honest status for each route, based on xAI's documentation and Bolta's own setup guide.

Ways to connect Grok Build to Bolta
MethodWith Grok BuildHow
grok mcp add (hosted MCP, browser sign-in)Not confirmedDocumented by xAI for remote servers and the recommended route here. Nobody at Bolta has run a full draft, review and schedule through it yet.
Bolta key with --headerNot confirmedxAI documents the --header option for a bearer token. Use a bolta_sk_ key only for scripts. Not checked against Bolta.
Bolta skill (npx skills add boltaai/bolta-skills --skill bolta)Not confirmedTeaches Grok your voice, the review list and routines. Restart grok and type /skills to see whether it loaded.
Claude Code plugin from boltaai/bolta-skillsNot confirmedxAI says Grok Build reads Claude Code plugins and marketplaces, but the exact plugin commands in Grok were not confirmed.
Grok app or grok.comNot confirmedBolta has not documented this, so we do not claim it. This page covers Grok Build only.
Capabilities

What you can run in Bolta from Grok Build

Each row is an area of Bolta, with the real tools behind it.

  • Turn release material into drafts

    Point Grok at CHANGELOG.md, release notes or a git log summary and get a draft per network, written in your brand voice and saved for review.

    get-voice-contextget-posting-rulessave-post

  • See what is waiting for you

    Ask what needs approval and Grok lists the drafts, reply suggestions and posts sent for review, without approving any of them.

    list-inbox-items

  • 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.

    approve-many-postsreject-post

  • Plan a repeating release post

    Describe a weekly routine, read the plan, then confirm it. It saves switched off and needs a second yes to turn on.

    planconfirm-plancreate-routineactivate-routine

  • Check what happened to your routines

    Ask whether Friday's run produced drafts and what is still unreviewed, from the terminal beside your code.

    list-routine-runslist-workspace-posts

  • Read results before you plan

    Pull analytics for connected accounts and use what did well to shape the next drafts.

    list-accountsget-account-analytics

In practice

A release day in the Grok Build terminal

An illustration of the shape of a session. Your replies and Grok's wording will differ.

IllustrationNot real output
  1. You

    We tagged v2.0 today. Use the top entry in CHANGELOG.md and draft a LinkedIn post for the Acme brand. Drafts only.

  2. Tool call
    list-workspaces

    Found the Acme brand and its connected accounts.

  3. Tool call
    get-voice-context

    Loaded the Acme voice: plain, first person, no hype.

  4. Tool call
    get-posting-rules

    LinkedIn length limit and approval rule fetched.

  5. Grok Build

    I read the v2.0 entry. It lists a faster importer, a fix for duplicate rows and a new export option. The duplicate-row fix is the most concrete of the three, so I will lead with it. Saving a draft now.

  6. Tool call
    save-post

    Draft saved for LinkedIn. Status: draft, not scheduled.

  7. Grok Build

    Draft saved. Here is the exact text: "v2.0 is out. The importer is faster, duplicate rows are fixed, and you can now export to CSV. If you hit a duplicate before, tell us if it is gone." It is not scheduled. Want a change, or should I queue it?

  8. You

    Cut the last sentence and make it Tuesday 9am. I need to see it again first.

  9. Tool call
    save-post

    Draft updated with the shorter text. Status: draft, not scheduled.

  10. Grok Build

    Updated text without the last sentence, still a draft. Nothing is scheduled. Reply yes and I will queue it for Tuesday 9am.

  11. You

    Not yet. I will look after standup.

  12. Grok Build

    Understood. The draft stays saved and unscheduled until you say yes.

Which route

MCP only, or MCP plus the plugin?

Both reach the same Bolta. The difference is how much Grok knows about using it.

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.

Claude Code plugin route

Choose this if you already keep Claude Code plugins.

xAI says Grok Build reads Claude Code marketplaces, plugins, skills and MCP servers. You can install the Bolta plugin from boltaai/bolta-skills, but the exact plugin commands in Grok were not confirmed, so treat this as the second choice.

Use cases

What can Grok Build do with Bolta?

  • Turn one CHANGELOG.md entry into a LinkedIn launch post and a shorter X version, both saved as drafts
  • 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
  • Glance at what is waiting for review in Bolta while your terminal is still open beside the code
  • Read how last week's posts did before you plan this week's, from the same terminal
  • Set up a weekly routine that drafts a release post for your review every Friday
The connection

What is the Bolta MCP?

The server Grok Build talks to when it works with Bolta.

MCP, the Model Context Protocol, is the open standard that lets an AI app call tools in another product. Bolta runs a hosted MCP server at https://mcp.bolta.ai/mcp. Your AI app discovers its 67 tools and calls them for you: list your brands, save a draft, plan a routine, read results.

One connection is one organization. You tick the brands the app may reach, and every call is checked against your role, so the app can never do more in Bolta than you can. Approving, scheduling and publishing need your yes.

  • Brands & accounts6 tools

    The brands this connection reaches, who works on them and who can approve, their approval settings, connected social accounts, and each platform's posting rules.

    list-workspaces, list-workspace-members, set-brand-approval, list-accounts, get-connect-link, get-posting-rules

  • Posts9 tools

    Save a draft or edit a post with save-post, then publish it now or at a time with publish-post after the user says yes.

    list-workspace-posts, get-post, save-post, publish-post, delete-post, bulk-create-posts, create-wordpress-blog-post, list-recently-deleted, restore-deleted

  • Review4 tools

    Everything waiting for a yes: submit drafts to the team or send them to a named person for approval, approve one or many, reject with a reason, and work the inbox of routine and campaign drafts.

    list-inbox-items, submit-for-review, approve-many-posts, reject-post

  • Plans6 tools

    Have Bolta plan a routine or a campaign the way its own chat does, change it, then save it on the user's yes.

    plan, plan-routine, plan-campaign, recommend-routines, revise-plan, confirm-plan

  • Routines10 tools

    Work that repeats and runs in Bolta even with the app closed.

    list-routine-templates, list-routines, get-routine, create-routine, update-routine, activate-routine, pause-routine, archive-routine, run-routine-now, list-routine-runs

  • Campaigns6 tools

    One to four weeks of posts about one thing: a launch, an event, a season.

    list-content-campaigns, get-content-campaign, create-content-campaign, update-content-campaign, analyze-content-campaign-source, set-content-campaign-status

  • Team versions4 tools

    One idea written as one post per person on the team, each in their own voice.

    plan-team-posts, update-team-post-plan, generate-team-post-drafts, get-team-post-plan

  • Voice & business8 tools

    The brand's voice and business facts, and writing in that voice.

    get-voice-context, get-voice-profile, create-voice-profile, update-voice-profile, list-business-dna, extract-business-dna, update-business-dna, voice-generate

  • Suggestions2 tools

    What Bolta suggests changing, for a routine or the whole brand, from what people approved, edited and rejected.

    list-suggestions, decide-suggestion

  • Replies10 tools

    Find conversations worth joining, draft replies in the brand voice, and send them once the user says yes.

    search-engagement-opportunities, list-engagements, get-social-content, draft-engagement-reply, draft-inbound-reply, publish-engagement-reply, reply-to-social-content, react-to-social-content, send-outreach-reply, update-outreach-reply

  • Results2 tools

    How posts and accounts are performing.

    list-account-insights, get-account-analytics

Try it

Seven things to ask Grok Build

Sample replies show the shape of what happens. They are illustrative, not real output.

You in Grok Build

Read the v2.0 section of CHANGELOG.md and write a LinkedIn draft for the Acme brand. Leave it unscheduled.

Bolta

Done. I read that section, loaded your voice and the LinkedIn rules, and saved a draft. The full text is above and nothing is queued. Reply yes with a time to queue it, or say what to change.

Draft saved. Waits for your yes.

get-voice-context, get-posting-rules, save-post

You in Grok Build

Which drafts in Bolta are still unreviewed? Only list them.

Bolta

Four items are waiting: two routine drafts, one reply suggestion and one post a teammate sent for review. All are untouched. Name the ones you want to look at and I will print the text before anything is approved.

Read only. Nothing approved.

list-inbox-items

You in Grok Build

I want a routine that drafts a release post each Friday. Show me the plan before saving anything.

Bolta

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.

plan, confirm-plan, create-routine

You in Grok Build

Which of my recent posts got the most replies, and what does that suggest for the next one?

Bolta

I read the analytics for your connected accounts. Here is what stands out. If you want, I can draft a couple of posts along those lines and save them for you to review.

Read only. Offers a draft.

list-accounts, get-account-analytics

You in Grok Build

Did my Friday release routine run this week, and is anything from it unreviewed?

Bolta

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.

list-routine-runs, list-inbox-items

You in Grok Build

Shorten that LinkedIn draft to three sentences. It stays a draft.

Bolta

The shorter text is above in full, saved over the same draft. It has no time set. Say yes and a time to queue it.

Draft updated. Waits for your yes.

get-posting-rules, save-post

You in Grok Build

Reject the second draft. My reason: it reads like a press release.

Bolta

Rejected, with your reason attached. A reason like that can help Bolta learn your voice. Want a plainer attempt to compare?

Rejected with your reason.

reject-post

Bolta publishes to

  • LinkedIn
  • X
  • Instagram
  • Facebook
  • Threads
  • Bluesky

Only accounts you have connected in Bolta can be posted to.

When the terminal is closed

What runs without Grok Build open

Grok Build only works while a session is running. Anything that should keep going belongs in Bolta.

  • A Bolta routine lives on Bolta's servers, so a Friday release draft is still produced with your laptop shut.
  • Drafts from a routine land in your review list and stay there until a person says yes.
  • xAI documents grok -p for scripts, and its overview gives an XAI_API_KEY variable for signing Grok itself in on CI. A cron run against Bolta is untested, and Bolta's own browser sign-in may not be possible unattended.
  • Approving or scheduling from Grok still needs you in the session, replying yes to the exact text.

Not confirmed: a full unattended run through Grok Build has not been tested at Bolta.

Who this is for

Developers and founders who ship and announce from the terminal

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.

  • Good for: launch posts, build-in-public updates, release announcements
  • Needs: a Bolta account with at least one brand, and a browser for the one-time sign-in
  • Does not need: a Bolta key, unless you run it from a script
Release notes to posts

From CHANGELOG.md to a draft in one prompt

Because Grok Build can read files in your project, you can point it at the source instead of pasting text.

  1. 01

    Name the file

    Say which file and which entry: Use the top entry in CHANGELOG.md. Grok reads it from your folder.

  2. 02

    Say where it goes

    Name the network and, if you have several brands, the brand. For example: a LinkedIn post and an X version, for the Acme brand.

  3. 03

    Ask for drafts only

    End with: Save them as drafts. Do not schedule them. Bolta then shows you the exact text and waits.

  4. 04

    Approve, change or reject

    Reply yes with a time to queue one, or tell Grok what to change. A rejection with your reason also helps Bolta learn your voice.

Scripts and cron

Running it without sitting at the terminal

xAI documents a headless mode, grok -p, that runs a prompt from a script. In principle you can run a drafting prompt on a schedule, for example Monday morning from cron.

We have not tested that with Bolta. A scripted run may not be able to open a browser for sign-in, so it would need either a sign-in saved by an earlier interactive session or a Bolta key (bolta_sk_) passed with --header "Authorization: Bearer ${BOLTA_API_KEY}" when you add the server. xAI documents the --header option, but we have not checked either route with Bolta.

Even then Bolta's rule holds. A script can leave drafts for you, but it cannot approve, schedule or publish a post that nobody has approved. For work that must repeat reliably, a Bolta routine is the safer tool, because it runs on Bolta's side even when your computer is off.

Plugins

The plugin route and avoiding a double install

xAI says Grok Build reads Claude Code marketplaces, plugins, skills, MCP servers and CLAUDE.md files with no extra setup. The Bolta plugin lives in the boltaai/bolta-skills marketplace, and inside Grok the /plugins window has a Marketplace tab.

Grok's docs list skill folders at ./.grok/skills, ~/.grok/skills and ~/.agents/skills. They do not name a Claude folder, so after any install restart grok and type /skills to check what loaded.

If the plugin also brings a Bolta connection, /mcps can show Bolta twice. Run grok mcp remove bolta to remove the one you added by hand.

Build in public

Keeping a build-in-public habit from the terminal

People who plan to post about their work often stall because the writing happens somewhere other than the work. Here the raw material is already open: a commit list, a TODO file, a half-written release note.

A workable rhythm is to end a work session by asking Grok for one draft about what you actually did, saved to your review list. You read it later, in the dashboard or back in the terminal, and say yes to the ones you like.

Keep each ask small. One post from one source gives a clearer result than a request to cover the whole month.

  • Ask from a real source: a file, a diff summary or notes you pasted
  • Name the network and the brand in the same message
  • End with: save as a draft, do not schedule
Health check

Three quick checks that Bolta is wired up

grok mcp doctor bolta is a configuration and connection check. It does not prove a full post flow works, so the read-only prompt is the better test.

  1. 01

    grok mcp list

    Run it in the terminal. A server named bolta should appear. If not, run the add command again.

  2. 02

    /mcps inside Grok

    Open the MCP tab and confirm Bolta shows once and is signed in. Press i on it to sign in again if needed.

  3. 03

    A read-only prompt

    Ask: List my Bolta brands and the accounts connected to each one. Do not change anything. A list back means the connection works end to end for reads.

Brands and roles

One sign-in, several brands, and what your role allows

At sign-in you tick which brands Grok may reach. One connection is one organization, so a new brand added to Bolta later needs a fresh sign-in from /mcps before Grok can see it.

Grok acts as you, so it cannot do more than your Bolta role allows. A teammate with a reviewer role who connects Grok gets reviewer limits, not owner limits. If a call comes back refused, that is the rule working, not a Grok fault.

Status

What is tested and what is not

Grok Build is new and its commands may change. If a command here differs on your machine, run grok mcp --help or check xAI's Grok Build docs.

What is tested and what is not
PartStatus
grok mcp add for a remote server, browser sign-inDocumented by xAI
The Bolta address and approval rulesBolta's own, same for every AI app
A full draft, review and schedule run in Grok BuildNot tested yet
Bolta plugin loading inside Grok BuildNot confirmed
Which Grok plan or account you needUnclear, xAI pages differ
Safety

What Grok Build cannot do without you

Grok Build connects as: One grok mcp add command (hosted MCP server).

  • Drafts are free, finals need your yes

    Grok Build can write, edit and save drafts at any time. Approving, scheduling, publishing, sending a reply, activating a routine or campaign and deleting each wait for your yes, shown against the exact text.

  • One connection, one organization

    When you connect Grok Build you tick the brands it may reach. It reaches only those, and when that is more than one brand, every call names the brand it is for.

  • Your role is the ceiling

    Each call Grok Build makes is checked like a normal request from you. Owners and admins can act on any post, creators on Bolta's drafts and on posts they are a named reviewer on, and viewers never approve or publish.

Terms

The words behind Grok Build and Bolta

For Grok Build: One grok mcp add command (hosted MCP server), signing in with Browser sign-in (OAuth), or a Bolta key for scripts.

MCP
The Model Context Protocol, an open standard that lets an AI app call tools in another product. Bolta's hosted server is at https://mcp.bolta.ai/mcp, and Grok Build reaches Bolta through a connection like it.
Skill
A folder of instructions an AI app reads so it knows how to use Bolta well. It does not connect by itself: install it with npx skills add boltaai/bolta-skills --skill bolta next to the connection.
Plugin
A bundle that brings the connection and the skill in one install, where the app supports plugins. Claude Code has one, added with its plugin marketplace commands.
API key
A bolta_sk_ key you create in Settings, sent as a Bearer header. It carries the permissions you choose, which suits apps you configure by hand or anything that runs unattended.
Read the MCP docs

Setup for Grok Build is only partly confirmed. See what is and is not confirmed. Last checked 2026-11-21.

Same name, different thing

Grok Build is not the Grok chatbot or Grok Bot

This page covers Grok Build, xAI's terminal agent, where MCP servers are added with a grok mcp command. The Grok app, grok.com and Grok Bot are separate. We have not documented Bolta in the Grok app or on grok.com.

FAQ

Frequently asked questions

Short answers about using Grok Build with Bolta.

Is Grok Build the same as Grok or Grok Bot?
No. Grok Build is xAI's terminal agent. The Grok chatbot and Grok Bot are different products. This page covers only Grok Build.
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.
Can Grok Build publish without my approval?
No. Bolta will not let an AI app publish a post that nobody has approved. It refuses the call or routes the post to review until someone with the right role says yes, and Grok should print the exact words first.
Is this tested end to end?
No. The connect command follows xAI's documentation, but no one at Bolta has taken a post through draft, review and schedule inside Grok Build. If you want the most tested route today, use Claude Code.
How do I add a second brand after signing in?
A connection reaches only the brands you ticked at sign-in. Inside Grok type /mcps, select Bolta, press i and sign in again, then tick the new brand. If the brand screen does not show, remove and re-add the connection.
Why does Bolta show up twice in /mcps?
This can happen if you added it by hand and a plugin or Claude Code config added it too, since xAI says Grok reads Claude Code MCP servers. Run grok mcp remove bolta to drop your manual one.
Can I run Grok Build on a schedule with grok -p?
xAI documents grok -p for running a prompt from a script, so a scheduled drafting run looks possible. We have not tested it with Bolta, and approval still gates anything that publishes. For reliable repeats, use a Bolta routine.
Does it work in the Grok app or on grok.com?
We have not documented that. This page is for Grok Build, where MCP servers are added with a command.
What does grok mcp doctor check?
Run grok mcp doctor bolta and it checks the saved configuration and the connection for that server. It is a quick health test. It does not prove a full post flow works.
Which Grok plan do I need?
We could not confirm it. xAI's overview says you need an xAI account to sign in, or an API key, and we saw other mentions of a paid plan that we could not verify. Check xAI's current docs before paying for anything.
Where does Grok Build save the Bolta connection?
By default in your user config, so Bolta works from any folder. Adding it with --scope project saves it in .grok/config.toml in the current folder instead, and then it only works there. Sign-in tokens are kept separately by Grok.
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.
Troubleshooting

If something does not work

Quick fixes for the common snags.

Grok says it has no Bolta tools, or bolta is missing from grok mcp list
Run the grok mcp add command again and restart grok. If you added it with --scope project, it only works in that folder. Add it again without that flag, then run grok mcp doctor bolta.
The browser sign-in never opens
Inside Grok type /mcps, select Bolta and press i to start sign-in again. Allow pop-ups, and finish in the browser where you are already logged in to Bolta.
Sign-in loops, or Bolta says invalid or expired
The saved sign-in is out of date. Sign in again from /mcps. If that does not clear it, run grok mcp remove bolta, add it again and sign in fresh. Asking again will not help.
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.
A call fails with 403 or Approval required
That is Bolta doing its job. An AI app cannot schedule or publish a post nobody has approved, and it cannot do more than your Bolta role allows. Ask for a draft or send it for review, then say yes to the exact text.

Ready to schedule social media posts with Grok Build?

Connect Grok Build and ask for your first draft. Nothing goes out until you say yes.