Crowntowncompost MCP vs Hindsight
A side-by-side look at the Crowntowncompost MCP and Hindsight MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Crowntowncompost MCP for support & service management work as a local process; choose Hindsight for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Crowntowncompost MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
CROWNTOWN_USERNAME, CROWNTOWN_PASSWORD, CROWNTOWN_SESSION_COOKIE, MCP_CONFIRM_MODE, MCP_CONFIRM_ELICITATION, MCP_CONFIRM_TTL_SECONDS, MCP_CONFIRM_SECRET. - You want tools like
crowntown_healthcheck, crowntown_get_dashboard, crowntown_get_account.
Choose Hindsight when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
HINDSIGHT_API_LLM_API_KEY, HINDSIGHT_API_LLM_PROVIDER, HINDSIGHT_DB_PASSWORD.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Knowledge & Memory |
| Quality signal | 63/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | API key required |
| Pricing | Free | Free |
| Required env vars | CROWNTOWN_USERNAMECROWNTOWN_PASSWORDCROWNTOWN_SESSION_COOKIEMCP_CONFIRM_MODEMCP_CONFIRM_ELICITATIONMCP_CONFIRM_TTL_SECONDSMCP_CONFIRM_SECRET | HINDSIGHT_API_LLM_API_KEYHINDSIGHT_API_LLM_PROVIDERHINDSIGHT_DB_PASSWORD |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 53,599 |
| Directory activity | 1 views 0 installs 0 upvotes | 15 views 0 installs 0 upvotes |
| Tools | 11 | Not listed |
| Full listing | View Crowntowncompost MCP | View Hindsight |
Tools & capabilities
Crowntowncompost MCP tools 11
crowntown_healthcheckConfirm 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_dashboardGet 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_accountGet 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_accountUpdate 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_historyList 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_servicesList 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. Read-only — use crowntown_skip_service to actually skip/unskip.crowntown_get_pickup_scheduleGet 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_serviceSkip (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_invoicesList your Crown Town Compost invoices — number, date, amount, status, whether payable, and links (Stripe PDF / receipt / hosted invoice page). Paginated. Read-only.crowntown_report_missed_pickupReport 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_supportSend 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).
Hindsight tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Crowntowncompost MCP
{
"mcpServers": {
"crowntowncompost-mcp": {
"command": "npx",
"args": [
"-y",
"crowntowncompost-mcp"
],
"env": {
"CROWNTOWN_USERNAME": "YOUR_CROWNTOWN_USERNAME_HERE",
"CROWNTOWN_PASSWORD": "YOUR_CROWNTOWN_PASSWORD_HERE",
"CROWNTOWN_SESSION_COOKIE": "YOUR_CROWNTOWN_SESSION_COOKIE_HERE",
"MCP_CONFIRM_MODE": "YOUR_MCP_CONFIRM_MODE_HERE",
"MCP_CONFIRM_ELICITATION": "YOUR_MCP_CONFIRM_ELICITATION_HERE",
"MCP_CONFIRM_TTL_SECONDS": "YOUR_MCP_CONFIRM_TTL_SECONDS_HERE",
"MCP_CONFIRM_SECRET": "YOUR_MCP_CONFIRM_SECRET_HERE"
}
}
}
}
Hindsight
{
"mcpServers": {
"vectorize-io-hindsight": {
"command": "npx",
"args": [
"-y",
"@vectorize-io/hindsight-coding-agents"
],
"env": {
"HINDSIGHT_API_LLM_API_KEY": "YOUR_HINDSIGHT_API_LLM_API_KEY_HERE",
"HINDSIGHT_API_LLM_PROVIDER": "YOUR_HINDSIGHT_API_LLM_PROVIDER_HERE",
"HINDSIGHT_DB_PASSWORD": "YOUR_HINDSIGHT_DB_PASSWORD_HERE"
}
}
}
}
Frequently asked questions
Crowntowncompost MCP is categorized under Support & Service Management and uses a local stdio subprocess. Hindsight belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Crowntowncompost MCP for support & service management work and Hindsight for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Crowntowncompost MCP is listed as free. Auth: other. Hindsight is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add crowntowncompost-mcp and vectorize-io-hindsight as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Crowntowncompost MCP has a quality signal of 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Hindsight has 57/100 (Good) with 15 views, 0 installs and 53,599 GitHub stars.