Skip to main content
Glama
Sign In
EMQX Cloud MCP

EMQX Cloud MCP

Official
by emqx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to EMQX Cloud MCP

No user-submitted related servers found.

    Related Servers

    • Octopus Deploy Official MCP

      avieira21139
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to inspect, query, and diagnose projects, deployments, releases, runbooks, tasks, tenants, Kubernetes resources, machines, certificates, accounts, and interruptions, with optional write operations and read-only safeguards.
      449 npm
      MIT

    • VASTOps MCP Server

      ssotoa70
      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

    • Datto EDR MCP Server

      FouadHELLAL7
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to search agents, triage alerts, review target groups, organizations, and locations, follow scans and tasks, inspect rules and extensions, and—with explicit confirmation—scan or isolate hosts through the Datto EDR API.
      36
      Apache 2.0
    • MDRN MCP server

      MDRN MCP serverofficial

      mdrn-io
      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.
      21 npm
      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

    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

    Resources