Skip to main content
Glama
chuotdelongchamp

hex-mcp-server

Related Servers

Alternatives to hex-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Databricks workspaces programmatically, providing comprehensive tools for cluster management, notebook operations, job orchestration, Unity Catalog data governance, user management, permissions control, and FinOps cost analytics.
      534 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with OpenHEXA platform through Claude Desktop, allowing users to query workspaces, list datasets, search pipelines, and view pipeline runs using natural language.
      1
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables MCP-capable agents to interact with Dock workspaces, including reading, creating, updating, and deleting rows, managing workspaces, and retrieving activity logs.
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable agents to manage Meshive GPU Cloud resources, including account, workspaces, pods, storage, GPUs, templates, serverless deployments, tasks, assets, machines, and billing history.
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to author and manage workflows, agents, tools, skills, policies, and reference docs in an Axonity tenant via the public REST API, with guardrails preventing direct publishing and secret exposure.
      100
      13 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables async chat with AnythingLLM workspaces so slow local-model answers never trip the ~60s MCP tool-call timeout, plus full workspace management (list, get, create, update, delete), document listing, and embedding updates over the AnythingLLM REST API.
      9
      MIT

    TDQS

    C2.7/5.0

    Scored across 58 tools

    Disambiguation4/5

    Most tools target distinct resource+action pairs, with clear descriptions separating similar operations like chart image from draft vs run, or suggestion vs suggestion-change updates. A few boundaries are fuzzy (e.g. hex-update-project for status/endorsements vs hex-update-semantic-project, and edit/update verb overlap across resources), but these are minor and descriptions disambiguate.

    Naming Consistency4/5

    The hex-<verb>-<resource> pattern is largely consistent across hyphenated names. Minor deviations appear in verb choice (edit vs update for similar operations) and edge cases like hex-get-me and hex-batch-update-compute-profile, but the overall convention remains predictable.

    Tool Count1/5

    58 tools is far beyond the typical 3-15 well-scoped range and exceeds the 50+ threshold for extreme mismatch. Even accounting for the broad Hex platform surface, this volume creates a heavy cognitive load for an agent.

    Completeness3/5

    Core lifecycle coverage exists for many resources (projects, cells, collections, data connections, groups, threads, suggestions), but notable gaps remain: no delete for projects, collections, data connections, or threads; no single-guide get; users only have deactivate, not create. These gaps are significant enough that agents will hit dead ends for some administrative workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues