Skip to main content
Glama
xyte-io

xyte-mcp

Official
by xyte-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to xyte-mcp

No user-submitted related servers found.

    Related Servers

    • teltonika-rms-mcp

      marceloiamunoz
      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

    • Fleet MCP

      SimplyMinimal
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Fleet Device Management for device management, security monitoring, and compliance enforcement through the Model Context Protocol.
      274 PyPI
      5
      MIT
    • Telesherpa Agentic Enterprise Platform by telesherpa

      Telesherpa Agentic Enterpriseofficial

      telesherpa
      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

    • Jamf Pro MCP Server

      dbankscard
      A
      license
      Not graded
      quality
      F
      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.
      38
      MIT
    • @beyondidentity/mcp by gobeyondidentity

      @beyondidentity/mcpofficial

      gobeyondidentity
      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
      10 npm
      Apache 2.0
    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.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

    ActivityMaintained
    ResponsivenessNo issues

    Resources