grokbot-messages
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_MESSAGES_API_KEY | Yes | Relay API key; to be replaced by a runtime read of the page config (#3) | |
| GOOGLE_MESSAGES_SESSION_KEY | Yes | Passphrase (>=16 chars) used to encrypt the session file | |
| GOOGLE_MESSAGES_SESSION_PATH | Yes | Path to the encrypted session file | |
| GOOGLE_MESSAGES_GOOGLE_COOKIES | No | Optional. Google web-session cookies, needed only for Google-account pairing. Google cookies grant broad access to your whole Google account, not just Messages. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_session_statusA | Report whether Google Messages is paired and when the auth token expires. Never returns secrets. |
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 1 tool
There is only one tool, so there is no possibility of confusion or misselection between tools. Its purpose is clearly stated and distinct.
The single tool uses a clear snake_case verb_noun pattern consistent with common MCP conventions. With only one name, there are no inconsistent naming styles to compare.
For a server apparently focused on messages, one tool is far too few. A single status-check tool does not provide a meaningful operational surface.
The tool surface is severely incomplete for a messaging server. It only reports session status and lacks core operations such as sending, listing, reading, or managing messages.