Install one MCP endpoint. Give every AI agent the same company context.
One hosted server for Claude, Cursor, Codex, and ChatGPT. Free context reads. Writes stay confirmable, provenanced, and undoable.
Claude
Cursor
Codex
ChatGPTConnect your host in one step
Point any MCP client at the hosted endpoint. OAuth handles the first connection — no self-hosted server, no version pin.
https://mcp.hivebase.ai/claude mcp add hivebase --transport http https://mcp.hivebase.ai/Backend or CI? Scoped API key + REST / @hivebase/sdk · API keys →
One loop every agent follows
Three moves — load free context, do the work, write back with a trail. Not a different integration per app.
Load free company context
Before any spend, the agent pulls a source-backed brief — the same packet Claude, Cursor, or Codex would get.
- READmcp.hivebase.ai$
Before any spend, the agent pulls a source-backed brief — the same packet Claude, Cursor, or Codex would get.
Always free within scope - RUNmcp.hivebase.ai$
Turn the brief into a task, choose how it runs, and track status — no second orchestration API.
Same tools over MCP or API - WRITEmcp.hivebase.ai$
When knowledge changes, OAuth holds for confirmation. Authorship stays on the record — and undoable.
Not a silent writer
Same loop over MCP for AI apps and the Platform API for services. Action receipts →
What agents wire first
9 audited tools across 3 domains. Pick a job — see the call and the outcome.
Read context before work
Source-backed company context — evidence, decisions, overlapping tasks — before an agent spends credits.
context.briefcontext.searchAcme renewal · SSO dependency · board risk this week
ClaudeCursorCodexChatGPTSame product. Two entry paths.
AI apps use MCP + OAuth. Services and CI use scoped keys.
- MCP · AI apps
- OAuth 2.1 + DCR
- Platform API · services
- Scoped hb_sk_* keys
- MCP · AI apps
- Claude, Cursor, Codex, ChatGPT, MCP hosts
- Platform API · services
- CI, workers, backends
- MCP · AI apps
- Confirmation / hold path
- Platform API · services
- Inline under programmatic trust
- MCP · AI apps
- mcp.hivebase.ai
- Platform API · services
- REST · @hivebase/sdk · webhooks
| MCP · AI apps | Platform API · services | |
|---|---|---|
| Auth | OAuth 2.1 + DCR | Scoped hb_sk_* keys |
| Caller | Claude, Cursor, Codex, ChatGPT, MCP hosts | CI, workers, backends |
| Writes | Confirmation / hold path | Inline under programmatic trust |
| Entry | mcp.hivebase.ai | REST · @hivebase/sdk · webhooks |
Questions
What is the HiveBase MCP server?
One hosted endpoint that gives Claude Code, Cursor, Codex, ChatGPT, and other MCP hosts the same company context, scoped auth, and write confirmation — instead of a disconnected integration per app.
Do I need to host it myself?
No. mcp.hivebase.ai is hosted. OAuth handles first connection for AI apps. API keys in settings cover CI and backends.
Can agents write, or only read?
Both — not symmetrically. Reads are free within scope. Writes are scoped, confirmation-gated for OAuth, and carry provenance so agents can't become silent writers.
MCP vs API keys — when each?
MCP + OAuth for interactive AI apps. Scoped hb_sk_* keys with REST or @hivebase/sdk for CI and non-interactive services.
When is this not needed?
Personal assistant memory is enough for one-person recall. A single-tracker team happy with that product's agent may not need HiveBase. The fit is multi-surface companies running multiple AI apps against one shared company record.
Install MCP first. Use the API where services need it.
OAuth for AI apps. Scoped keys for CI and backends.