Skip to main content
Glama
BasisSetVentures

Grok CLI MCP Server

by BasisSetVentures
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Grok CLI MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Gemini CLI

      choplin
      A
      license
      Not graded
      quality
      C
      maintenance
      Wraps Google's Gemini CLI to expose search, chat, and file analysis tools via the Model Context Protocol for AI assistants.
      87 npm
      101
      MIT

    • Gemini Agent MCP Server

      LeeSinLiang
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a Model Context Protocol interface to the Gemini CLI, enabling AI agents to call the Gemini model and interact with development tools like code linting, GitHub operations, and documentation generation. Includes security measures to prevent unauthorized file access through path validation.
      3
      MIT

    • PyCLI MCP

      ofek
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language interaction with any Python CLI application (Click, Typer, Argparse) through the Model Context Protocol.
      23
      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

    B3.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    The tools have distinct primary purposes: grok_chat handles multi-turn conversations by flattening messages, grok_code focuses on code-related queries with language hints, and grok_query is for single-prompt interactions with raw output options. However, grok_chat and grok_query both involve sending prompts to Grok, which could cause minor confusion about when to use each for simple queries.

    Naming Consistency5/5

    All tool names follow a consistent 'grok_' prefix pattern with descriptive suffixes (chat, code, query), using snake_case uniformly. This makes the tools easily identifiable and predictable within the server's domain.

    Tool Count4/5

    With 3 tools, the count is reasonable for a CLI server focused on interacting with Grok, covering chat, code, and general query use cases. It is slightly lean but not insufficient, as each tool addresses a specific aspect of the Grok interface.

    Completeness3/5

    The tools cover core functionalities for querying Grok (chat, code, general queries), but there are notable gaps such as missing operations for managing sessions, handling file uploads, or configuring settings, which might limit advanced workflows in a CLI context.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources