Skip to main content
Glama
chrischall

crowntowncompost-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to crowntowncompost-mcp

No user-submitted related servers found.

    Related Servers

    • apps-mcp

      jammaru
      A
      license
      Not graded
      quality
      A
      maintenance
      Unofficial MCP server for the Apps API that enables managing customers, payments, plans, coupons, and Discord integration through natural language.
      66 npm
      2
      MIT

    • ghl-mcp

      craig248
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for GoHighLevel sub-accounts, enabling management of CRM contacts, pipelines, calendars, invoices, and more via natural language.
      -
    • BillingServ MCP by BillingServ

      BillingServ MCPofficial

      BillingServ
      A
      license
      A
      quality
      B
      maintenance
      This is an MCP server for the BillingServ API. Once it's set up, your AI assistant can look up customers, invoices, orders, packages, and reports straight from your BillingServ installation
      3
      68 npm
      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.2/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: schedule, history, upcoming services, account, dashboard, invoices, skips, missed pickups, and support. Even where data overlaps (e.g., dashboard vs. pickup schedule), the descriptions and resource names make the intended purpose clear.

    Naming Consistency4/5

    Tools follow a consistent crowntown_<verb>_<noun> pattern for nearly all actions (get_account, list_invoices, skip_service, etc.). The only noticeable deviation is crowntown_healthcheck, which breaks the verb_noun pattern and would more consistently be check_health or health_check.

    Tool Count5/5

    11 tools is well-scoped for a customer self-service MCP: read operations, account updates, service modifications, reporting, and support are all represented without unnecessary duplication. The count aligns with the domain's natural complexity.

    Completeness4/5

    The tool surface covers the core customer lifecycle: viewing schedule/history/invoices, updating account details, skipping pickups, reporting issues, and contacting support. Minor gaps like subscription changes or payment method management exist, but they are not essential for the apparent primary use case.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources