Dubber MCP server

dubber-mcp

MCP server for Dubber — call recording upload/retrieval, compliance metadata and tags, group/account/user management, REST-hook (webhook) notifications, and Dub.Point telecom-system (e.g. BroadWorks) integration.

Built on the MCP 2026-07-28 spec via the split v2 SDK (@modelcontextprotocol/server / /node / /client ^2.0.0-beta.5) with dual-era serving: one shared McpServerFactory behind createMcpHandler({ legacy: 'stateless' }) answers both 2025-era initialize-handshake clients (the WYRE gateway today) and modern 2026-07-28 envelope clients, with an identical, deterministic 37-tool surface for every caller. Ships as a GHCR container only (no MCPB bundle). The Dubber client is @wyre-ai/node-dubber.

Tools (37, flat)

dubbergroupslistunidentifiedrecordings, dubbergroupscreateunidentifiedrecording.

• Core: dubbertestconnection.
• Groups: dubbergroupsget, dubbergroupscreate_child,

dubberrecordingsgetwaveform, dubberrecordingsupdatemetadata, dubberrecordingsaddtags, dubberrecordingsinitiatemultipartupload, dubberrecordingsgetuploadtarget, dubberrecordingscompleteupload. Gated: dubberrecordingsdelete (⚠ DESTRUCTIVE), dubberrecordingsdelete_tags (⚠ HIGH-IMPACT).

• Accounts: dubberaccountscreate, dubberaccountsget, dubberaccountsupdate.
• Recordings: dubberrecordingslist, dubberrecordingscreate, dubberrecordingsget,

dubberusersupdate. Gated: dubberusersdelete (⚠ DESTRUCTIVE).

• Users: dubberuserslist, dubberuserscreate, dubberusersget,

dubbernotificationsget, dubbernotificationsupdate, dubbernotificationsactivate, dubbernotificationslistunclaimed. Gated: dubbernotifications_delete (⚠ HIGH-IMPACT).

• Profile: dubberprofileget.
• Notifications (REST hooks): dubbernotificationslist, dubbernotificationscreate,

dubberdubpoints_find.

• Dub.Point: dubberdubpointslist, dubberdubpointscreate, dubberdubpoints_get,

• OAuth: gated dubberoauthrevoke_token (⚠ HIGH-IMPACT).

Credentials

Four values, all required — none of them a human login (see "Vendor quirks" below).

In gateway mode a request missing any of the four required headers is answered 401 (JSON-RPC error -32001) before the MCP handler runs. It never falls through to env credentials — a header-controlled base URL is likewise refused entirely (env-mode only), so a caller can never redirect client secrets to another host.

When CONDUITS2SSECRET is set (conduit provisions this sidecar's own derived subkey), every request except /health must also carry a valid X-Gateway-S2S HMAC header signed by the gateway, or it is answered 401. This stops a compromised sibling sidecar from impersonating the gateway. Unset, the check is off (the fleet's dormant default).

Running

export NODE_AUTH_TOKEN=$(gh auth token)   # GitHub Packages auth for @wyre-ai/*
npm install
npm run build
node dist/index.js                        # stdio (default)
MCP_TRANSPORT=http node dist/index.js     # HTTP on :8080 (/mcp, /health)
npm run smoke                             # proves both protocol eras serve the same tools

Docker (linux/amd64 per fleet law):

Shortened. The full README is on GitHub.