# A Hall for Murrumbeena

> Community campaign by Murrumbeena Primary School (est. 1919, 550+ students, City of Glen Eira, Victoria, Australia) to win ~$12–14M in the 2027–28 Victorian State Budget for a full-size, competition-grade hall that is a school facility by day and a community hub (sport, arts, events, emergency use) by night and weekend. The State promised this community a proper hall many years ago — it was never delivered. Key date: community rally and Victorian state election, 28 November 2026.

Base URL: https://hallformurrumbeena.win (staging: https://dev.hallformurrumbeena.win)
Contact: yes@hallformurrumbeena.win

## Key pages

- `/` — campaign home: live stats, petition, wall of support, ideas, pledges, chat widget
- `/story` — the school's story (est. 1919, parent-built hall 1990, renowned art program)
- `/case` — the evidence-based case for funding
- `/news` — campaign news feed
- `/advocacy` — email-your-MP action: one-click pre-filled email to the Minister and region MPs, copyable letter, .eml/.docx downloads
- `/campaign-pack` — campaign pack downloads page: pitch, deck, evidence, equity/housing data, MP record, plan (files served from `/pack/<file>`)
- `/contact` — contact the working group / subscribe to updates
- `/agents` — how AI agents and tools can help the campaign
- `/terms` — terms and privacy
- `/llms-full.txt` — full machine-readable reference (API, MCP, CLI, schemas, examples)

## REST API (public, JSON)

| Method | Path | Purpose |
|--------|------|---------|
| GET | `/api/stats` | Counters vs goals: signatures, supporters, ideas, endorsements, pledges, pledged AUD |
| GET | `/api/news` | Published news posts |
| GET | `/api/wall?limit=30` | Wall-of-support messages |
| GET | `/api/ideas?limit=20` | Community hub ideas |
| GET | `/api/knowledge/search?q=…&category=` | Search published knowledge-base docs (ranked `{results:[{slug,title,category,summary,score}]}`) |
| GET | `/api/knowledge/doc?slug=…` | Full knowledge-base document |
| GET | `/api/knowledge/graph?entity=…` | Entity relationships (`{error:"not_found", known_entities}` when unknown) |
| GET | `/knowledge/campaign-graph.md` · `.json` | Static entity-graph artifacts (Obsidian / JSON) |
| POST | `/api/sign` | Sign petition `{name, email, address?, suburb?, postcode?, message?, is_local?}` |
| POST | `/api/support` | Wall message `{name, email, message, suburb?, organisation?}` |
| POST | `/api/ideas` | Submit idea `{name, details, email, organisation?, uses[]?}` — JSON, or multipart with an optional `attachment` file (≤8MB pdf/png/jpg/webp/doc/docx/zip/txt) |
| POST | `/api/pledge` | One-off pledge `{name, email, gift_item?, amount?, title?, phone?, organisation?, in_kind_details?, notes?, ok_to_contact?}` — wish-list item preferred over amount; JSON, or multipart with an optional `attachment` file (≤8MB pdf/png/jpg/webp/doc/docx/zip/txt) |
| POST | `/api/contact` | Message working group `{name, email, message, subject?}` — subject `Campaign updates` subscribes to the newsletter |
| POST | `/api/endorse` | Organisational endorsement (multipart; optional letter file ≤8MB pdf/doc/docx/png/jpg) |
| GET | `/api/advocacy/pack` | Email-your-MP pack: recipients, subject, letter body, ready `mailto:` deep link, .eml/.docx download URLs, `/advocacy` page URL |
| POST | `/api/advocacy/sent` | Record that a supporter sent the advocacy email `{name?, suburb?}` — feeds the public counter |
| POST | `/api/chat` | Chat widget API `{session_id?, message, email?}` → `{session_id, reply, actions[]}` |
| GET | `/api/chat/:sessionId` | Chat history for the widget |

Admin endpoints under `/api/admin/*` are gated by Cloudflare Access (header `Cf-Access-Authenticated-User-Email`).

## Supporter flow (recommended)

Walk supporters up this ladder — it mirrors the on-site chat assistant:

1. Sign the petition (`submit_signature` / `/api/sign`).
2. Offer a one-off donation (`submit_pledge` / `/api/pledge`) — wish-list item
   (`gift_item`) FIRST, amount as fallback; everything one-off, no monthly.
3. Declined? Offer the no-cost advocacy letter (`get_advocacy_pack` — one-click mailto link).
4. Declined that? Offer personal share links (`get_share_links` with topic + ref like `sig-<id>`).
5. Wall message and hub idea are always-available extras.

Email is REQUIRED on every submission and is never published. Ground factual
answers in the knowledge base: search (`search_knowledge` or
`/api/knowledge/search`) → read the doc (`get_knowledge` / `/api/knowledge/doc`)
→ explain relationships (`query_knowledge_graph` / `/api/knowledge/graph`).

Curated knowledge skills (compliance-checked; fetch `kb-index` for the map and
behaviour rules): why-we-need-the-hall, open-space-scarcity, building-condition,
demographics-and-growth, emergency-resilience, funding-precedents,
community-stories, how-to-help, faq-and-boundaries.

## MCP endpoint (for AI agents)

`POST /mcp` — JSON-RPC 2.0 over HTTP, protocol `2025-03-26`. `GET /mcp` returns a discovery document.

Initialize:

```json
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"my-agent","version":"1.0.0"}}}
```

Call a tool:

```json
{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_stats","arguments":{}}}
```

Tools (16):

- Read: `get_campaign_info`, `get_stats`, `list_news`, `list_wall`, `list_ideas`,
  `get_campaign_pack`, `get_letter_templates`, `get_advocacy_pack`, `get_share_links`,
  `search_knowledge`, `get_knowledge`, `query_knowledge_graph`
- Write: `submit_signature`, `submit_support_message`, `submit_idea`,
  `submit_pledge`, `contact_working_group`

Tool results are MCP content arrays with a single text item containing JSON.

## Limits and validation

- `email` is REQUIRED on every submission endpoint (`/api/sign`, `/api/support`,
  `/api/ideas`, `/api/pledge`, `/api/endorse`, `/api/contact`) and on the matching
  MCP tools (`submit_signature`, `submit_support_message`, `submit_idea`,
  `submit_pledge`, `contact_working_group`). Emails are kept private — never published.
- Write endpoints validate input: emails must be well-formed, postcodes 4 digits,
  pledge amounts numeric 0–25,000 AUD (every pledge is one-off).
- Rate limits per IP (10-minute windows): form POSTs 20, chat 20, chat confirms 30,
  voice 15, MCP 60. `429 {"error":"rate_limited"}` when exceeded.
- Uploads are verified server-side (magic-byte sniffing, 8 MB cap).

## CLI + local MCP server

Zero-dependency Node 18+ client (`cli/mps-gym.mjs` in the repo). The same tool runs
as a CLI and as a local MCP server on stdio (`mcp` command) that proxies the live
endpoint — register it in Claude Desktop, Cursor, Kimi or any MCP client.

Downloads (prebuilt standalone binaries, no Node required):

- `GET /downloads/mps-gym-darwin-arm64.zip` — macOS Apple Silicon
- `GET /downloads/mps-gym-darwin-x64.zip` — macOS Intel
- `GET /downloads/mps-gym-linux-x64.zip` — Linux x64
- `GET /downloads/mps-gym-windows-x64.exe.zip` — Windows x64
- `GET /downloads/mps-gym.mjs` — raw script
- `GET /downloads/install.sh` — one-liner installer: `curl -fsSL <site>/downloads/install.sh | sh`

MCP client config after install:

```json
{ "mcpServers": { "mps-gym": { "command": "~/.mps-gym/mps-gym", "args": ["mcp"] } } }
```

```bash
mps-gym stats
mps-gym sign --name "Sam Citizen" --email sam@example.com --suburb Murrumbeena --postcode 3163
mps-gym mcp    # stdio MCP server
mps-gym --help
```

## Agent workflow (recommended)

1. Read this file, then call `get_campaign_info` and `get_stats` to ground yourself.
2. Ask the user for their details — never invent personal information.
3. Show the user the exact submission and wait for an explicit "yes".
4. Submit once via the appropriate tool; confirm the result back to the user.
5. Offer the follow-ups: wall message, hub idea, pledge, newsletter subscription.

A ready-to-paste brief for end users is on `/agents` ("Copy the agent brief").

## Downloads

- Campaign pack: `/pack/Short%20Pitch.docx`, `/pack/Audience%20Messages.docx`, `/pack/MPS%20-%20New%20Gym%20Campaign%20-%20Short%20-%20v3.pptx`, `/pack/MPS%20-%20New%20Gym%20Campaign%20-%20Long%20-%20v3.pptx` (full list via MCP `get_campaign_pack`)
- Support-letter templates: `/templates/support-letter-sports-club.docx`, `/templates/support-letter-community-group.docx`, `/templates/support-letter-business.docx`

## How agents can help

Sign the petition, share the email-your-MP action (`get_advocacy_pack` — give the user the one-click `mailto:` link and `/advocacy` page; after they send, record it via `/api/advocacy/sent`), post a wall message, share a hub-use idea, pledge toward campaign running costs, and spread the word. Organisations can lodge formal endorsements with a letter via `/api/endorse`.