Google Voice MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLEVOICE_STATE_DIR | Yes | Absolute path to a private local directory for the browser profile. Keep it outside the repository. | |
| GOOGLEVOICE_DEBUG_PORT | Yes | A free localhost port for Chrome DevTools debugging, for example 19223. | |
| GOOGLEVOICE_ALLOW_WRITES | No | Leave unset or set to 0 while setting up. Set to 1 only when you intend to allow send, reply, and mark-read tools. | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gv_loginA | Launch system Chrome with remote debugging for Google login. The user connects via SSH tunnel and chrome://inspect to complete login (including 2FA). After login, call gv_check_login to verify. |
| gv_check_loginB | Check whether the user is currently logged into Google Voice. |
| gv_list_smsB | List recent SMS conversations from Google Voice. Returns conversation ID, contact, last message snippet, timestamp, and read/unread status. |
| gv_read_smsA | Read messages within a specific SMS conversation. Returns individual messages with sender, text, timestamp, and direction. |
| gv_send_smsC | Send a new SMS message to one or more phone numbers via Google Voice. |
| gv_reply_smsB | Reply to an existing SMS conversation. |
| gv_mark_readB | Mark an SMS conversation as read. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.