Model Context Protocol

Download once. Connect where you work.

Baise uses one Streamable HTTP endpoint. The tools returned to an agent are filtered to the products and permissions on its credential.

Canonical endpoint

https://mcp.baiseapps.com/mcp

API keys work for server automation and local clients. OAuth 2.1 discovery supports remote clients that complete an interactive Baise developer login.

Supported profiles

Claude CodeHTTP profile with an environment-backed Authorization header.

CodexTOML profile using bearer_token_env_var.

ChatGPTRemote MCP connection manifest and OAuth discovery.

Antigravitymcp_config.json profile using serverUrl.

Profiles are downloaded only from the authenticated developer console. Baise product apps do not distribute them.

OAuth discovery

Remote clients use the developer website as the OAuth 2.1 issuer. Authorization code exchange requires PKCE S256; access tokens expire after one hour and refresh tokens rotate.

GET/.well-known/oauth-protected-resourceMCP resource metadata

GET/.well-known/oauth-authorization-serverAuthorization server metadata

POST/oauth/registerDynamic client registration

GET/oauth/authorizeAuthenticated consent with PKCE

POST/oauth/tokenCode exchange and refresh rotation

POST/oauth/revokeToken revocation

Product scopes follow baise:product:permission. The mcp:tools scope is read-only across products.

Verify the connection

curl https://mcp.baiseapps.com/mcp \
  -H "Authorization: Bearer $BAISE_API_KEY" \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'