MCP Server

Connect AI coding assistants like Claude Code and Cursor to your HMS Sovereign account via the hosted Model Context Protocol server.

HMS Sovereign exposes a hosted Model Context Protocol (MCP) server at mcp.hmsovereign.com. This allows AI coding assistants — including Claude Code, Cursor, and any other MCP-compatible tool — to interact with your HMS Sovereign account directly, without leaving your development 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 HMS Sovereign OpenAPI spec and exposes all API endpoints as MCP tools. It stays in sync automatically — no configuration changes are required when the API is updated.

Authentication

Your HMS Sovereign API key is passed via the Authorization header in your MCP configuration. The server forwards this header to the API on every tool call.

Find your API key in the dashboard under Settings → API Keys.

Setup

Claude Code

Add the following to your Claude Code MCP configuration file (.claude/mcp.json or via /mcp add):

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

Cursor

Add to your Cursor MCP settings:

{
  "mcpServers": {
    "hms-sovereign": {
      "url": "https://mcp.hmsovereign.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Other MCP clients

Any client that supports the MCP Streamable HTTP transport can connect using:

URL: https://mcp.hmsovereign.com/mcp
Transport: Streamable HTTP
Auth: Authorization: Bearer YOUR_API_KEY header

Available Tools

The MCP server exposes all HMS Sovereign 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

Your API key is transmitted over TLS and never logged by the MCP server
The server is stateless — no session data is retained between requests
All API calls are scoped to your organization via your API key
The MCP server itself requires no additional credentials beyond your existing HMS Sovereign API key

Troubleshooting

Tools not appearing in your AI assistant

Verify your MCP configuration is correct and that your API key is valid. You can test the key directly:

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

Authentication errors on tool calls

Ensure the Authorization header is set in your MCP client configuration, not as a query parameter or in the URL.

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. Only share your API key with trusted environments and tools.

On this page