crowntowncompost-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CROWNTOWN_PASSWORD | Yes | Your portal password | |
| CROWNTOWN_USERNAME | Yes | Your portal username/email |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crowntown_healthcheckA | Confirm credentials are configured, log in to the Crown Town Compost portal, fetch the dashboard, and report {authenticated, account_status, service_addresses}. On failure, error.kind says which hop broke: no_credential (nothing configured), credential_rejected (the portal refused the username/password), session_expired (a supplied session cookie is no longer honoured), edge_blocked (a CDN/WAF refused the request before the portal saw it, so the credentials were never judged), timeout, transport or http. Read-only; never returns the credentials. |
| crowntown_get_dashboardA | Get your Crown Town Compost dashboard: account status, active subscription (plan, price, renewal date), next service date, service address(es) and their pickup day(s), and your composting environmental impact (lbs diverted, seedlings, miles offset, gallons of gas). Read-only. |
| crowntown_get_accountA | Get your account contact details (first name, last name, phone) and notification preferences (email reminders, service notifications). Read-only — use crowntown_update_account to change them. |
| crowntown_update_accountA | Update your contact details and/or notification preferences. Reads your current account form, changes ONLY the field(s) you specify, and re-saves the rest verbatim. The preview shows the current values and the resulting state. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). |
| crowntown_list_service_historyA | List past collection stops for your account — date, status (Success/Missing/Empty/Inaccessible/Unacceptable), collection time, weight, and services rendered. Paginated and filterable by status. Read-only. |
| crowntown_list_upcoming_servicesA | List upcoming scheduled collection days from the service calendar, each with the identifiers needed to skip it (rid, clid), the service date, and whether it is currently scheduled or already skipped. view "brief" answers one line per day instead: "Compost pickup — — scheduled|skipped". Read-only — use crowntown_skip_service to actually skip/unskip. |
| crowntown_get_pickup_scheduleA | Get the pickup schedule for each service address: pickup day(s), next service date, the official set-out-by time, and an observed arrival-time window (earliest/latest/typical and whether it is consistent or varies) derived from the recorded collection times in your service history. Crown Town Compost publishes no guaranteed arrival window, so the observed window is empirical. Read-only. |
| crowntown_skip_serviceA | Skip (or un-skip) an upcoming collection day. Pass the rid + clid from crowntown_list_upcoming_services. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). |
| crowntown_list_invoicesA | List your Crown Town Compost invoices — number, date, amount, status, whether payable, and links (Stripe PDF / receipt / hosted invoice page). Paginated. view "brief" answers one line per invoice instead ("Invoice — — ", inside the untrusted-data envelope) and lists only the payable invoices unless payable_only is false. Read-only. |
| crowntown_report_missed_pickupA | Report that a scheduled collection was missed. This notifies Crown Town Compost staff. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). |
| crowntown_contact_supportA | Send a message to Crown Town Compost customer support. The reply-to email and phone default to the ones the support form pre-fills from your account, and the preview shows the exact values that will be sent. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
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).
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.
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.
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.