showcase-demo

Showcase demo

The recorded showcase for agent-connector — demo.gif / demo.mp4 in this folder, regenerated by build.sh with vhs.

What it shows

Three actors, each behind a colored bar, then a brand closer:

1. ① MCP DEVELOPER — your whole connector (server + hooks) is a few lines. Define it once, then ship it as your own branded CLI — acme-db install --dry-run renders the big ACME-DB banner (the banner adapts to the brand name) and fans the one definition out into every host's native MCP + hook config — not just plugins.
2. ② THE MCP's USERS — each user installs it with their own CLI's native marketplace, no agent-connector required: live claude / copilot / codex / agy plugin installs of the packaged bundle.
3. ③ Agent-CLI USER — no connector is authored or installed. The framework CLI is useful here as a token-usage utility: agent-connector usage report reads supported agent CLI logs locally and reports whole-conversation totals.

The code-savings numbers (a real, name-withheld MCP we ported) live in the post text, not the video — keeps the clip focused on what it does.

Regenerate it

# from a built checkout (npm run build first), with vhs + ffmpeg installed:
brew install vhs ffmpeg          # ttyd comes with vhs
npm run build                    # produces dist/cli.js + dist/cli/sdk.js
examples/showcase-demo/build.sh  # → examples/showcase-demo/demo.gif + demo.mp4

build.sh is portable — it resolves the repo root, node, and a throwaway mktemp sandbox at runtime (no hardcoded paths). To build against a different checkout: REPO_ROOT=/path/to/agent-connector examples/showcase-demo/build.sh.

It never touches your real config

Every command runs against seeded sandbox HOMEs created under a mktemp directory (auto-removed on exit), so your real ~/.claude, ~/.codex, ~/.cursor, … are left untouched. The scene-2 marketplace installs run against per-actor sandbox HOMEs too.

Notes

• Scene 2 needs the agent CLIs on PATH (claude, copilot, codex, agy). Any that are missing are skipped with a note — the demo still renders, just with fewer live installs.
• Wide terminal on purpose. The tape sets a 1600×860 / 14pt terminal (~170 cols) so the banner renders in its big ANSI-Shadow form; in a narrow terminal the CLI falls back to a one-line ◆ AGENT-CONNECTOR title.
• The banner's gradient palette is chosen at random per run (sunset, lava, fire, amber, peach, berry, ocean, aurora, forest, synthwave), so each recording comes out in a different color.
• The branded acme-db CLI is built with the public SDK exactly like examples/branded-cli/ — createConnectorCli({ packageJson, connector }).