v0 custom MCP: connect Sume with a Bearer token or OAuth
In v0, open the + menu, choose MCPs, add a custom MCP and pick Bearer Token or OAuth for auth. Which to use for Sume's hosted server, and what each grants.
In v0, open the "+" menu in the prompt form, choose MCPs, add a custom MCP, enter https://mcp.sume.com/mcp, and pick an auth type. v0's docs list four: No Auth, Custom Headers, Bearer Token and OAuth. For Sume, choose OAuth when a person is at the keyboard, because the grant starts read-only; choose Bearer Token with an API key for a fixed, unattended setup.
v0's steps come from its MCP docs; Sume's from the MCP quickstart and OAuth and API keys, all read on 2026-10-06. Sume has no official v0 integration.
Which auth type should I pick?
The table below lists each item as documented.
| v0 auth type | Works with Sume | What the session gets |
|---|---|---|
| OAuth | Yes, preferred for interactive clients | mcp:read always; mcp:write only if you grant it |
| Bearer Token | Yes, with an API key | The full tool set, including paid tools |
| Custom Headers | Yes, x-api-key or Authorization | Same as an API key |
| No Auth | No | Sume requires credentials |
What happens during OAuth?
Sume's consent page lives on the MCP host: /oauth/authorize redirects to /oauth/consent on mcp.sume.com. The scopes are mcp:read (required) and mcp:write (opt-in); there is no paid scope. A write grant always includes read. The protected-resource metadata is published at /.well-known/oauth-protected-resource/mcp, which is how a client finds the authorization server.
Why not an API key by default?
An API key sees paid tools at once and an OAuth token is not a key, so do not mint a key to stand in for a failed OAuth flow. If v0 shows an unauthorized error, retry the OAuth connection; Sume's docs say OAuth is the path for interactive clients, and keys are for headless ones.
Sources
Related posts
More in Integrations
- Viber bot video message: 26 MB, 180 s, .mp4 URL, a Sume clip
Viber's bot API wants an MP4 URL ending in .mp4, 26 MB max, 180 s max, and a JPEG thumbnail. A 60 second Sume avatar clip fits. The checks to run first.
- VoltAgent MCPConfiguration: connect to the Sume hosted MCP server
VoltAgent's MCPConfiguration takes type http, a url and requestInit headers. Reach Sume at mcp.sume.com/mcp with an API key, then pass tools to an agent.
- WhatsApp Business MCP is dev-only: keep Sume generation server-side
WhatsApp Business tools MCP was announced as dev and test only. Generate with Sume on your server and gate the MCP transport by environment. Tested code.
- Zed tool permissions: confirm by default, rules per Sume tool
Zed confirms every tool action by default and can allow or deny one MCP tool by name. Keep Sume's paid generators on confirm while reads run freely.
Written by Sume