Skip to content

feat(web): rebuild the share page as a per-client connect storyboard - #2

Merged
daretodave merged 2 commits into
mainfrom
step-04a-share-storyboard
Jul 1, 2026
Merged

feat(web): rebuild the share page as a per-client connect storyboard#2
daretodave merged 2 commits into
mainfrom
step-04a-share-storyboard

Conversation

@daretodave

Copy link
Copy Markdown
Owner

Rebuilds the /<slug> share page's instruction component from the approved design mock: a per-client connect storyboard that walks the visitor Add → Authenticate → connected, drawn to resemble their client's surface.

What changed

  • Per-client config fidelity — each http client gets the config shape it actually accepts: VS Code's top-level servers + transport type, Cline's streamableHttp, Zed's context_servers, Windsurf's serverUrl, the generic url + type. stdio walks clone → build → point-at-it with the per-client run key.
  • The authenticate beat — the often-missed OAuth step after Add: an explicit Connect/Authenticate control, or a browser that opens on its own (with a trust dialog where it applies). Every flow ends on a connected cap, never on "Added".
  • New scenes (auth / browser / modal / connected-cap / beat-kind); terminal gains status tags + a glow row for the /mcp beat.
  • storyboard.tsx + beat.tsx replace build-steps.tsx + step-card.
  • One-click stays remote-only and honest (a stdio deep-link can't clone or build); the banner is keyed per client so a stale "Sent to X" can't survive a switch.
  • The static-token path is footnoted on the config-file beats (Zed, Generic).
  • serverName slugifies so a punctuated title can't emit a leading-dash arg that breaks claude mcp add.
  • The Claude row is relabelled "Claude".

Verification

Full local gate green: typecheck · lint · format · co-located-test law · agnostic-seam · 244 unit tests with coverage · build + bundle-budget (186.9 / 200 kB gzip). An adversarial review (one fidelity pass per client + dimension reviewers, each finding re-verified) surfaced 10 issues — all fixed in this branch.

Also carries an earlier readme update commit already present on the branch.

Replace the one-step-per-client matrix with a beat storyboard that walks each
client Add -> Authenticate -> connected, drawn to resemble that client's surface.
Every http client gets the config shape it actually accepts -- VS Code's
top-level `servers` with a transport `type`, Cline's `streamableHttp`, Zed's
`context_servers`, Windsurf's `serverUrl`, the generic `url` + `type` -- plus the
authenticate beat that follows Add: an explicit Connect/Authenticate control, or
a browser that opens on its own, each ending on a connected cap, never on
"Added". stdio walks clone -> build -> point-at-it with the per-client run key.

- scenes: auth / browser / modal / connected-cap / beat-kind; terminal gains
  status tags + a glow row for the /mcp authenticate beat
- storyboard.tsx + beat.tsx replace build-steps.tsx + step-card
- one-click is remote-only and honest (a stdio deep-link can't clone or build);
  key the banner per client so a stale "Sent to X" can't survive a switch
- footnote the static-token path on the config-file beats (Zed, Generic)
- slugify the server key so a punctuated title can't emit a leading-dash arg
- relabel the Claude row "Claude"
@daretodave
daretodave merged commit c5567b9 into main Jul 1, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant