Skip to main content
Glama
Kargatharaakash

grok-bot-mcp

by Kargatharaakash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to grok-bot-mcp

No user-submitted related servers found.

    Related Servers

    • grokbot-mcp

      Kenzim
      A
      license
      C
      quality
      C
      maintenance
      Enables IDEs and MCP hosts to drive a user's Grok Bot cloud agents, including sending messages, waiting for replies, reading history, and managing agents, secrets, widgets, handoffs, and desktop access. It acts as an outbound bridge from Cursor, Claude, and VS Code to those cloud agents.
      21
      MIT

    • grokbot-mcp

      YunosukeYoshino
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to invoke Grok Bot through a webhook and receive synchronous tool results from its asynchronous callbacks, with run management, cancellation, and budget guardrails.
      MIT

    • Grok Ally

      yikZero
      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

    • Grok Web MCP

      zijueming
      F
      license
      Not graded
      quality
      C
      maintenance
      Automates Grok web interface to provide chat, web search, and conversation management via MCP, supporting multiple accounts and local/remote deployment.
      -

    • Grok MCP Server

      BrewMyTech
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with the Grok AI through an MCP server, supporting chat completions, text completions, embeddings, and model operations with streaming capabilities.
      5
      29 npm
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools target clear distinct operations (account vs bot lifecycle vs transcript vs database). However, get_transcript, read_transcript_entries, and search_messages all operate over transcript data, and list_bots vs search_bots overlap, which could cause occasional misselection.

    Naming Consistency5/5

    All 11 tools follow a consistent snake_case verb_noun pattern (check_usage, switch_account, list_bots, create_bot, delete_bot, send_message, get_transcript, search_bots, list_databases, read_transcript_entries, search_messages). No mixed conventions.

    Tool Count5/5

    11 tools is well within the ideal 3-15 range and each covers a meaningful slice of the domain (accounts, bots, transcripts, databases). Nothing feels redundant or padded.

    Completeness4/5

    Core lifecycle is covered: list/search/create/delete bots, send/get messages, and query databases. Minor gaps exist, e.g. no update_bot and no tool to add/list accounts beyond check_usage/switch_account, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources