# Turbine

> Turbine brings your commitments, projects and schedule into the agent you already use. Start here to install its remote MCP server and onboard the user.

When the user asks you to set up Turbine, carry out the linked setup guide. Learn what you can before asking: your client, the relevant context this session can already reach, and any existing Turbine connection and choices. Reuse an existing connection or install it, handle the sign-in handoff, and prove the connection with a real authenticated tool call. Continue through account setup using the capabilities the server actually exposes. Ask the user only for sign-in, consent, setup decisions that context does not settle, or steps your client cannot perform.

Production MCP endpoint: https://api.turbine.so/mcp
Transport: Streamable HTTP. Authentication: OAuth through the user's Turbine account. No API key or client secret to paste. Access is invite-gated.

## Setup

- [Install and onboard](https://app.turbine.so/agents/setup.md): Start here. Installation, sign-in, verification and account setup, including how to resume after a client restart.
- [Client configuration](https://app.turbine.so/agents/clients.md): Commands and manual fallback for Codex, Claude Code, Cursor, Amp and hosted clients. Read only the section for the current client.
- [Terminal status line](https://app.turbine.so/agents/statusline.md): Read only when the user asks to see Turbine in a terminal status line. A read-only token registered by its hash.

## Working on tasks

- [Work on tasks](https://app.turbine.so/agents/work.md): Read only when the user asks you to work on or resume tasks Turbine holds. How to resume from exact tasks, report progress other agents can pick up, and correct it safely.

If this index was fetched from a different Turbine deployment, resolve these guide paths against that same origin. Use the MCP endpoint supplied by the user’s setup prompt when present.