grokbot-bridge-mcp
Related Servers
Alternatives to grokbot-bridge-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude Code to message configured Grok Bot agents and receive their replies through a local, token-authenticated HTTP MCP endpoint backed by Cursor's BDK. It runs on macOS and Windows and supports asking, checking, listing, and interrupting bot tasks.97 npmMIT
- AlicenseCqualityCmaintenanceEnables IDEs and MCP hosts to drive a user's Grok Bot cloud agents, including sending messages, waiting for replies, reading history, and managing agents, secrets, widgets, handoffs, and desktop access. It acts as an outbound bridge from Cursor, Claude, and VS Code to those cloud agents.21MIT
- AlicenseAqualityDmaintenanceEnables AI agents to manage Grok Bots through MCP: create, list, search, and delete bots, send and receive messages, read conversation transcripts, search message history, and check usage.113MIT
- AlicenseAqualityCmaintenanceLets MCP clients such as Claude Code, Codex, Cursor, and VS Code drive the Grok Bot desktop app on macOS by listing the user's bots, reading their chats, sending them messages, and answering their multiple-choice questions locally without API keys. All actions run live in the real app via the macOS Accessibility API, with no network calls, telemetry, or dependencies.41MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Codex and Claude Code to start or continue conversations with Grok Build, track progress, read completed answers, and cancel running turns using an existing Grok login.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables Claude or other MCP-compatible models to delegate tasks to Grok Bot on a cloud computer, automatically waking it if needed and returning execution results for multi-turn collaboration.1MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct action: ask sends and waits, check retrieves replies since the last interaction, interrupt stops the current turn, and list enumerates bots without sending. The ask/check pair is complementary rather than overlapping, with descriptions explicitly clarifying when to use each (e.g. after ask returns "running").
All four tools follow the same grokbot_<verb> snake_case pattern (check, ask, interrupt, list). The naming is predictable and immediately readable.
Four tools precisely cover the bridge use case: send, poll, interrupt, and enumerate. Nothing feels padded or missing for a focused async messaging bridge.
The core lifecycle is covered: discover bots (list), send work (ask), retrieve async replies (check), and cancel (interrupt). Minor gaps exist, such as no explicit way to clear/acknowledge a reply or inspect conversation history, but agents can work around this.