crowntowncompost-mcp

MCP server for the Crown Town Compost customer portal — check your pickups, invoices, and upcoming collection days, skip a service, report a missed pickup, and update your account, all in natural language.

Developed and maintained by AI (Claude Code). Use at your own discretion.

What it talks to

crowntowncompost.com is a marketing site with no customer data. Everything lives at portal.crowntowncompost.com, a Django app (a white-labeled StopSuite hauler platform). This server signs in server-side with your own portal username and password — a normal form login that returns a session cookie — and reads the same pages and JSON endpoints the website uses. No browser extension, no bot-wall workaround, no third-party service in the middle.

Related MCP server: ghl-mcp

Install

npm install -g crowntowncompost-mcp

Then add it to your MCP host with your portal credentials:

{
  "mcpServers": {
    "crowntowncompost": {
      "command": "npx",
      "args": ["-y", "crowntowncompost-mcp"],
      "env": {
        "CROWNTOWN_USERNAME": "you@example.com",
        "CROWNTOWN_PASSWORD": "your-portal-password"
      }
    }
  }
}

Locally you can instead copy .env.example to .env. The server boots without credentials (so a host's install-time probe succeeds); the configuration error surfaces on the first tool call.

Tools

Reads

Writes (all confirm-gated)

Every mutating tool takes confirm. Without confirm: true it makes no network call and returns a dry-run preview of exactly what would be sent. Where a re-read can prove the change stuck (skips, account updates) the tool re-reads and reports verified; where it can't (support messages, missed-pickup reports) it says so rather than claiming success.

Payments are deliberately out of scope — crowntown_list_invoices returns the hosted invoice URL for you to open in a browser.

Hosted connector (claude.ai)

There is also a Cloudflare Worker entry point (src/worker.ts) that makes this server reachable from claude.ai — web, desktop, and mobile — rather than only from a local stdio host. It wraps the same tools behind an OAuth login page where you enter your own portal credentials.

This works because the portal's auth is a plain server-side form login, with nothing that needs a browser or a filesystem. Since the portal issues no refresh token, your credentials are stored encrypted so the connector can sign in again when the session expires.

Deploy is manual — see docs/DEPLOY-CONNECTOR.md.

Without the MCP

The skills/crowntown-portal skill does the same things with curl in a shell — useful in scripts or on a machine where this server isn't installed. It documents the Django CSRF handshake, both JSON endpoints, and every write's field list.

Development

npm install
npm run build
npm test

Tests mock the network — no credentials needed and nothing hits the live portal. tests/server-boot.test.ts spawns the real built artifacts (the npm bin and the bundle, the latter without node_modules) and runs the MCP handshake against them.

npm run worker:test runs the connector suite separately, inside the real Workers runtime — npm test excludes it, since it imports cloudflare:test and can't load under Node.

Endpoint shapes are documented in docs/CROWNTOWN-API.md, including which parts are live-verified and which are not.

License

MIT