MCP Server

Connect AI coding assistants like Claude Code and Cursor to your VoiceDock account via the hosted Model Context Protocol server — just sign in, no API key to paste.

VoiceDock exposes a hosted Model Context Protocol (MCP) server at mcp.hmsovereign.com. This lets AI assistants — including Claude, Claude Code, Cursor, and any other MCP-compatible tool — interact with your VoiceDock account directly, without leaving your environment.

Once connected, your AI assistant can list assistants, initiate calls, check usage, manage campaigns, and perform any other operation available in the API — all through natural language.

Endpoint

https://mcp.hmsovereign.com/mcp

The server dynamically loads the VoiceDock OpenAPI spec and exposes every API endpoint as an MCP tool. It stays in sync automatically — no configuration changes are required when the API is updated.

Authentication

The MCP server is an OAuth 2.1 resource server. You connect with just the URL above — no key to copy. Your client discovers the sign-in flow automatically, opens a browser where you log in with your VoiceDock account and approve access, and then works against your organisation. Behind the scenes we map your account to your organisation's credentials; you never handle an API key.

Tip: Prefer a static token (CI, scripts, servers)? A raw organisation API key still works as a Bearer token — see Legacy: API key below.

Setup

Claude Code / Cursor / Claude Desktop

Add the endpoint and let the client run the sign-in flow:

{
  "mcpServers": {
    "voicedock": {
      "type": "http",
      "url": "https://mcp.hmsovereign.com/mcp"
    }
  }
}

The first time you connect, a browser opens: sign in with your VoiceDock account and click Allow on the consent screen. That's it — the tools appear in your assistant.

Claude Desktop: Settings → Connectors → Add custom connector → paste the URL.
Claude Code: claude mcp add --transport http voicedock https://mcp.hmsovereign.com/mcp (or add the JSON above).
Cursor: MCP settings → add the JSON above.

Other MCP clients

Any client that supports the MCP Streamable HTTP transport and OAuth can connect with the URL alone:

URL: https://mcp.hmsovereign.com/mcp
Transport: Streamable HTTP
Auth: OAuth 2.1 (the server advertises its authorization server via protected-resource metadata; clients register dynamically and prompt you to sign in)

Legacy: API key

If your client can't run an OAuth flow, or you're wiring this into a server or CI job, pass an organisation API key as a bearer token instead:

{
  "mcpServers": {
    "voicedock": {
      "type": "http",
      "url": "https://mcp.hmsovereign.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Find your API key in the dashboard under Developer → Your API Key. Both methods resolve to the same organisation.

Available Tools

The MCP server exposes all VoiceDock API endpoints as tools — one tool per endpoint. Examples:

Tool	Description
`listAssistants`	List all voice assistants in your organization
`createAssistant`	Create a new voice assistant
`getAssistant`	Retrieve a specific assistant by ID
`updateAssistant`	Update assistant configuration
`createOutboundCall`	Initiate an outbound call
`listCalls`	List calls with optional filters
`getCall`	Get call details including transcript and analysis
`createCampaign`	Create an outbound call campaign
`listVoices`	Browse available TTS voices
`getUsage`	Retrieve usage and billing data

The full list of tools mirrors the API reference.

Example Usage

Once connected, you can ask your AI assistant to perform tasks in plain language:

"Create a new assistant called 'Support Bot' with a friendly greeting and GPT-4o as the language model."

"List all calls from this week and summarize the outcomes."

"Start an outbound call to +31612345678 using assistant ID xyz."

"Show me my usage for the last 30 days."

Security

OAuth 2.1 with your own account — no long-lived key to copy, share, or leak. Access is tied to your VoiceDock login, shown on an explicit consent screen, and revocable from your client at any time.
The MCP server is stateless — no session data is retained between requests.
All tool calls are scoped to your organisation, derived from your signed-in identity (or, for the legacy path, your API key).
Traffic is TLS-only and the token is never logged by the MCP server.
Only approve connections you started yourself. The consent screen names the app requesting access — if you don't recognise it, click Deny.

Troubleshooting

The browser sign-in doesn't open

Make sure your client supports remote MCP servers with OAuth (recent Claude Desktop, Claude Code, and Cursor do). If it can't, use the legacy API-key method instead.

Tools not appearing after connecting

Reconnect the server so the client re-fetches the tool list. For the legacy path, verify your API key is valid:

curl https://api.hmsovereign.com/api/v1/assistants \
  -H "Authorization: Bearer YOUR_API_KEY"

Server unavailable

Check status.hmsovereign.com for current platform status.

Note: The MCP server is read/write — connected AI assistants can create, update, and delete resources on your behalf. Approve only trusted apps on the consent screen, and keep any legacy API key to trusted environments.

On this page