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)

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

ToolScopePurpose
whoami—Echo account id, scopes, audience, and token kind.
get_audiovoice:readJSON metadata for an audio clip (visibility-aware).
list_my_audiovoice:readList the caller's clips; cursor-paginated.
upload_audiovoice:createUpload from base64 bytes (capped — see below).
delete_audiovoice:deleteDelete one of the caller's clips.
MCP upload capMCP accepts up to 8 MiB per audio clip. Binary content is base64-encoded in the JSON-RPC request. REST accepts up to 50 MiB per audio clip.

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: