grok-delegate
Related Servers
Alternatives to grok-delegate
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible agents like ChatGPT and Claude to securely access a Grok Bot workstation's folder-scoped files, shell, and Git tools over HTTPS+OAuth or local stdio, and to orchestrate specialized Grok Bot agents via a message bridge.1MIT
- AlicenseAqualityCmaintenanceExposes local Grok Build bridge as MCP stdio server, enabling code agents like Claude Code to run Grok models, check status, and manage runs.640 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides a stdio MCP bridge for coding agents to query and record engineering knowledge locally, preserving debugging history, failed attempts, and verified solutions.0MIT

GenieOS MCP Serverofficial
AlicenseAqualityCmaintenanceStdio bridge for editors to connect to the GenieOS MCP server, enabling AI agents to interact with GenieOS via Streamable HTTP transport.642 npmMIT- AlicenseNot gradedqualityFmaintenanceLocal stdio MCP server for working on Intern-hosted sites through guarded Git checkouts. It enables authentication, site preparation, testing, validation, and publishing via coding harnesses like Codex and Claude Code.43 npmMIT
- AlicenseAqualityBmaintenanceBridges MCP clients such as Claude Code and Cursor to independent Codex app-server sessions, letting them start, poll, steer, review, compact, cancel, and answer prompts for asynchronous Codex tasks over local stdio or a remote authenticated WebSocket. Runs read-only by default, with workspace-write sandboxing only when a user explicitly enables it, and reports job status, model listing, and progress back to the client.101MIT
TDQS
Scored across 23 tools
Most tools are individually distinct and well-described, but the grok_agent_* vs grok_delegate_* families create overlapping clusters: grok_agent_status/grok_delegate_status, grok_agent_poll/grok_delegate_poll, and grok_agent_start/grok_delegate_start/grok_delegate all require careful reading to pick the right one. The descriptions help, but an agent could easily select the wrong family.
Names consistently use snake_case and mostly follow a prefix_verb pattern, but the two prefixes grok_agent_ and grok_delegate_ are used without a clear rule, and several tools are nouns (economy, project, models, doctor) rather than verb_noun. Session tools are internally consistent, but the mixed conventions reduce predictability.
23 tools is on the heavy side for one server and the count is inflated by four separate status/diagnostic tools plus multiple start/poll variants. The scope is broad enough that most tools earn their place, but some consolidation of status and session helpers would improve focus.
The surface covers configuration, session lifecycle, job lifecycle, sync/async delegation, review/execute/fix variants, and diagnostics, which is sufficient for the primary workflows. Minor gaps remain—no cancel for background delegate jobs and no unified job listing—but agents can work around them.