The connection URL for Drive's Segments Model Context Protocol server.

Connecting a client: this endpoint is the MCP server itself, not a URL-minting step — point your MCP client directly at it, configuring it to send an OAuth2 access token (see Authentication) as a bearer token and X-Client-Id as a static header on every request, the same as any other Drive API call. Many MCP clients accept a config file for this, for example:

{
  "mcpServers": {
    "drive-segments": {
      "url": "https://api-sandbox.thisisbud.com/drive-mcp/v1/segments",
      "headers": {
        "Authorization": "Bearer <access_token>",
        "X-Client-Id": "<client_id>"
      }
    }
  }
}