Spix MCP Server
Give AI agents the ability to make phone calls and send emails — as MCP tool calls.
Spix is communications infrastructure for AI agents. This MCP server exposes Spix's API as tools that any MCP-compatible client (Claude Desktop, Cursor, Windsurf, etc.) can use.
What your agent gets
Tool | Description |
| Make an outbound AI phone call |
| Get the full transcript of a call |
| Get an AI-generated call summary |
| Send an email |
| Reply to an email thread |
| Create or update a contact |
| Cross-channel interaction history |
| AI summary of contact relationship |
| List available playbooks |
| Check credit balance |
20+ tools total. Run spix-mcp to see the full list.
Quick start
1. Get a Spix API key
Sign up at app.spix.sh or via the CLI:
curl -fsSL https://github.com/Spix-HQ/spix-cli/releases/latest/download/spix-darwin-arm64 -o spix
chmod +x spix && sudo mv spix /usr/local/bin/
spix signup
spix auth key create --name mcp2. Install
pip install spix-mcpOr run directly with uvx (no install):
uvx spix-mcp3. Configure Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"spix": {
"command": "uvx",
"args": ["spix-mcp"],
"env": {
"SPIX_API_KEY": "your-api-key"
}
}
}
}Restart Claude Desktop. Spix tools will appear in the tools panel.
Cursor / Windsurf
{
"mcpServers": {
"spix": {
"command": "uvx",
"args": ["spix-mcp"],
"env": {
"SPIX_API_KEY": "your-api-key"
}
}
}
}Configuration
All configuration is via environment variables:
Variable | Required | Description |
| Yes | Your Spix API key |
| No | Default playbook ID for calls |
| No | Session name for audit logging |
| No |
|
Tool profiles
Safe profile (default): Read operations + create calls/emails. Cannot delete resources or modify billing.
Full profile: All operations including delete, billing management, and admin tools.
{
"env": {
"SPIX_API_KEY": "your-key",
"SPIX_TOOL_PROFILE": "full"
}
}Session scoping
Restrict what your agent can access:
{
"env": {
"SPIX_API_KEY": "your-key",
"SPIX_DEFAULT_PLAYBOOK": "your-playbook-id",
"SPIX_SESSION_NAME": "sales-bot"
}
}How it works
Your Agent (Claude, etc.)
↓ MCP tool call
Spix MCP Server (this package)
↓ HTTP API call
Spix Backend (api.spix.sh)
↓ Carrier APIs
Phone call / Email / SMSThe MCP server is a thin bridge between MCP protocol and the Spix REST API. All business logic runs server-side. The MCP server handles:
Tool schema generation from the API spec
Session scoping and access control
Request/response formatting for MCP protocol
Voice calls
When your agent calls spix_call_create, Spix:
Dials the number via Telnyx/Twilio
Uses Deepgram Nova-3 for real-time speech recognition
Uses Claude for conversation turn generation
Uses Cartesia Sonic-3 for text-to-speech
Records the call and generates a transcript + summary
Your agent can then read the transcript and summary via spix_call_transcript and spix_call_summary.
Links
License
MIT