Skip to main content
Glama
Sign In
crowntowncompost-mcp

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
      B
      maintenance
      Unofficial MCP server for the Apps API that enables managing customers, payments, plans, coupons, and Discord integration through natural language.
      47 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

      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
      75 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 have a clear resource+action identity (list_invoices, skip_service, report_missed_pickup, update_account). The main soft overlap is between crowntown_get_dashboard and crowntown_get_pickup_schedule (both return next service date and address/pickup days), plus list_upcoming_services vs. pickup schedule, but the descriptions explicitly differentiate them (summary vs. empirical arrival window vs. skippable calendar entries).

    Naming Consistency4/5

    All names share a consistent crowntown_ prefix and snake_case verb_noun pattern (list_*, get_*, update_*, skip_*, report_*, contact_*). crowntown_healthcheck is the one deviation, being a bare noun with no verb, but it is unambiguous in context.

    Tool Count5/5

    11 tools is squarely in the well-scoped range, and each one maps to a distinct customer-portal need: account read/write, dashboard, schedule, upcoming services, skip, history, missed pickup, invoices, support, and diagnostics. Nothing appears redundant or filler.

    Completeness4/5

    The lifecycle is well covered: view account/dashboard/schedule/history, act on services (skip, report missed), manage account, list invoices, and contact support. Minor gaps exist — no subscription management (pause/cancel/change plan) and no invoice payment action beyond following the Stripe link, but these are plausibly out of scope for this MCP.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources