---
title: "Grok Bot integration with Bolta"
description: "Add Bolta to Grok Bot as a custom connector. Your Bot drafts posts, checks your approval queue and reads analytics, and nothing publishes until you say yes. Honest notes on what is confirmed."
canonical_url: "https://bolta.ai/integrations/grok-bot"
markdown_url: "https://bolta.ai/integrations/grok-bot.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# Grok Bot integration with Bolta

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

Add Bolta to Grok Bot as a custom connector. Your Bot drafts posts, checks your approval queue and reads analytics, and nothing publishes until you say yes. Honest notes on what is confirmed.

## Summary

Let your always-on Grok Bot draft social posts that wait for your yes

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- Have a Monday routine draft the week's posts and leave them in your review queue
- Turn release notes your Bot already read into a LinkedIn and X draft
- Ask your Bot in Slack or on X what is waiting for approval in Bolta, once you have checked Bolta is available there
- Get a weekly recap of how recent posts performed, delivered by your Bot
- Keep each client in its own Bolta brand and tick only the brand a job needs
- Reply to your own comment threads with drafts you approve before they go out

## Limitations and boundaries

- Confirmed in xAI's docs: Grok Bot has an Add a custom connector form in the desktop app that takes a Remote HTTPS server URL, optional HTTP headers and an optional OAuth Client ID.
- Not confirmed: whether Bolta's browser sign-in finishes from that form when the Client ID is left empty. We have not tested it end to end.
- Per xAI's teams page, Grok Bot is included with every paid Cursor plan, through an individual SuperGrok link, or with a seat on a self-serve Grok Business plan. That page does not say whether every plan can add custom connectors. We quote no price.
- Not confirmed: whether an API key sent in the headers field works, and whether the Bolta skill installs in Grok Bot.
- Not confirmed: whether custom connectors can be added from mobile, Slack or X. The docs describe the form for the desktop app only.
- 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.

## Open the Grok Bot desktop app

Make sure you are signed in. xAI documents custom connectors for the desktop app, so start there rather than on mobile.

## Open Connect apps

Find Connect apps in the left sidebar. This is where catalog apps and your own connectors live. Some third-party write-ups call it Marketplace, so the label may change.

## Choose Add a custom connector

Scroll to the bottom of the list and choose Add a custom connector. A form opens asking for a name, a type and a server address.

## Fill in the form

Name it Bolta, set Type to Remote HTTPS and paste the Server URL https://mcp.bolta.ai/mcp. Leave the HTTP headers and the OAuth Client ID empty for the normal sign-in.

## Choose Add plugin

This saves the connector. If the Bolta card then shows Needs auth or Disconnected, choose Authenticate.

## Approve on bolta.ai and tick your brands

Your browser opens a bolta.ai page. Sign in, read the permission screen and tick only the brands this Bot should reach. xAI says to finish within about 10 minutes, or choose Reconnect to start again.

## Confirm it is installed

Back in Grok Bot, check that Bolta shows under Installed. Added only means installed, not signed in, so make sure it is not still on Needs auth. In a chat, type @ and pick Bolta so the Bot knows which connector you mean.

## Run a read-only check

Ask: Which Bolta brands can you reach, and which social accounts does each have? Do not change anything. If it answers, the connection works and nothing was created.

## Optional: save a routine

Ask the Bot to draft posts in Bolta every Monday, and say that it must wait for your approval before anything is scheduled or published. The skill route (npx skills add boltaai/bolta-skills --skill bolta) is untested in Grok Bot.

## Grok Bot vs Grok Build vs the Grok chatbot

Product: Grok Bot; Where it runs: Its own cloud computer; desktop, mobile, Slack, X; How Bolta connects: Connect apps, Add a custom connector, Remote HTTPS | Product: Grok Build; Where it runs: Your terminal; How Bolta connects: grok mcp add command, see the Grok Build page | Product: Grok chatbot; Where it runs: The Grok app and grok.com; How Bolta connects: Not covered by this page; no setup is confirmed

## Routines that draft in Bolta while you are away

xAI describes routines that run on a schedule or on events, even when your laptop is closed. A Bot can have up to 50, at least 5 minutes apart. That makes a weekly content job a natural fit, as long as the job only drafts. Monday content batch: draft the week's posts and save them for review. Release notes to LinkedIn: on a GitHub event you set, draft one post. Weekly recap: read analytics and send you a short summary. Always say in the routine that it must wait for your approval. Bolta enforces this too.

## Two layers of approval, and only one is Bolta's

Grok Bot lets you write short permission rules in plain language under Settings, General, in the Bot group (Custom Rules, each set to Allow automatically or Ask first). Its Auto-review checks each action and shows an approval card when it wants you to decide. That is the first layer and it is xAI's. Bolta is the second. A draft stays a draft until you or a teammate with the right role says yes. If a Bot asks to publish without that, Bolta refuses it or sends it to review. Do not rely on the Bot's rules alone.

## All your Bots share one computer

xAI warns that every Bot you own shares one computer and one security boundary, and any Bot can use any installed connector. Once Bolta is installed, any of your Bots can use it, so you cannot give each Bot its own Bolta access. Tick only the brands you want reachable when you approve on bolta.ai. Use separate Bolta brands for separate clients, and connect only the one this work needs. If your team's connector policy blocks Bolta, the card shows Disabled by team admin.

## Three routines worth setting up first

These are starting ideas, not tested recipes. Each one should draft, then wait. Say that in the routine itself. 1. Monday content batch: Draft three posts for one brand and put them in review. Use plan before saving, and keep the routine off until you have read a sample. 2. Release notes to a draft: When your Bot sees a release in a tool you connected, it can draft one LinkedIn and one X post. xAI lists GitHub among its routine triggers. 3. Friday performance recap: Read the week's analytics for each account and send you a short written summary. This only reads, so no approval is needed.

## The API key route, and why it is second

If the browser sign-in will not finish, you can try the headers field. Create a key in Bolta under Settings, API Keys, then add an Authorization header with the value Bearer followed by the key. We have not confirmed Grok Bot sends it. A key skips the sign-in screen where you tick brands. Create it for the one brand this Bot needs and tick only the permissions that brand needs. Keep it out of chat. xAI says a Bot can ask for secrets through a masked secret card, and the Bot never sees the value.

## What we have and have not checked

Question: Custom connector form in the desktop app; Status: Documented by xAI | Question: Bolta browser sign-in with no Client ID; Status: Not tested | Question: API key in the headers field; Status: Not tested | Question: Bolta skill install in Grok Bot; Status: Not tested | Question: Adding connectors from mobile, Slack or X; Status: Not documented | Question: Plan that includes custom connectors; Status: Not stated by xAI

## Is Grok Bot the same as Grok Build or the Grok app?

No. Grok Bot is an always-on agent on its own cloud computer. Grok Build is xAI's terminal agent, and Bolta has a separate page for it. This page covers Grok Bot only.

## Do I need to copy an API key to connect Bolta to Grok Bot?

Not for the normal route. You add the server address and approve on bolta.ai. An API key in the headers field is a fallback we have not tested in Grok Bot.

## Can Grok Bot publish posts without my approval?

No. Nothing is approved, scheduled or published until a person with the right role says yes. Bolta refuses the request or sends it to review.

## Can a Grok Bot routine draft my posts every week while my computer is off?

xAI says routines run on a schedule even when your laptop is closed. Bolta can hold the drafts for your review. Ask the routine to draft only, and confirm what it will do before you turn it on.

## Which brands can my Bot reach, and can I limit it?

Only the brands you tick on the permission screen when you sign in. Reconnect Bolta to change them. Remember that all your Bots share one computer.

## What plan do I need for Grok Bot and custom connectors?

xAI's teams page lists three routes: every paid Cursor plan, an individual SuperGrok link, or a seat on a self-serve Grok Business plan. It does not say whether every route can add custom connectors, and we do not quote a price. Check xAI for current plans. Bolta plans are on our pricing page.

## Why does Bolta show as Needs auth or Disconnected in Connect apps?

The sign-in has not finished or has expired. Choose Authenticate or Reconnect and complete the bolta.ai step within about 10 minutes.

## Does my team admin policy block custom MCP servers?

It can. xAI says Grok Bot follows your team's connector policy, and a blocked app shows Disabled by team admin. xAI does not say whether members can add their own custom connectors, so ask your admin if saving fails.

## Does the sign-in definitely work from Grok Bot?

We have not confirmed it. xAI documents the form and Bolta is a standard remote MCP server, so it should be addable. Whether the browser sign-in completes without a Client ID is untested.

## Can I add Bolta from my phone or from Slack?

Unconfirmed. The docs describe the custom connector form for the desktop app. Once connected, your Bot may be reachable from other surfaces, but check that before relying on it.

## How do I stop a routine my Bot started?

Ask your Bot to pause it, or open Routines in Bolta and pause it there. Grok Bot routines are managed in Grok Bot, and Bolta routines are managed in Bolta, so check both places.

## Does Grok Bot keep my Bolta sign-in forever?

Not necessarily. If the sign-in expires the card shows Needs auth or Disconnected, and you choose Authenticate or Reconnect. We have not measured how long a session lasts.

## The Bolta card says Needs auth or Disconnected

Open the card and choose Authenticate (on a phone the button is Authorize), or Reconnect if the earlier attempt timed out. The browser step has to finish within about 10 minutes.

## The sign-in window never opens or never finishes

xAI does not document which sign-in a remote server needs, and we have not confirmed Bolta's completes without a Client ID. Try Reconnect once. If it still fails, try the API key header route, which is also unverified.

## I cannot find Add a custom connector

The form is documented for the desktop app only. Update the app and look at the bottom of the Connect apps list. The label has reportedly changed before, so it may differ.

## Saving the connector is blocked or shows Disabled by team admin

A team connector policy can block the server. Ask your admin to enable it in Teams Marketplace. On an Enterprise MCP allowlist, they also add https://mcp.bolta.ai/mcp there, then you restart the app.

## My Bot cannot see a brand I expected

The permission screen only gave the Bot the brands you ticked. Run Reconnect on the Bolta card and tick the brand that was left out.

## Bolta refused to publish a post my Bot tried to send

That is the approval gate working. Open Bolta, read the exact text and approve it yourself, or ask the Bot to save it as a draft.

## Grok Bot is not Grok Build or the Grok chatbot

Grok Bot is an always-on agent with its own cloud computer, reached from desktop, mobile, Slack and X. Grok Build is xAI's terminal agent and uses a one-line command instead of a form. This page is for Grok Bot.

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Related page: /integrations/grok-build](https://bolta.ai/integrations/grok-build)
- [Related page: /integrations/claude-cowork](https://bolta.ai/integrations/claude-cowork)
- [Related page: /integrations/hermes-agent](https://bolta.ai/integrations/hermes-agent)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

- [Grok Bot official website](https://docs.x.ai/grok-bot/overview)
