Skip to main content
Glama

Related Servers

Alternatives to EMQX Cloud MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with VAST Data clusters for monitoring, listing, and management operations. It provides both read-only and read-write modes for cluster and tenant administration tasks.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI assistants read access to MDRN's workspaces, projects, products, builds, releases, deployments and logs, plus safe write actions such as deploying a connected repository, rolling back, toggling products and managing service variables and services.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to create projects, deploy files, container images, or Git repositories, attach domains, set write-only secrets, add Postgres, read logs, metrics, and failure summaries, and roll back.
      9 npm
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to access Saxo Bank portfolio data, account balances, positions, orders, transactions, and market data such as instruments, quotes, and charts. It is read-only by default, with trading tools available only when explicitly enabled.
      10
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to inspect and manage video renders, templates, generation models, hosted assets, and ingest sources while using isolated private account profiles. It requires explicit approval for mutation operations and supports both MCP and CLI access.
      23
      34 npm
      AGPL 3.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
      39 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: list_projects (projects), list_deployments (deployments), and get_deployment (single deployment status). There is no overlap between them, so an agent can select correctly with confidence.

    Naming Consistency5/5

    All three tools follow a clean verb_noun snake_case pattern (list_projects, list_deployments, get_deployment). The convention is uniform and predictable.

    Tool Count3/5

    Three read-only tools is thin for a deployment-management server that implies lifecycle operations. It is borderline rather than broken, but the surface feels under-scoped for the domain.

    Completeness2/5

    Only read/list operations exist: there is no create, update, delete, or restart deployment, and no access to credentials, metrics, or connection details. Agents managing EMQX Cloud deployments will hit dead ends for any mutating or monitoring workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues