Integrations
HiveBase with ChatGPT workspace agents
How HiveBase and ChatGPT workspace agents compose — one company ledger next to OpenAI's teammates, not instead of them.
HiveBase with ChatGPT workspace agents is a composition, not a replacement. ChatGPT agents stay the teammates you already run in that workspace. HiveBase is the source-backed company context and the receipted work ledger those agents can use through MCP.
HiveBase Squads are staff on one governed company brain. ChatGPT workspace agents are workers in the keep-your-surface lane. The two are not competing rosters. Sell the density of agents across surfaces, never a single-vendor company.
Labs govern what their teammates can see. HiveBase governs what a teammate does through the connector to the company record. Native ChatGPT actions that never call HiveBase are briefed, not governed.
What each side does
| Surface | Job |
|---|---|
| ChatGPT workspace agents | Teammates inside ChatGPT. Citation workflows use the ChatGPT MCP aliases. |
| HiveBase | One company Brain and a shared, receipted task ledger every connected client reads. |
ChatGPT citation-oriented connections use
https://mcp.hivebase.ai/chatgpt/mcp, which exposes only search and fetch
aliases backed by the same retrieval contract as context.search. Other MCP
hosts use the canonical catalog at https://mcp.hivebase.ai.
Mechanics
Add the connector
In ChatGPT settings, add the HiveBase MCP server URL and complete OAuth.
Copy the URL from AI clients in HiveBase settings, or use
https://mcp.hivebase.ai (canonical) /
https://mcp.hivebase.ai/chatgpt/mcp (citation aliases).
Brief before acting
Have the agent start with context.brief or search/fetch so it is
working from cited company context, not a pasted recap.
Leave the session on the ledger
When writeback is enabled, record a durable fact or decision
(context.remember, decision.record) with a stable idempotency key and
keep the receipt. The next agent — in ChatGPT or elsewhere — can retrieve
it.
Chrome forwarding remains a separate, manual capture path. Installing MCP does not create that route.
When not to use this composition
- You only need ChatGPT's own memory for personal recall. Do not stand up HiveBase for a private thread.
- You need HiveBase to govern ChatGPT-native tools, GPTs, or workspace actions that never call the connector. We brief those surfaces; we do not authorize them.
- You need HiveBase to replace ChatGPT agents with Squads. Squads are not a drop-in teammate roster; they are staff on the Brain, with act off until you turn a category on.
- You need a connection without OAuth. Copying a URL is not a connection. A row appears in AI clients only after an OAuth grant.