Skip to main content
Glama
djtelicloud

UniGrok

by djtelicloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to UniGrok

No user-submitted related servers found.

    Related Servers

    • Toolport

      btsouth
      A
      license
      A
      quality
      A
      maintenance
      One local gateway for all your MCP servers — shared by every AI coding tool (Claude, Cursor, VS Code, Codex). Set up each server once; keys stay in the OS keychain; lazy discovery keeps agent context small. Local-first, open source.
      4
      3 npm
      232
      MIT

    • Grok Codex

      Meapri
      A
      license
      A
      quality
      D
      maintenance
      MCP server for integrating xAI's Grok model into OpenAI Codex Desktop/GUI, enabling direct Grok calls via chat completions or responses with OAuth or API key authentication.
      9
      MIT

    • Mullet

      tomgould
      A
      license
      C
      quality
      A
      maintenance
      Exposes an MCP toolset that routes each coding task to the cheapest capable model, from a free local LLM up to Claude, while giving clients file, shell, git, web, memory, knowledge-search and parallel swarm-delegation capabilities. Also allows an OpenAI-compatible REST and WebSocket API to be served for non-MCP clients.
      53
      Business Source 1.1
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 47 tools

    Disambiguation2/5

    Many tools have overlapping purposes, such as multiple chat/agent tools (`agent`, `chat`, `grok_agent`, `stateful_chat`) and multiple model listing tools (`list_models`, `list_models_detailed`). While descriptions attempt to differentiate, the overlap is significant and would likely cause misselection.

    Naming Consistency2/5

    Tool names are inconsistent in style: some are short single words (`agent`, `chat`), while others use long snake_case phrases (`grok_mcp_discover_self`, `remote_code_execution`). No clear pattern emerges, mixing verbs and nouns.

    Tool Count2/5

    47 tools is excessively high for a single MCP server. While the server covers many domains (chat, git, knowledge, media, etc.), the tool set would be more coherent if split into specialized servers. The count feels unwieldy.

    Completeness4/5

    The server covers a wide range of functionality including chat, agent, file management, web/X search, code execution, research jobs, knowledge memory, git operations, and media generation. Minor gaps exist (e.g., missing git push/pull, knowledge update), but overall it is fairly complete for its domain.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources