Getting connected

Kubeez MCP uses standard OAuth so your MCP client can act on your behalf with your consent.

#How authorization works

1. Your MCP client contacts the Kubeez server and is told to open a browser so you can sign in.
2. You sign in at Kubeez and see which capabilities the client is requesting (e.g. “Generate images and videos”, “Check your credit balance”).
3. You approve or deny. If you approve, the client receives a token.
4. The client sends that token with every request. Generations use your Kubeez account and credits.

You can revoke access at any time from your Kubeez account settings (e.g. under MCP / connected apps).

#Capabilities (scopes)

When you authorize, you may see one or more of these:

• Generate media - Start image and video generations.
• Generate music - Start music generations.
• Generate ads - Start ad-copy generations.
• Read balance - Check your credit balance.
• Read generations - List and inspect your generation history.

The client will only be able to use the capabilities you approve. If a tool needs a capability you didn’t grant, the request will be refused.

#Tokens

• The client receives an access token and uses it for API calls.
• Tokens can be refreshed so you don’t have to log in again every time they expire.
• If the token is missing or invalid, the server will respond with an error and the client should prompt you to authorize again.

No passwords or long-lived secrets are shared with the client; only short-lived tokens that you can revoke.

Next: Media tools, Music tools, or Ads tools.