Skip to main content
Glama
opsvex-hq

aws-iot-core-mcp

by opsvex-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to aws-iot-core-mcp

No user-submitted related servers found.

    Related Servers

    • Mender MCP Server

      pasinskim
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to interact with Mender IoT platform for device management, deployment monitoring, and fleet analysis through natural language commands. Provides read-only access to device status, deployment logs, releases, and system monitoring capabilities.
      2
      MIT

    • mcp-azure-landing-zone

      jmartinezHNL
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to inspect and audit Azure Landing Zones by inventorying resources, auditing tagging, evaluating policy compliance, and detecting infrastructure drift, all in read-only mode.
      -

    • VFS DMS ChatGPT Plugin

      mergi72
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables read-only file-management operations from AI assistants, including health checks, connection and folder listings, search, share-link resolution, metadata retrieval, and on-demand document reading.
      MIT

    • Sprinklr MCP Server

      daiict218
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants read-only access to Sprinklr data via MCP, allowing querying reports, searching cases, and calling Sprinklr API endpoints.
      7 npm
      ISC

    • safe-sql-mcp

      ahmedabdirahman1-max
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables read-only SQL database access for AI assistants, allowing schema exploration and safe query execution without risk of data modification.
      -
    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

    A4.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    Each tool targets a distinct resource or action, and the descriptions go out of their way to explain relationships (list_things vs describe_thing, list vs describe topic rules, get_device_shadow vs list_named_shadows). The main overlap is that assess_fleet_health internally subsumes shadow freshness, certificate status, and connectivity checks that the single-purpose tools also perform, so an agent must choose between the sweep and the targeted reads.

    Naming Consistency5/5

    All 12 tools use a consistent snake_case verb_noun pattern (list_things, describe_thing, get_device_shadow, search_fleet_index, inspect_thing_certificates, assess_fleet_health). Singular/plural usage is predictable: describe_* for one entity, list_* for collections.

    Tool Count5/5

    12 tools is well-scoped for the IoT Core diagnostic domain, with each tool covering a distinct facet (registry, rules, endpoint, index, shadows, certificates, health sweep). Nothing feels padded or thin.

    Completeness4/5

    The surface thoroughly covers read-only diagnosis across things, rules, shadows, certificates, and fleet indexing with no obvious dead ends for that purpose. Minor gaps exist for adjacent resources like thing groups and jobs, and there is no write/mutation path, though the toolset appears intentionally read-only.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources