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

    • Fleet MCP

      SimplyMinimal
      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.
      212 PyPI
      5
      MIT

    • Jamf Pro MCP Server

      dbankscard
      A
      license
      Not graded
      quality
      C
      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.
      35
      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
      9 npm
      Apache 2.0

    • Freshservice MCP Server

      tannertm0
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to connect with Freshservice ITSM for managing tickets, assets, agents, and organizational data through natural language. It provides a comprehensive set of tools for performing CRUD operations on service desk records and searching across the Freshservice platform.
      53
      44 npm
      1
      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

    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 issues

    Resources