Skip to main content
Glama

Related Servers

Alternatives to twingate-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides read-only access to TrustLayer's public API, enabling users to query and retrieve data about parties, documents, projects, and other TrustLayer entities through MCP-compatible tools.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Microsoft Intune through the Microsoft Graph API, enabling MCP clients to query managed devices, apps, compliance policies, and configuration profiles.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only inspection of Cloudflare account resources, including zones, DNS records, Workers, Pages projects, R2 buckets, and Tunnels, via a secure MCP endpoint.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Google Ads account data including campaigns, ad groups, keywords, and performance reports. Enables querying via GAQL through an MCP interface.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to discover schemas, keys, and lineage across bronze, silver, and gold tables, and to run guarded read-only SQL queries against the lakehouse.
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only access to Aruba Fabric Composer inventory, network state, and VMware vCenter/vSphere visibility through MCP tools over streamable HTTP.
      -

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource or a distinct direction of an access query: list_* tools each cover one entity type, get_user is the single-email lookup complement to list_users, and get_user_access (user→resources) is clearly the inverse of get_resource_access (resource→principals). Descriptions explicitly cross-reference each other to steer selection, leaving no realistic misselection risk.

    Naming Consistency5/5

    Uniform verb_noun snake_case throughout: list_* for enumerations (groups, resources, users, remote_networks, connectors, devices) and get_* for targeted lookups (user, user_access, resource_access). No camelCase or vague verbs intrude.

    Tool Count5/5

    Nine tools is well within the ideal 3-15 range and each earns its place by covering a distinct Twingate entity or access relationship. Nothing looks padded or redundant.

    Completeness3/5

    The read-only/audit surface is coherent and covers the main entities plus access relationships, but it is entirely queries: there are no create, update, or delete operations for users, groups, resources, or connectors, and no get_group/get_resource/get_connector single-item lookups. An agent can investigate but cannot remediate anything it discovers.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues