A
licenseNot graded
qualityB
maintenanceEnables 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.
1
MIT
call-grokbot
by ZensHQ
Related Servers
Alternatives to call-grokbot
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables delegating bounded tasks from Codex to Claude Code, including read-only reviews, isolated branch edits, long-running background work, and approval handling.353 npmMIT
- AlicenseAqualityBmaintenanceEnables any MCP client such as Cursor, Claude Code, or Codex to dispatch tasks to a Cursor Grok Bot running on its cloud computer, poll for its replies, and interrupt an in-progress run. It also lists the bots available for contact, without routing replies through an extra model.41MIT
- AlicenseAqualityBmaintenanceEnables Codex to ask Claude Code for an independent opinion or delegate tasks, then follow up in the same isolated, resumable Claude session.21MIT
- AlicenseAqualityDmaintenanceEnables Codex to delegate coding tasks to Grok Build CLI, with Codex handling planning and review while Grok executes.63MIT
- AlicenseNot gradedqualityCmaintenanceEnables Codex and local Claude Code sessions to exchange messages in both directions, letting Codex list sessions, send messages, and receive replies as new turns while Claude sessions can message Codex threads.353 npmMIT
TDQS
A4.1/5.0
Scored across 4 tools
Disambiguation5/5
Each tool maps to a distinct action: list discovers bots, ask sends work, check reads results, and interrupt stops work. The descriptions explicitly clarify the ask/check boundary, so an agent can select the right tool reliably.
Naming Consistency5/5
All four names are single lowercase imperative verbs in a consistent style: list, ask, check, interrupt. There is no mixing of camelCase, snake_case, or verb/noun patterns.
Tool Count5/5
Four tools is a well-scoped set for a focused bot interaction client, with each tool covering a distinct part of the loop: discovery, sending, polling, and interruption. No tool feels redundant or missing from the core count.
Completeness4/5
The surface covers the essential lifecycle: list bots, send a task, check replies, and interrupt running work. A minor gap is the lack of explicit bot detail or historical conversation retrieval beyond new replies, but the core workflow is complete.
Maintenance
ActivityNo data
ResponsivenessNo issues