Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GROKBOT_TOKENNoCursor JWT if no auth.json
GROKBOT_DATA_DIRNoData directory (default ./data, Docker /data)
GROKBOT_MCP_HOSTNoHTTP bind host (default 127.0.0.1)
GROKBOT_MCP_PATHNoHTTP bind path (default /mcp)
GROKBOT_MCP_PORTNoHTTP bind port (default 8080)
PYTHONUNBUFFEREDNoSet to 1 to ensure unbuffered output
GROKBOT_AUTH_FILENoOverride PKCE credential path (default ~/.config/grokbot-mcp/cursor-auth.json)
GROKBOT_MCP_TOKENNoRequired for HTTP; Bearer shared secret
GROKBOT_MCP_RATE_PER_MINNoRate limit per minute (default 60)
GROKBOT_WAIT_TIMEOUT_SECNoWait timeout in seconds (default 45, clamp 1..120)

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

CapabilityDetails
tools
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": true
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
grokbot_whoamiA

Current Cursor account email, user_id, and grokbot SCHEMA_VERSION.

grokbot_list_agentsA

List Grok Bot cloud agents (id, agent_id, name, description, harness).

grokbot_get_agentB

Get one agent plus todos, sessions, and runtime capabilities.

grokbot_create_agentC

Create a Grok Bot agent. Only when the user asked. harness is box|temporal.

grokbot_update_agentC

Update agent name, description, title, avatar_shape, or avatar_color.

grokbot_delete_agentA

Delete an agent. Without confirm=true this is preview-only.

grokbot_sendB

Send a user message (fire-and-forget). Returns message_id and delivery. Retry with the same message_id.

grokbot_statusC

GetGrokBotSendStatus for a previously sent message_id.

grokbot_historyC

Recent transcript entries (entry_public shape). Default limit 40, max 100.

grokbot_interruptC

Interrupt the agent's current run. Returns had_active_run.

grokbot_draftC

Send an email or Slack draft. Exactly one of email or slack is required.

grokbot_discard_draftC

Discard a pending email or Slack draft for an entry.

grokbot_reactC

React to a transcript entry with an emoji.

grokbot_waitB

Block until the next assistant-ish transcript entry after send, the agent stops running, or timeout. Does not use MCP Tasks.

grokbot_pendingB

List pending widgets and HandoffRequested events. Drops items older than 6 hours.

grokbot_resolve_widgetD

Resolve a widget: respond, dismiss, form, secret, or approve.

grokbot_list_secretsA

List secret names and descriptions for an agent. Values are never returned.

grokbot_put_secretB

Create or replace a secret. The value is never echoed in the result or logs.

grokbot_delete_secretB

Delete a secret. Without confirm=true this is preview-only.

grokbot_desktopB

Account-level sandbox VNC coordinates. wake=true requires confirm=true. Returns run_state, connect_url, and websocket header names (not token values).

grokbot_end_handoffB

Clear a stuck desktop handoff (captcha / login) without waking the box.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
meCurrent Cursor account
agentsGrok Bot roster

TDQS

C2.7/5.0

Scored across 21 tools

Disambiguation4/5

Most tools target distinct resources or actions, and the agent and secret CRUD groups are clearly separated. Some overlap exists among send/status/wait/draft and between pending/history, but descriptions provide enough context to choose correctly.

Naming Consistency3/5

All tool names share the grokbot_ prefix and snake_case, which is consistent. However, the set mixes verb_noun patterns (list_agents, create_agent, resolve_widget) with bare nouns/verbs (status, history, wait, desktop, whoami), making the convention less predictable.

Tool Count3/5

21 tools is on the heavy side for a single server, even though the capabilities span agents, messaging, widgets, secrets, desktop, and handoff. Each area is distinct, but some niche operations could likely be consolidated.

Completeness4/5

Core CRUD for agents and secrets, messaging, widget handling, desktop access, and handoff are all covered. Minor gaps remain, such as todo/session management, draft listing/approval, and transcript search, but the main workflows are supported.

Maintenance

ActivityMaintained
ResponsivenessNo issues