Spix MCP

What Spix-HQ/spix-mcp MCP server does

Spix-HQ/spix-mcp MCP server makes Spix communication infrastructure available to AI clients through the Model Context Protocol. Agents can place outbound AI calls, inspect call status, retrieve transcripts and summaries, send or read email, exchange SMS, and manage contacts. The server also exposes operations for playbooks, phone-number routing, webhooks, API keys, billing status, credit history, and related analytics.

Readable MCP resources provide another way to access current state. Supported resource patterns include call transcripts and summaries, SMS threads, playbook and contact records, contact history, phone routing, credit balance, and billing information.

How it works

The package acts as a bridge between an MCP client and the Spix REST API. An agent sends an MCP tool request to the local server, which forwards the operation to Spix. Spix then handles the underlying communication service and carrier interactions.

For a voice call, Spix dials through Telnyx or Twilio, uses Deepgram Nova-3 for speech recognition, Claude for conversation turns, and Cartesia Sonic-3 for speech synthesis. Calls are recorded and produce a transcript and summary that the agent can request with the call tools or corresponding resources.

The server supports two tool profiles. The default safe profile provides 43 tools and omits destructive actions such as canceling calls, deleting playbooks, releasing phone numbers, revoking keys, and changing plans. The full profile exposes 49 tools, including those operations. The safe profile is intended for production deployments where destructive access should be restricted.

Setup and configuration

Install the package with pip or run it without a local installation through uvx:

pip install spix-mcp
uvx spix-mcp

A Spix account and API key are required. The Spix CLI must also be installed and authenticated for the documented CLI-based setup commands. Claude Desktop can be configured with uvx and the spix-mcp package, while Cursor can be configured through spix mcp install cursor or an equivalent MCP configuration. The API key is supplied as SPIX_API_KEY.

Optional settings include SPIX_DEFAULT_PLAYBOOK for a default call playbook, SPIX_SESSION_NAME for audit-log session naming, and SPIX_TOOL_PROFILE with either safe or full.

Tools and capabilities

The available tool groups cover:

• Calls: create, list, inspect, cancel, transcribe, and summarize calls.
• Email and SMS: send, reply, list messages, and inspect SMS threads.
• Playbooks: create, update, clone, pause, resume, delete, and manage rules, voices, languages, and emotions.
• Contacts and numbers: create and inspect contacts, review contact history, tag contacts, and bind or release phone numbers.
• Account operations: inspect authentication, manage API keys, view billing and credits, change plans, and register webhook subscriptions.

Limitations and notes

The package requires Python 3.10 or newer, a Spix API key, and a Spix account. Email is available through the free Sandbox, while calls require the Agent plan according to the requirements. Communication and billing operations depend on the Spix backend and its configured services.

Spix-HQ/spix-mcp MCP server is the standalone MCP package; the full Spix CLI includes the MCP server alongside other terminal commands. Choose the standalone package when only MCP access is needed. Use the full profile only with trusted clients because it includes destructive and billing-related operations.