grok-bot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROK_BOT_EXE | No | Path to the Grok Bot executable if it is installed somewhere other than the default location. | |
| GROK_CDP_PORT | No | Debug port to use instead of the default Chromium DevTools port 9333. | 9333 |
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 |
|---|---|
| grok_sendA | Send a message to a bot in the Grok Bot desktop app and wait for its reply. Grok Bot is an agent that can browse the web, make phone calls, send email, and run routines, so it may act on the message. If it is still working when the wait ends, call grok_read later to get the rest. |
| grok_readA | Read the latest messages in a Grok Bot chat (also shows whether the bot is still working). |
| grok_list_botsA | List the bots in the Grok Bot app and which one is open. |
| grok_select_botB | Switch the Grok Bot app to a different bot. |
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 4 tools
Each tool targets a distinct action on a distinct concern: sending a message, reading messages, listing bots, and switching the active bot. There is no realistic way to confuse send with read, or list_bots with select_bot, since the descriptions explicitly contrast them (e.g. grok_send tells the agent to use grok_read afterward).
All four tools use a single predictable scheme: the `grok_` prefix followed by a lowercase snake_case verb, with `_bots` appended when operating on the bot list. There is no mixing of camelCase, bare verbs, or alternative prefixes.
Four tools is a lean but coherent surface for a desktop-app bridge, and each one earns its place (send/read for chat, list/select for bot management). It is on the thin side, and a couple more operations (e.g. starting a new chat) would round it out.
The core loop of listing/selecting a bot and sending/reading messages is covered, but there is no way to start a new chat/conversation, cancel or interrupt a running bot, or discover existing chats beyond the 'latest messages' read. These are notable gaps an agent could hit when the current chat is not the one it wants.