grok-bot
Related Servers
Alternatives to grok-bot
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.70 npmMIT
- 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
- AlicenseAqualityBmaintenanceA fire-and-poll MCP server that lets Claude Code run long background jobs without hitting tool-call timeouts.3MIT
- AlicenseAqualityDmaintenanceMCP server that wraps the Grok CLI to enable code review, adversarial testing, and chat with xAI's Grok model, integrating into any MCP host as a peer reviewer, adversary, and consultant.4118 npm11MIT
- AlicenseNot gradedqualityCmaintenanceA remote MCP server that lets an AI assistant session and a separate agent exchange queued messages via tools like send_to_chief and wait_for_reply, waking the agent with webhooks and long-polling for its replies.1MIT
- AlicenseAqualityBmaintenanceUse XAI's latest api functionalities with Grok MCP. It supports image understanding and generation, live search, latest models and more.2255MIT
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.