Skip to main content
Glama
myst3k

wasabi-wacm-connect-mcp

by myst3k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to wasabi-wacm-connect-mcp

No user-submitted related servers found.

    Related Servers

    • WIBI MCP Gateway

      roalejandro
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing WIBI's API v2 as tools, supporting OAuth 2.1 for production (Claude web/desktop) and stdio for local dev, enabling natural-language queries about campaigns, products, clients, reports, broadcasts, and subscriptions with per-commerce isolation and admin scope switching.
      -

    • clio-mcp

      ToddHebebrand
      F
      license
      B
      quality
      C
      maintenance
      A standalone MCP server that enables Claude Desktop to manage Clio legal practice matters, documents, billing, and more via ~46 tools, with secure OAuth and audit logging.
      46
      -

    • trimble-connect-mcp

      nhantruong96
      A
      license
      A
      quality
      C
      maintenance
      A local MCP server giving Claude access to Trimble Connect, with 40 tools for projects, folder trees, files, versions, members, groups, and permissions via the Core API v2.
      40
      MIT

    • vturb-mcp

      hiperbold
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the vTurb Analytics API that exposes 15 tools to query real-time and historical video analytics directly from Claude, with built-in rate limiting and smart player detection.
      1
      -
    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 18 tools

    Disambiguation4/5

    Most tools are clearly separated by resource type (channel/control/sub accounts, members, invoices, usage), and descriptions identify their scope. The main confusion risk is between the two usage families (Sub-Account vs Control Account) and between members and sub-accounts, but naming and descriptions are sufficient to avoid habitual mis-selection.

    Naming Consistency4/5

    The set follows a consistent list_<plural>/get_<singular> pattern for most resources. Minor deviations exist: get_storage_amounts is a list-style getter, and the bucket/standalone account areas have list tools without corresponding get tools.

    Tool Count4/5

    18 tools is slightly above the typical 3-15 range, but the count is justified by distinct WACM entities (accounts, members, usage, invoices, buckets, storage options). There is little redundancy, so the extra breadth is reasonable rather than bloated.

    Completeness4/5

    For a read-only WACM data-access surface, the set covers account hierarchy, members, usage, invoices, and bucket utilization well. Notable gaps are the absence of get_standalone_account, no individual bucket retrieval, and no write operations, but agents can work around these with the provided list tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources