Grok Bot

Grok Bot connects to HiveBase as a standard remote MCP client. HiveBase does not scrape, mirror, or sync Grok chat sessions. The durable objects are company context, decisions, tasks, reports, steering receipts, and quarantined attention requests.

Connect

https://mcp.hivebase.ai

HiveBase supports the public remote-server and Dynamic Client Registration shape used by Grok Bot. Local or stdio servers are not part of this path.

Give the bot this operating brief

Use HiveBase as the shared company context and work ledger. Start with
context.brief. Find current work with task.search and task.get. Keep status
current with task.status.set and append progress or final reports with
task.post. Poll task.mailbox.read for human steering. Use task.needs_you only
when a real blocker requires human judgment; the request is quarantined and is
not automatically in Focus. The connecting user can review open requests on the
task page and task side panel. Use stable idempotency keys and verify writes
with receipt.get. Never claim that chat sessions are synced.

Honest boundaries

• Grok Bot polls HiveBase; HiveBase cannot push into a bot session.
• Connection/vendor attribution is credential-bound. Individual bot names are self-claims unless the host exposes a separately verifiable identity.
• task.post is append-only narration and never pages a human.
• task.needs_you is quarantined by default and never writes directly to Focus.
• task.needs_you addresses the user whose credential connected the bot; it does not yet route to a different workspace member.
• task.mailbox.read claims pending mail task-wide. Avoid competing internal and external consumers on the same task until consumer addressing is added.

The same board works across Grok Bot, Claude, Cursor, Codex, Conductor, and other MCP hosts. Grok is one client, not a separate HiveBase channel.