Google Voice MCP
Related Servers
Alternatives to Google Voice MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables sending, reading, searching, and managing SMS/RCS messages through Google Messages web interface, requiring a persistent browser session paired with a phone.AGPL 3.0
- AlicenseAqualityCmaintenanceEnables reading and sending messages in Google Messages for web through a paired Chrome tab using chromefile, with tools for status, listing conversations, reading message history, and sending texts.4MIT
- AlicenseAqualityBmaintenanceEnables AI agents to list spaces, read and search Google Chat conversations, and send messages or thread replies by driving the Chat web app in a signed-in Chrome profile, with no Google Chat API, OAuth app or Cloud project required.7452 npmMIT
- AlicenseAqualityBmaintenanceAccess your Carbon Voice conversations and voice memos—retrieving messages, conversations, voice memos, and more as well as send messages to Carbon Voice users.44396 npm10ISC
- AlicenseAqualityBmaintenanceEnables MCP clients to connect to Google Messages for Web for session-status checks and, eventually, message preparation and confirmation workflows without exposing secrets.1Apache 2.0
- AlicenseAqualityCmaintenanceEnables agents to reuse a human-completed Chrome login session to open confirmed origins, read visible page text, and perform single click, fill, or key press actions without ever handling passwords or exposing cookies.6MIT
TDQS
Scored across 7 tools
Most tools are clearly distinct (list vs read vs send vs mark_read target different operations). The closest pair is gv_reply_sms vs gv_send_sms and gv_list_sms vs gv_read_sms, but descriptions clarify that one replies to an existing conversation and the other sends to new numbers, and one lists conversations while the other reads messages within.
All tools follow a consistent gv_ prefix with a clear verb_noun pattern (list_sms, send_sms, read_sms, reply_sms, mark_read, check_login). No camelCase mixing or vague verbs.
Seven tools is well-scoped for an SMS-focused Google Voice integration, with each tool earning its place across the login and messaging lifecycle.
The SMS lifecycle is well covered: login, verify, list, read, send, reply, and mark read. Minor gaps exist (no delete/archive conversation, no unread marking or search, and no call/voicemail coverage despite the 'Google Voice' name), but core workflows are complete.