Skip to main content
Glama
hexonal
by hexonal

Related Servers

Alternatives to grok-import-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      F
      maintenance
      Enables chat completions using x.ai's Grok API with support for multiple Grok models (grok-beta, grok-2-latest, grok-4-latest) and configurable parameters like temperature and max tokens.
      1
      4 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM hosts to delegate, fan out, and panel tasks across Claude Code, Codex, Grok, and OpenAI-compatible workers, with optional write access controlled by server flags.
      -
    • 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
      C
      maintenance
      Enables local harnesses to delegate independent text/code, world-knowledge, audio, and image tasks to DeepSeek and Gemini models, with batch submission, status polling, cancellation, and configurable execution limits.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Automates Grok web interface to provide chat, web search, and conversation management via MCP, supporting multiple accounts and local/remote deployment.
      -

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct verb: batch_add_tokens adds, batch_delete_tokens deletes, enable_nsfw toggles a flag, and list_tokens lists. The descriptions clarify scope (specific pool vs. all pools), so there is no overlap or ambiguity.

    Naming Consistency4/5

    Three tools use a clear verb_noun pattern (list_tokens, enable_nsfw, batch_add_tokens), but the 'batch_' prefix on add/delete creates a slight inconsistency. Still, all names are snake_case and readable, with predictable structure.

    Tool Count5/5

    Four tools is perfectly scoped for a focused token management utility. Each tool handles a distinct operation without unnecessary bloat or redundancy.

    Completeness2/5

    The surface is missing key lifecycle operations: delete only works across all pools (not a specific pool), there is no disable_nsfw counterpart, and no way to update token properties besides NSFW. These are significant gaps for a token management tool.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues