Turbine developer docs for MCP and OAuth
Access to the MCP server is invite-gated and requires OAuth through the user's Turbine account. The public website and documentation can be read without signing in.
Quickstart: how to get access
Request beta access through the Turbine waitlist.
If you have access, follow the agent setup guide to connect your MCP client to https://api.turbine.so/mcp and sign in with your Turbine account.
AuthKit advertises authorization code with PKCE S256, client ID metadata documents, and a dynamic client registration endpoint in its issuer metadata. These are advertised capabilities, not evidence that every client flow has been tested.
An unauthenticated request to the MCP endpoint returns HTTP 401 with error invalid_token and error_description "Authentication required". Its WWW-Authenticate Bearer challenge includes resource_metadata="https://api.turbine.so/.well-known/oauth-protected-resource/mcp". Read the OAuth protected-resource metadata to discover the AuthKit issuer. A 401 is expected before sign-in, not proof of account access.
Remote MCP server
The production endpoint is https://api.turbine.so/mcp. It uses the Streamable HTTP transport.
The MCP endpoint requires an OAuth bearer token from the user's Turbine account. It does not provide anonymous access to anyone's tasks, calendar or inbox.
AuthKit handles authorization. Its OAuth authorization-server metadata and OpenID Connect configuration are published at the AuthKit issuer, not mirrored on turbine.so.
Access is currently invite-gated. Request access to join the beta.
Agent documentation
Agent index (llms.txt): the starting point for an agent, with the endpoint, authentication and links to every guide.
Install and onboard: installation, sign-in, verification and account setup.
Client configuration: commands and manual fallbacks for Codex, Claude Code, Cursor, Amp and hosted clients.
Work on tasks: how an agent resumes tasks that Turbine holds and reports progress other agents can pick up.
Machine-readable pages
The OpenAPI 3.1 document describes public document GET operations, OAuth protected-resource metadata, and the MCP authentication boundary. Standard MCP envelopes are described separately from observed responses. It does not enumerate authenticated tools or expose a REST API for user data. An MCP client discovers tools after sign-in.
Discovery links include the MCP server card, AI catalog, and API catalog.
This site publishes its own guide for agents and a sitemap. Every public page, including this one, is also available as Markdown: request the same URL with Accept: text/markdown.
Operator
Turbine is currently operated from Switzerland by its founders. Until a Swiss company name is published here, references to "Turbine", "we", "us", or "our" mean the Turbine founding team operating the service.
Questions about connecting an agent can go through the channels on our Contact page.