grokbot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_API_KEY | Yes | API key for authenticating MCP clients. Used as `Authorization: Bearer $MCP_API_KEY` or `X-API-Key: $MCP_API_KEY`. Generate with `openssl rand -hex 32`. | |
| CURSOR_WEBHOOK_URL | Yes | The POST URL of your Grok Bot routine (trigger: Webhook). | |
| CURSOR_WEBHOOK_API_KEY | Yes | The Key of your Grok Bot routine, used to authenticate the outgoing webhook call. | |
| CALLBACK_SIGNING_SECRET | Yes | Secret used to compute the HMAC-SHA256 callback token that authenticates callbacks from Grok Bot to the Worker. Generate with `openssl rand -hex 32`. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues