Connect voicebin.ca to your MCP client
Use your audio clips from an AI assistant.
MCP for AI agents
voicebin.ca runs a Model Context Protocol server at https://voicebin.ca/mcp, so Claude Desktop, Cursor, the MCP Inspector, and other agents can manage your audio clips directly.
Option A — OAuth (interactive clients)
Install in VS Code MCP Registry record Other Bins MCP guides
Add https://voicebin.ca/mcp as a remote MCP server in your client, then sign in with your Pastebin.ca account.
In Claude, open Customize → Connectors → Add → Custom → Web, enter the URL and use Claude’s published identity when prompted.
Try it List my three most recent audio clips and show their titles.
Option B — API-key bearer (automation)
For headless/server-side use, send a minted key directly:
{
"mcpServers": {
"voicebin": {
"url": "https://voicebin.ca/mcp",
"headers": { "Authorization": "Bearer pbca_live_…" }
}
}
}Tools
| Tool | Scope | Purpose |
|---|---|---|
whoami | — | Echo account id, scopes, audience, and token kind. |
get_audio | voice:read | JSON metadata for an audio clip (visibility-aware). |
list_my_audio | voice:read | List the caller's clips; cursor-paginated. |
upload_audio | voice:create | Upload from base64 bytes (capped — see below). |
delete_audio | voice:delete | Delete one of the caller's clips. |
OAuth & DPoP
pastebin.ca is the OAuth authorization server; voicebin.ca is a protected resource and never mints tokens.
- OAuth tokens are audience-bound to
https://voicebin.ca/mcp(RFC 8707) and honored only on the MCP route. - If a key is DPoP-bound (RFC 9449), every MCP request must carry a matching ES256 proof; replays are rejected. Plain bearer keys work without DPoP.
- Revoke a key or connected app anytime from your pastebin.ca account.
Discovery
Machine-readable metadata for clients and agents:
Protected-resource metadata ↗ Authorization-server metadata ↗ Agent discovery (agent.json) ↗ OpenAPI 3.1 document ↗ MCP endpoint (POST) ↗