A
licenseA
qualityC
maintenanceGives AI agents phone numbers, email, SMS, and voice calls as MCP tools, enabling them to provision numbers, capture 2FA codes, send messages, and make calls.
15
MIT
Spix
Officialby Spix-HQ
Related Servers
Alternatives to Spix
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceManage voice AI agents, make calls, run campaigns, and control phone numbers through natural language.5811 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage phone numbers, send/receive SMS, and place voice calls through natural language, connecting to the phone network via the AgentPhone API.281 npm124MIT
@telitask/mcp-serverofficial
FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage phone calls, contacts, and tasks directly, including making and scheduling calls, retrieving transcripts, and handling contact and to-do items.1-
VoidMob MCPofficial
AlicenseAqualityAmaintenanceProvides 28 tools for mobile proxies, non-VoIP SMS verifications, dedicated numbers, and global eSIMs, enabling AI agents to perform phone-related tasks.29429 npm35MIT- AlicenseNot gradedqualityCmaintenanceGives an AI assistant its own real phone number and email address so it can place and answer calls, book reservations by phone, send and receive texts, and read written summaries, structured details, and transcripts of every conversation. Also manages contacts, persona and voice settings, webhooks, and a unified call/message history through a hosted OAuth-secured MCP endpoint requiring no local code.MIT
TDQS
B3.1/5.0
Scored across 43 tools
Disambiguation5/5
Each tool targets a distinct resource and action, with clear separation across domains like auth, billing, calls, contacts, etc. No two tools appear to perform the same function, and descriptions further clarify any potential overlap.
Naming Consistency3/5
Tools follow a spix_{domain}_{action} pattern, but actions vary: some are verbs (create, list, send), others are nouns (credits, history) implying list/show. This mixed convention, while readable, lacks full uniformity.
Tool Count3/5
With 43 tools across many domains, the count is high but justified by the broad scope. However, it borders on excessive for an MCP server, as agents may face decision overload. Could be trimmed or grouped more efficiently.
Completeness4/5
The tool surface covers core communication workflows: calls, contacts, emails, SMS, playbooks, billing, and webhooks. Minor gaps exist (e.g., email attachments, call recording), but the set is largely sufficient for the platform's purpose.
Maintenance
ActivityInactive
ResponsivenessUnresponsive