Developers
Authentication
OAuth 2.1 for agent hosts and server-side callers, with scopes granted at sign-in.
OAuth access is checked for scope, role, membership, visibility, and effect.
OAuth
Modern hosts should use a Client ID Metadata Document. Dynamic Client
Registration remains available for legacy clients. Authorization requires PKCE
S256 and binds tokens to https://mcp.hivebase.ai.
The protected-resource metadata is:
https://mcp.hivebase.ai/.well-known/oauth-protected-resourceAuthorization-server metadata and browser flows live on app.hivebase.ai.
Refresh tokens rotate, revoked token families fail, redirect URIs match exactly,
and authorization responses include the RFC 9207 issuer.
Consent capabilities
| Capability | Scopes | Default |
|---|---|---|
| Catch me up | context:read, decision:read | On |
| Remember what we decide | context:write, decision:write | Explicit toggle |
Finish bounded work appears only for invited workspaces with a certified action pack.
Server-side callers
Server-side callers sign in once through the same OAuth flow, with a person approving it, and send the access token the same way:
Authorization: Bearer <access token>Scopes
If a request lacks a scope, the WWW-Authenticate challenge identifies the
exact required scope.