> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stardrift.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect any MCP client

> What a Model Context Protocol client needs to talk to Stardrift: Streamable HTTP, OAuth with dynamic client registration, and the scopes to request.

Any client that speaks MCP over Streamable HTTP and can complete an OAuth sign-in works with Stardrift.

|                      |                                                                                                      |
| -------------------- | ---------------------------------------------------------------------------------------------------- |
| Endpoint             | `https://stardrift.ai/mcp`                                                                           |
| Transport            | Streamable HTTP                                                                                      |
| Authentication       | OAuth 2.1 with PKCE; dynamic client registration and client ID metadata documents are both supported |
| Resource metadata    | `https://stardrift.ai/.well-known/oauth-protected-resource`                                          |
| Authorization server | `https://stardrift.ai/api/oauth`                                                                     |
| Scopes               | `guides:read guides:write bookings:read saved:read saved:write`                                      |

An unauthenticated request returns `401` with a `WWW-Authenticate` header that names the resource metadata URL and the scopes to request. Clients that follow the MCP authorization specification discover everything from there and open the browser for sign-in. Tokens go in the `Authorization: Bearer` header.

Clients that cannot run an OAuth flow are not supported yet.

See [what you are granting](/) for what each scope allows and [Tools](/tools) for the catalog.