Skip to main content
Glama
WYRE-AI

sherweb-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to sherweb-mcp

No user-submitted related servers found.

    Related Servers

    • oitvoip-mcp

      MSPbotsAI
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Oitvoip (NetSapiens) that exposes domain, reseller, device, subscriber, and CDR tools via the ns-api.
      -

    • chargebee-mcp

      MSPbotsAI
      A
      license
      A
      quality
      B
      maintenance
      MCP server wrapping the Chargebee REST API to manage customers, subscriptions, invoices, and transactions.
      10
      Apache 2.0

    • SuperOps MCP Server

      Matt-Beyond-Tech
      A
      license
      A
      quality
      C
      maintenance
      MCP server for interacting with the SuperOps.ai PSA/RMM platform, providing tools for managing clients, tickets, assets, and technicians via GraphQL API.
      21
      Apache 2.0

    • saas-alerts-mcp

      WYRE-AI
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Kaseya SaaS Alerts, providing tools to query security events, manage customers/users, handle devices, billing, reports, and partner settings via the External Partner API.
      -
    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

    A3.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource or action: list/get for customers and subscriptions, payable vs receivable for billing direction, and dedicated tools for charge details, quantity changes, amendment status, catalog products, navigation, and status. There is no meaningful overlap that would cause an agent to select the wrong tool.

    Naming Consistency4/5

    All tools share the sherweb_ snake_case prefix and mostly group by domain, but the pattern varies between domain_action (customers_list, subscriptions_get) and domain_noun_phrase (billing_payable_charges, customers_accounts_receivable), with two meta tools (navigate, status) outside the pattern. This is readable but not perfectly uniform.

    Tool Count5/5

    12 tools is well within the ideal range and appropriately scoped for a Sherweb billing/customer/subscription server. Each domain has a focused set of tools with no obvious bloat or redundancy.

    Completeness3/5

    The set covers read operations and subscription quantity changes well, but there are notable gaps: no customer create/update/delete and no subscription purchase/cancel tools. Listing sellable products without a way to actually create a subscription is a significant missing workflow.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources