Skip to main content
Glama

Related Servers

Alternatives to grokbot-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      11
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Bridges remote MCP clients like Cursor, Grok Bot, and Claude Desktop to a locally running Grok Build agent over ACP/WebSocket, enabling session creation, prompting, cancellation, and status checks through standard MCP tools.
      5
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables ChatGPT Desktop and Codex to delegate substantial work to a locally installed Grok Build agent. Supports consultations, background builder/tester jobs, cancellation, session discovery, and transcript export.
      7
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects ChatGPT and MCP clients to authorized local development environments, enabling secure file access, shell execution, persistent tasks, browser/desktop control, and remote management of projects.
      13
      MIT

    TDQS

    C2.7/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools target distinct resources or actions, and the agent and secret CRUD groups are clearly separated. Some overlap exists among send/status/wait/draft and between pending/history, but descriptions provide enough context to choose correctly.

    Naming Consistency3/5

    All tool names share the grokbot_ prefix and snake_case, which is consistent. However, the set mixes verb_noun patterns (list_agents, create_agent, resolve_widget) with bare nouns/verbs (status, history, wait, desktop, whoami), making the convention less predictable.

    Tool Count3/5

    21 tools is on the heavy side for a single server, even though the capabilities span agents, messaging, widgets, secrets, desktop, and handoff. Each area is distinct, but some niche operations could likely be consolidated.

    Completeness4/5

    Core CRUD for agents and secrets, messaging, widget handling, desktop access, and handoff are all covered. Minor gaps remain, such as todo/session management, draft listing/approval, and transcript search, but the main workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues