Skip to main content
Octolane MCP supports OAuth 2.0 and API keys. The hosted endpoint is https://mcp.octolane.com/mcp, using Streamable HTTP. MCP access is included on every Octolane plan.

OAuth

Use OAuth for clients that offer an interactive connection flow. Add the server URL, review the requested access, then enter your personal Octolane API key on the Octolane authorization page. Create the key in Settings → API keys first. The client handles the authorization-code flow with PKCE and sends the resulting bearer token. Enter credentials only on Octolane’s authorization page, never in the AI conversation. If authorization expires or the key is revoked, reconnect using an active key. The server publishes its current configuration at: The authorization server advertises these scopes: Use the live metadata for authorization endpoints and supported registration methods. These are advertised scope names, not a documented way to create a read-only API key. Treat a connected key as capable of writes within its member’s access. Scopes do not bypass workspace permissions or plan entitlements.

Personal API keys

Create a key in Settings → API keys. The same personal key works with the REST API and MCP. For clients that accept custom headers, send:
For example, a client supporting the following remote-server configuration can use:
MCP uses the Authorization bearer header. The REST API at api.octolane.com uses x-api-key; the headers are not interchangeable. An MCP request with only X-API-Key returns 401 with “Missing Authorization header”. Configuration formats vary by client. Use the Claude, ChatGPT, or Cursor guide. ChatGPT uses OAuth for this connection.

Permissions and revocation

Requests act with the connected person’s workspace permissions. Personal API keys use their creator’s current access and stop working when disabled or when the creator leaves the workspace. They do not grant unrestricted access to every record or administrative action. Store keys in your client’s credential settings or supported environment-variable configuration. Do not put real keys in shared source files. Revoke exposed or unused keys from API-key settings.

Rate limits

Handle 429 Too Many Requests, following Retry-After when supplied and backing off before retrying. MCP-specific numeric limits are not published in the discovery metadata. Do not assume that REST route quotas apply to every MCP tool. Contact help@octolane.com for workspace-specific limits.

Troubleshooting

Opening the MCP URL in an unauthenticated browser may return 401; that alone does not indicate an outage.