# Turbine client configuration

Use the section for the client hosting the conversation. These examples use production. Substitute the explicit endpoint from the user's setup prompt for another deployment. Check for an existing matching server first, preserve other configuration, then return to [verification and account setup](setup.md#3-verify-the-connection).

## Codex CLI, desktop and IDE

On the machine running the user's Codex client:

```sh
codex mcp list
codex mcp add turbine --url https://api.turbine.so/mcp
codex mcp login turbine
```

Run the add command only if Turbine is absent. Keep the login process alive while the user follows its generated URL. The native commands manage the user's MCP configuration; do not dump credential files into the conversation. Refresh tools or request a new session if necessary, then make an authenticated read in that client.

Manual configuration in `~/.codex/config.toml`, preserving the rest of the file:

```toml
[mcp_servers.turbine]
url = "https://api.turbine.so/mcp"
```

Then run `codex mcp login turbine`. Desktop settings also offer MCP servers → Add server → Streamable HTTP, followed by authentication. Local config does not install a connector into a hosted web conversation.

[Official Codex instructions](https://developers.openai.com/codex/mcp)

## Claude Code

On the machine running Claude Code:

```sh
claude mcp get turbine
claude mcp add --transport http --scope user turbine https://api.turbine.so/mcp
```

Add only if absent. Authenticate through `/mcp` in the Claude Code session, choosing Turbine. If the agent cannot operate that client control, ask the user to run `/mcp` and sign in, then resume verification. The user scope makes the connection available across projects without editing a shared repository.

Claude Code can load tool schemas on demand. When a tool search is available, search it for Turbine and for the exact tool names you need before concluding any are missing. If Turbine is connected but still lacks them, `/mcp` → turbine → Reconnect refreshes a connected server's tools; if you cannot operate it, ask the user for that one action. Then search again and make an authenticated read in the same session. A reconnect or restart is not guaranteed to change the catalog. That reconnect is the one refresh attempt, whatever its result; the tools are available only when this session's search finds them. If they are still missing, go to [what to do after the refresh](setup.md#after-one-refresh) rather than refreshing again.

[Official Claude Code instructions](https://code.claude.com/docs/en/mcp) · [Server status](https://code.claude.com/docs/en/mcp#server-status-detail) · [Tool updates](https://code.claude.com/docs/en/mcp#dynamic-tool-updates)

## Cursor

Merge this entry into `~/.cursor/mcp.json`, preserving existing entries. Use `.cursor/mcp.json` only when the user requested project scope.

```json
{
  "mcpServers": {
    "turbine": {
      "url": "https://api.turbine.so/mcp"
    }
  }
}
```

Use Cursor's MCP settings to authenticate Turbine through its OAuth flow. Reload the connection if necessary and verify a read in Cursor.

[Official Cursor instructions](https://cursor.com/docs/mcp)

## Amp

Prefer a personal remote definition when supported by the installed version, so it is available across Amp clients:

```sh
amp mcp remote --personal list
amp mcp remote --personal add Turbine https://api.turbine.so/mcp --auth oauth
amp mcp remote --personal login Turbine
amp mcp remote --personal check Turbine
amp mcp remote --personal tools Turbine --refresh
```

Add only if absent, complete the generated sign-in handoff, and discover Turbine tools in the current conversation. For a local-only Amp installation, inspect `amp mcp --help` and use its supported `amp mcp add` flow. Do not silently replace a personal connection with a shared project or workspace definition.

[Official Amp instructions](https://ampcode.com/docs/customize/mcp)

## Claude web or desktop

Use the client's connector controls if your tools can operate them. Otherwise, give this single handoff with the name and URL already supplied:

In Settings → Connectors, add a custom connector named **Turbine**, with URL `https://api.turbine.so/mcp`. Connect it and sign in with your Turbine account. Return to this conversation so the agent can verify it.

Do not write Claude Code configuration or a desktop stdio-server config to set up a hosted remote connector.

[Official Claude connector instructions](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)

## Hosted ChatGPT and other clients

Inspect the current client's connector or plugin management capabilities and official instructions. Use its remote MCP installation control where available. Supply name **Turbine**, endpoint `https://api.turbine.so/mcp`, transport **Streamable HTTP**, authentication **OAuth**. Turbine does not require a manually supplied API key or OAuth client secret.

A hosted client may require the user to add or enable a connector. Its plan or workspace policy may also restrict custom servers. If installation is unavailable to this agent, identify the exact control the user must use and resume after they return. Editing files in a hosted code sandbox does not configure the surrounding chat application.

[Official ChatGPT MCP instructions](https://learn.chatgpt.com/docs/extend/mcp?surface=web)

## Terminal status line

To show what is on now and next in a terminal status line (Claude Code, tmux or any command-backed status bar), follow [the status line guide](statusline.md) once the client is connected.