grok-bot
Related Servers
Alternatives to grok-bot
No user-submitted related servers found.
Related Servers
- 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 gradedqualityBmaintenanceLets Claude Code drive the user's own Chrome window — opening pages, clicking, and capturing screenshots — over a local stdio native-messaging bridge. Also handles Chrome site-permission prompts automatically and ships diagnostic/doctor tooling for reconnecting the bridge.MIT
- AlicenseAqualityCmaintenanceLets Claude Code and Codex steer each other's live desktop chats on Windows via UI Automation. List and read chats, send messages or mid-turn steers, and pause, resume or edit Codex goals.7MIT
- AlicenseBqualityDmaintenanceEnables Claude Code to send prompts to Claude Desktop using macOS automation and AppleScript. Supports conversation management and configurable response polling, though reading responses back is limited by Electron's accessibility APIs.21MIT
- FlicenseNot gradedqualityDmaintenanceAutomates Grok web interface to provide chat, web search, and conversation management via MCP, supporting multiple accounts and local/remote deployment.-
- AlicenseNot gradedqualityBmaintenanceAn MCP server that lets agents delegate work to Grok Bot desktop app bots by sending messages, waiting for and reading replies, checking weekly usage, and creating, renaming, or deleting Bots. It drives the locally running app over its debug port, so any MCP client can hand tasks to an always-on bot.5MIT
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.