MCP authentication
Today: API key Live
Section titled “Today: API key ”The MCP server accepts the same personal API key as the REST API:
Authorization: Bearer cb_live_...Create the key in Clipbeat Studio, Settings, Developers, API keys. The key’s scopes decide which tools it can call. Setups for each client are in Connect an MCP client.
Soon: one click sign-in with OAuth Available soon
Section titled “Soon: one click sign-in with OAuth ”With OAuth, a user connects an AI client to Clipbeat by signing in and approving the connection, without copying a key. This is how clients that only offer a sign-in screen (for example Claude and ChatGPT connectors) will connect. When it launches, MCP connections move to OAuth and API keys remain the way to use the REST API.
How connecting will work
Section titled “How connecting will work”- The user adds
https://api.clipbeat.app/mcpto their AI client. - The client discovers Clipbeat’s authorization server and opens a Clipbeat sign-in page.
- The user signs in and sees which client is asking, what it may do and how much it may spend per day.
- The user approves. The client receives tokens and the tools appear.
The user sees and controls every connection in Clipbeat Studio (connected apps): the daily credit limit can be changed and the connection revoked at any time.
Planned details for client developers
Section titled “Planned details for client developers”The design follows the MCP authorization specification and OAuth 2.1:
| Item | Plan |
|---|---|
| Protected resource metadata | GET https://api.clipbeat.app/.well-known/oauth-protected-resource/mcp (RFC 9728) |
| Authorization server metadata | GET https://api.clipbeat.app/.well-known/oauth-authorization-server (RFC 8414) |
| Authorization endpoint | https://api.clipbeat.app/oauth/authorize |
| Token endpoint | https://api.clipbeat.app/oauth/token |
| Client registration | Client ID metadata documents, and dynamic client registration at https://api.clipbeat.app/oauth/register (RFC 7591) |
| Revocation | https://api.clipbeat.app/oauth/revoke (RFC 7009) |
| PKCE | Required, S256 only |
| Resource indicator | resource=https://api.clipbeat.app/mcp (RFC 8707); tokens are only valid for the MCP server |
| Scopes | create:video, read:video, read:balance |
| Access token lifetime | 1 hour |
| Refresh tokens | Rotated on every use, valid for 30 days |
| Spending limit | A daily credit limit per connection, set by the user when approving |
A request to /mcp without valid credentials will return 401 with a WWW-Authenticate header that points to the
protected resource metadata, so standard MCP clients can start the flow on their own.
What will not change
Section titled “What will not change”- Prices, rate limits, the content policy and the tools themselves stay the same.
- Payment still comes from the account’s credit balance; card details never go through the client.
- The REST API keeps using API keys.
Questions about the OAuth rollout: [email protected].