Problem
The README promises "Get Started in 60 Seconds" and the setup works, but the gap between setup complete and first successful MCP tool call is the real drop-off point. A first-time user lands on an empty dashboard with no working example, has to read the REST connector doc, decide which API to try, configure auth, import a spec, generate an MCP key, and wire it into their AI client — easily 5–10 minutes of friction even when everything goes right.
PR #178 mitigates this with a documented 3-minute quickstart (VIES VAT example), but documentation can only do so much. The high-impact fix is shipping a working demo out of the box.
Proposal
On first boot (or as an opt-in step in `setup.sh`), pre-load one or two zero-auth public-API connectors so the user sees working tools immediately. Good candidates because they need no credentials:
- VIES VAT validation (EU Commission, no key) — instant "validate this VAT number" demo
- OpenPLZ Germany (postal codes, no key) — visual "look up a German address" demo
- DPD Germany Tracking (public, no key) — "track this parcel" demo
The connectors already exist as JSON adapters in `packages/backend/src/adapters/`. The change is a backend seed step that installs one of them on the first Admin registration, plus a UI nudge: "Try this demo tool →".
Why this matters
Star-to-active-user conversion on Show HN / GitHub launches is dominated by the first 5 minutes of UX. An empty dashboard reads as "product not ready"; a working demo connector reads as "this thing actually does what the README says".
Out of scope for this issue
- Auto-registering an Admin account (security concern — first-user-wins is intentional)
- Pre-seeding credentials for SaaS connectors (DHL, Personio, etc.) that require API keys
Related
Problem
The README promises "Get Started in 60 Seconds" and the setup works, but the gap between setup complete and first successful MCP tool call is the real drop-off point. A first-time user lands on an empty dashboard with no working example, has to read the REST connector doc, decide which API to try, configure auth, import a spec, generate an MCP key, and wire it into their AI client — easily 5–10 minutes of friction even when everything goes right.
PR #178 mitigates this with a documented 3-minute quickstart (VIES VAT example), but documentation can only do so much. The high-impact fix is shipping a working demo out of the box.
Proposal
On first boot (or as an opt-in step in `setup.sh`), pre-load one or two zero-auth public-API connectors so the user sees working tools immediately. Good candidates because they need no credentials:
The connectors already exist as JSON adapters in `packages/backend/src/adapters/`. The change is a backend seed step that installs one of them on the first Admin registration, plus a UI nudge: "Try this demo tool →".
Why this matters
Star-to-active-user conversion on Show HN / GitHub launches is dominated by the first 5 minutes of UX. An empty dashboard reads as "product not ready"; a working demo connector reads as "this thing actually does what the README says".
Out of scope for this issue
Related