Integrations
HiveBase with Grok Bot
How HiveBase and Grok Bot compose — company context and a receipted work ledger next to xAI's bot, not instead of it.
HiveBase with Grok Bot is a composition, not a replacement. Grok Bot is the runner you already chose. HiveBase is the company context and the receipted work ledger that bot can read and write through remote MCP.
Labs govern what their bot can see inside their product. HiveBase governs what the bot does through the connector to the company record, and it remembers those writes. Native Grok actions that never touch the connector are briefed, not governed. That pipe rule is the honest boundary.
What each side does
| Surface | Job |
|---|---|
| Grok Bot | Conversational runner. Polls HiveBase; HiveBase cannot push into a bot session. |
| HiveBase | Source-backed company context, shared Tasks, decisions, and receipts across every client. |
They share one board. Grok is one MCP client, not a separate HiveBase channel.
Mechanics
Connect the bot over remote MCP
In Grok Bot, add https://mcp.hivebase.ai as a custom remote connector and
complete browser OAuth. See the connect guide.
Start from company context
Ask the bot to call context.brief (or read
hivebase://context/company-primer) before it proposes work. That is the
same payload every other connected client receives.
Keep work on the shared ledger
Use task.search / task.get for current work, task.status.set and
task.post to leave progress, task.mailbox.read for steering. Writes take
a stable idempotency key and return a receipt.
HiveBase does not scrape, mirror, or sync Grok chat sessions. The durable objects are company context, decisions, tasks, reports, steering receipts, attention requests, and held effects with their receipts.
When not to use this composition
- You only need personal recall inside Grok. Native memory is enough; do not stand up HiveBase for a private chat log.
- You need HiveBase to interrupt a live Grok session. HiveBase can call a
webhook a bot routine listens on (
subscription.create), but it cannot inject into a chat that is already running. - You need HiveBase to govern Grok-native actions that never call the connector. We do not pretend to govern what we do not touch.