Skip to main content
Glama
Google Voice MCP

Google Voice MCP

by hashirskh

Related Servers

Alternatives to Google Voice MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      7
      452 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Access your Carbon Voice conversations and voice memos—retrieving messages, conversations, voice memos, and more as well as send messages to Carbon Voice users.
      44
      396 npm
      10
      ISC
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to connect to Google Messages for Web for session-status checks and, eventually, message preparation and confirmation workflows without exposing secrets.
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      6
      MIT

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    Seven tools is well-scoped for an SMS-focused Google Voice integration, with each tool earning its place across the login and messaging lifecycle.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues