---
title: "Grok Build integration with Bolta"
description: "Connect Grok Build to Bolta with one grok mcp add command. Draft LinkedIn and X posts from your changelog, review them, and approve before anything publishes. Setup, checks and honest limits."
canonical_url: "https://bolta.ai/integrations/grok-build"
markdown_url: "https://bolta.ai/integrations/grok-build.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# Grok Build integration with Bolta

Source: https://bolta.ai/integrations/grok-build
Last updated: 2026-11-21

Connect Grok Build to Bolta with one grok mcp add command. Draft LinkedIn and X posts from your changelog, review them, and approve before anything publishes. Setup, checks and honest limits.

## Summary

Draft posts about your release without leaving Grok Build

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- 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

## Limitations and boundaries

- 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.
- Integration availability depends on current APIs, authentication, scopes, and account permissions.
- Generated content can be incorrect and should be reviewed before publication.
- Availability depends on the current Bolta plan, connected network, account permissions, and integration coverage.
- Current prices and plan limits must be verified on the Bolta pricing page.

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

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

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

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

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

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

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

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

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

## 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

## 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. Name the file: Say which file and which entry: Use the top entry in CHANGELOG.md. Grok reads it from your folder. 2. 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. Ask for drafts only: End with: Save them as drafts. Do not schedule them. Bolta then shows you the exact text and waits. 4. 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.

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

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

## 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

## 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. grok mcp list: Run it in the terminal. A server named bolta should appear. If not, run the add command again. 2. /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. 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.

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

## 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. Part: grok mcp add for a remote server, browser sign-in; Status: Documented by xAI | Part: The Bolta address and approval rules; Status: Bolta's own, same for every AI app | Part: A full draft, review and schedule run in Grok Build; Status: Not tested yet | Part: Bolta plugin loading inside Grok Build; Status: Not confirmed | Part: Which Grok plan or account you need; Status: Unclear, xAI pages differ

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

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

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

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Related page: /integrations/claude-code](https://bolta.ai/integrations/claude-code)
- [Related page: /integrations/grok-bot](https://bolta.ai/integrations/grok-bot)
- [Related page: /integrations/codex](https://bolta.ai/integrations/codex)
- [Related page: /integrations/cursor](https://bolta.ai/integrations/cursor)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

- [Grok Build official website](https://x.ai/cli)
