Spoke Phone MCP by usefulapi
Server Details
Read Spoke calls, transcripts, directory and users; manage phonebook contacts and send SMS.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 27 tools
Each tool maps to a distinct resource+action pair, and the get/list split for calls, transcripts, users, teams, phonebooks and trunks is clear. The only real overlap is the trio of content-analysis tools (list_content_analysis, list_call_content_analysis, get_content_analysis), which differ mainly by scope and require reading the description closely, plus get_phonebook vs get_phonebook_contact which is handled by the descriptions.
All 27 tools use the same spokephone_ prefix followed by a consistent verb_noun snake_case pattern (get_*, list_*, save_*, delete_*, send_*). The single deviation, list_call_content_analysis vs list_content_analysis, still follows the convention and reads naturally.
At 27 tools the set is heavy, exceeding the comfortable range, but there is almost no filler: each tool covers a distinct resource in a broad telephony domain (calls, users, teams, locations, phonebooks, transcripts, AI analysis, trunks, webhooks, directory, SMS). The count is defensible for the domain yet larger than an agent can easily scan.
Read coverage is strong and a few key writes exist (send_sms, save_phonebook_contact, delete_phonebook_contact), but lifecycle gaps are notable: webhooks are read-only (list/get with no create/update/delete), phonebooks can be read but not created or deleted, and users/teams/locations/trunks have no mutation operations. Agents will hit dead ends for subscription and contact-container management.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read calls, contacts, users, teams and numbers; tag calls and create or update contacts.
Place calls, send WhatsApp, manage contacts, leads and campaigns, and read call records and billing
Send and read OpenPhone messages, calls, contacts and phone numbers.
Read Spruce Health contacts, conversations, messages, phone lines and team members (read-only).
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceLets an AI assistant read call and message history, send texts and picture messages, reach Phone Book contacts by name, and — once switched on — place calls run by a voice agent, all limited to the phone numbers the user ticks. Hosted remotely with OAuth sign-in, so nothing needs to be installed locally.MIT- AlicenseAqualityCmaintenanceProvides access to UniFi Talk phone system data including call history, timelines, transcriptions, users, devices, and service health, with read-only operations by default and optional write capabilities.7MIT
- AlicenseNot gradedqualityBmaintenanceHosted MCP server for PacketExchange, the wholesale voice and SMS marketplace. Agents can search routes per mobile network with measured connect and caller ID results, compare prices, send SMS, place and follow calls, run SMS or voice verification codes and check the account balance. Route search works without an API key.MIT

@dialgem/mcpofficial
AlicenseNot gradedqualityCmaintenanceLets AI assistants manage voice agents, calls, and phone numbers, exposing read and write tools plus spend tools gated behind explicit opt-in.Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.