Bogi developer resources

Connect an agent to a Bogi workspace through the hosted MCP server. Discover the protocol, authenticate with scoped OAuth access, and request only the capabilities your workflow needs.

API and protocol references

Bogi MCP setup

Connect Claude Code, Codex, Cursor, or another compatible MCP client.

https://usebogi.com/mcp

Bogi OpenAPI 3.1

Machine-readable transport, discovery, and OAuth security contract.

https://usebogi.com/openapi.json

OAuth server metadata

Discover authorization, token, registration, PKCE, and supported scopes.

https://usebogi.com/.well-known/oauth-authorization-server

Protected resource metadata

Discover the authorization server and scopes supported by the Bogi resource.

https://usebogi.com/.well-known/oauth-protected-resource

Scoped OAuth permissions

Bogi uses the OAuth 2.0 authorization code flow with S256 PKCE and dynamic client registration. Clients declare scopes with the standard OAuth scope parameter. The consent screen lets the user choose a workspace and approve a subset of the requested access. Bogi checks the required scope again when each MCP tool runs.

workspace:read: Read files and context
workspace:write: Write files, create assets, and persist changes
workspace:execute: Run shell commands and code
apps:preview: Start and inspect app previews
threads:read: Read chat threads and transcripts

MCP transport

Send Streamable HTTP MCP requests to https://usebogi.com/api/v1/mcp. Initialize the session and discover tools through MCP; tool input schemas are returned by the protocol and may evolve independently of this documentation.