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.
      9 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
      C
      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
      43 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

    Disambiguation4/5

    Most tools target clearly distinct resources/actions (account, invoices, service history, upcoming services, skip). There is mild overlap among crowntown_get_dashboard, crowntown_get_pickup_schedule, and crowntown_list_upcoming_services, since the dashboard already surfaces next service date and pickup days, but the descriptions differentiate scope (summary vs. per-address arrival window vs. calendar with skip IDs) well enough to guide selection.

    Naming Consistency4/5

    All tools use the crowntown_ prefix and a predictable verb_noun pattern (list_*, get_*, update_account, skip_service, report_missed_pickup, contact_support). The only deviation is crowntown_healthcheck, which is a bare noun with no verb, a minor inconsistency in an otherwise uniform scheme.

    Tool Count5/5

    Eleven tools is well-scoped for a single-account compost service portal. Each tool maps to a distinct user need (auth check, dashboard, account read/update, invoices, history, schedule, upcoming, skip, report missed pickup, support), with no filler.

    Completeness4/5

    The lifecycle is largely covered: profile read/update, invoice listing, service history, upcoming schedule, skip/unskip, missed-pickup reporting, and support contact. Minor gaps remain — invoices are read-only (no pay action despite 'payable' status) and there is no subscription management (pause/cancel) or invoice detail view — but these are workable around via links.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources