Skip to main content
Glama
WYRE-AI

gorelo-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to gorelo-mcp

No user-submitted related servers found.

    Related Servers

    • CyberQP MCP Server

      WYRE-AI
      F
      license
      A
      quality
      B
      maintenance
      Provides read-only visibility into CyberQP privileged access management data, including customer and account metadata, tenant event logs, and Just-In-Time account status and policies, for AI assistants.
      10
      -

    • Autotask MCP Server

      TICnine
      A
      license
      C
      quality
      C
      maintenance
      Provides AI assistants with direct access to Autotask PSA for MSP operations. Enables natural language interaction for ticket management, time logging, company lookups, project tracking, and billing review through 39 comprehensive tools.
      100
      34 npm
      Apache 2.0

    • infera-mcp-server

      rdndelgado
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query internal business data for insights into customers, revenue, subscriptions, sales, and churn through controlled, read-only MCP tools.
      -

    • xentral-mcp-server

      kochfreiburg
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to access Xentral ERP data — articles, customers, sales orders, invoices, and stock levels — through read-only MCP tools.
      AGPL 3.0

    • Company Data MCP Server

      Sidrahhh
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to company data across PostgreSQL, MongoDB Atlas, and flat files through MCP tools, allowing AI assistants to query and retrieve information via natural language.
      -
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.6/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: tickets, comments, conversations, approvals, clients, contacts, contracts, assets, time entries, users, and configuration lists. The list-versus-get pattern is clearly separated, and even related pairs like conversations/comments and assets/custom-assets are distinguishable by their descriptions.

    Naming Consistency5/5

    All tools share the gorelo_ prefix and follow a consistent verb_noun convention: list_<resource> for collections and get_<resource> for single entities. Config lists use the same list_<resource> pattern, making the entire tool set predictable.

    Tool Count3/5

    At 24 tools, the server sits at the heavy end of the typical range. Each tool is straightforward and purposeful, but the overall surface feels large and is made up almost entirely of list/get read operations that could be seen as repetitive.

    Completeness3/5

    Read coverage is broad across the main GoRelo entities, but the surface is entirely read-only. There is no ticket update, comment creation, or log-time action, even though billing roles and work types reference logging time, which creates notable workflow gaps for agents that need to act on the data.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources