Skip to main content
Glama

Related Servers

Alternatives to xyte-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query and operate a fleet of remote management devices through the RMS API in natural language, including device status, data usage, alerts, fleet summaries, and guarded reboots.
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to query and manage monitoring data through structured tools, covering alerts, devices, metrics, dashboards, reports, remediation workflows, and optional AI/ML analysis integrations.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Fleet Device Management for device management, security monitoring, and compliance enforcement through the Model Context Protocol.
      230 PyPI
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to self-register, authenticate, and operate a no-code ontology and knowledge-graph platform for facility management, field service, CRM, fleet management, workflow automation, and related business processes through 172 tools.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Jamf Pro for comprehensive Apple device management, including device inventory, policy deployment, configuration profiles, script execution, and compliance reporting.
      39
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to directly manage Beyond Identity resources such as identities, groups, applications, SSO configurations, and credentials via natural language tool calls.
      36
      7 npm
      Apache 2.0

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct role: listing endpoints, describing a specific endpoint, and making an API call. There is no overlap or ambiguity.

    Naming Consistency4/5

    All tools start with 'xyte_' and follow a resource_action pattern, but there is a minor inconsistency: 'xyte_endpoints_list' uses plural 'endpoints' while 'xyte_endpoint_describe' uses singular 'endpoint'.

    Tool Count5/5

    With three tools, the server covers the essential workflow for an API wrapper: discover, describe, and call. It is well-scoped and not excessive or sparse.

    Completeness5/5

    The tools provide a complete cycle for interacting with the Xyte API: listing available endpoints, getting detailed parameters for a specific endpoint, and executing the call. No obvious gaps are present.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues