README: add audience framing (who this is for, feature parity acknowledgment) #6

Closed
opened 2026-05-26 01:29:53 +00:00 by coilysiren · 0 comments
Owner

Fresh-eyes feedback from an external reader: the README explains what this is and (now) why-this-deployment-shape, but never names who this is for or honestly acknowledges feature parity with other Lunch Money MCPs.

Adds:

  • Who this is for section: 3 audience bullets (homelab/k3s + Claude-on-phone, multi-consumer endpoint, Helm-over-bespoke-installer preference).
  • Renames Why this runs as a service to Why you might try this one (askers exact framing) and prepends a feature-parity opener so the differentiator framing is honest.

To stay under the 80-line / 4000-char cap, moves the real-world infrastructure values permalink out of README and into docs/deploy.md under a new Real-world example section.

Fresh-eyes feedback from an external reader: the README explains what this is and (now) why-this-deployment-shape, but never names who this is for or honestly acknowledges feature parity with other Lunch Money MCPs. Adds: - Who this is for section: 3 audience bullets (homelab/k3s + Claude-on-phone, multi-consumer endpoint, Helm-over-bespoke-installer preference). - Renames Why this runs as a service to Why you might try this one (askers exact framing) and prepends a feature-parity opener so the differentiator framing is honest. To stay under the 80-line / 4000-char cap, moves the real-world infrastructure values permalink out of README and into docs/deploy.md under a new Real-world example section.
Sign in to join this conversation.
No description provided.