grok-bot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROK_RELAY_ENV | No | Optional path to the env file loaded by scripts/run-mcp.sh (defaults to ~/.config/grok-relay/env). | |
| GROK_WEBHOOK_KEY | Yes | Routine webhook key (required to send tasks). | |
| GROK_WEBHOOK_URL | Yes | Routine webhook URL (required to send tasks). | |
| GROK_RELAY_TASKS_DIR | No | Full task directory (defaults to ./tasks). | ./tasks |
| GROK_RELAY_RESULTS_DIR | No | Result directory (defaults to ./results). | ./results |
| GROK_RELAY_RESULTS_URL | No | Optional HTTP origin for results and task upload (no trailing slash, no /results or /tasks suffix). | |
| GROK_RELAY_RESULTS_TOKEN | No | Bearer token; required when GROK_RELAY_RESULTS_URL or GROK_RELAY_RESULTS_URL_FILE is set. | |
| GROK_RELAY_RESULTS_URL_FILE | No | Optional file containing the results server origin; re-read on every request and retry. |
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 |
|---|---|
| ask_grokA | Send a task to Grok Bot and wait for the answer. Returns the answer, or a request_id with status pending if it times out so you can collect it later with get_grok_result. |
| submit_grok_taskA | Fire-and-forget: start a Grok Bot task and return a request_id immediately. Use get_grok_result to collect the answer later. |
| get_grok_resultA | Look up a previously submitted task by request_id. Returns the result, or status pending if it is not ready yet. A finished result may include an |
| list_grok_artifactsA | List the artifact files Grok Bot attached to a request (name, size in bytes, sha256, content type). Artifacts hold the full detail: reports, source lists, JSON, CSV, XLSX. |
| download_grok_artifactsA | Download a request's artifact files to a local folder (default ~/grok-relay-artifacts/<request_id>/), verifying each sha256. Returns the local paths so you can Read them. Optionally pass names to fetch only some files. |
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 5 tools
ask_grok and submit_grok_task both start a Grok task, which could cause initial confusion, but the descriptions explicitly frame one as blocking and the other as fire-and-forget. The three result/artifact tools (get_grok_result, list_grok_artifacts, download_grok_artifacts) have clearly distinct roles.
All names are snake_case, verb-first, and consistently prefixed with grok (ask_grok, submit_grok_task, get_grok_result, list_grok_artifacts, download_grok_artifacts). ask_grok is a slight deviation from the verb_noun pattern but remains readable and predictable.
Five tools is well-scoped for an async task-submission plus artifact-retrieval server. Each tool covers a distinct stage of the workflow: submit (sync or async), poll, list artifacts, download artifacts.
The lifecycle of submit → poll → retrieve artifacts is fully covered, including checksum verification on download. Minor gaps exist: no cancel/abort for a pending task and no way to list all outstanding requests, but agents can work around these by tracking request_ids.