Skip to main content
Glama
WYRE-AI

Alloy Navigator MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Alloy Navigator MCP Server

No user-submitted related servers found.

    Related Servers

    • HaloPSA MCP Server

      Switchboard666
      F
      license
      A
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with HaloPSA data through secure OAuth2 authentication. Supports SQL queries against the HaloPSA database, API endpoint exploration, and direct API calls for comprehensive PSA data analysis and management.
      10
      7 npm
      -

    • autotask

      jamesdeane2
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with AutoTask PSA data, supporting natural language ticket queries, updates, notes, and bulk export.
      MIT

    • AlertOps MCP Server

      WYRE-AI
      F
      license
      A
      quality
      B
      maintenance
      Enables read-only access to AlertOps incident alerting and on-call data, including alerts, users, groups, integrations, and schedules, for AI assistants.
      11
      -

    • Notory MCP server

      ruffymk3
      F
      license
      A
      quality
      C
      maintenance
      Enables an AI assistant to interact with a Notory inventory instance through its REST API, allowing lookups and modifications based on token scope. It automatically discovers available endpoints from the live OpenAPI spec, covering over 200 endpoints beyond just assets.
      5
      -
    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.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear, non-overlapping purpose: listing objects, fetching one object, retrieving its activity log, and looking up reference values. No tool could be confused with another.

    Naming Consistency5/5

    All tool names follow the same alloy_ prefix with a verb_noun pattern: list_objects, get_object, get_object_activities, get_dictionary. The convention is uniform and predictable.

    Tool Count5/5

    Four tools is a well-scoped set that covers the core object-read workflow without unnecessary bloat. Each tool serves a distinct need and fits within the ideal 3-15 range.

    Completeness4/5

    The set covers the main read-only lifecycle: list objects with filters, fetch full object details, get activity history, and resolve dictionary values. Minor gaps exist, such as no way to enumerate available object classes or perform create/update/delete operations, but these seem outside the server's clear query-focused purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources