Skip to content

feat: faster first run, real demo, MCP directory metadata - #3

Merged
pasichDev merged 3 commits into
mainfrom
docs/onboarding
Sep 22, 2026
Merged

pasichDev merged 3 commits into
mainfrom
docs/onboarding

Conversation

@pasichDev

Copy link
Copy Markdown
Owner

What

  • setup ends with the hosts it configured, one thing to try, and the dashboard URL — instead of env snippets and a "start the server" step that does not exist.
  • README: quick start moved under the tagline; one command; a real recorded demo GIF.
  • demo-setup.sh: seeded workspaces now match what agents resolve (gitlab.com/acme/backend, not acme/backend).
  • Directory metadata: glama.json, 400×400 logo, llms-install.md, MCP Bundle manifest + pack script; plugin marketplace version 2.0.0 → 3.0.0.

Testing

  • npm test: 512/512 pass (two new tests for the closing message).
  • Fresh HOME: setup finishes in ~17 s and prints the new closing screen; first todo_add ~2 s, dashboard auto-starts.
  • mcpb/pack.sh builds docket-3.0.0.mcpb (validated); todo_add works through the unpacked bundle.

The last screen of `setup` is the only part of its output most people read, and
it ended on env snippets for hosts setup had just configured itself, followed by
"Start the server with: npx -y @pasichdev/docket" — a step that does not exist
(the first agent to connect starts everything), and, run inside a checkout of
this repo, the one invocation that fails.

It now names the hosts it actually configured, gives the one thing to try
("add a todo: try docket") and the dashboard URL. The manual snippet for other
hosts is a whole entry — command, args and env — rather than an env block with
nothing to attach it to.
The README opened with two paragraphs of why and four screenshots before the
install command, and the command block then told people to add the server by
hand after a `setup` that had already done it. Quick start now sits under the
tagline: one command, what it does, what to try.

demo.gif is a real run, not a staged one: two different coding CLIs, headless,
in two projects, each add a todo over MCP, and both land on the dashboard filed
under their own project.

demo-setup.sh seeded items under `acme/backend` while agents file them under
`gitlab.com/acme/backend`, so the demo showed one project as two.
- glama.json, so the Glama listing can be claimed — it still shows the
  pre-rename "todo-mcp" at a pre-3.0 version.
- A 400×400 logo (the site's favicon), which Cline's marketplace requires.
- llms-install.md: install steps an agent can follow unaided.
- mcpb/: manifest and pack script for a one-click MCP Bundle (desktop hosts,
  Smithery). It packs the published npm tarball rather than the working tree,
  so a bundle is exactly the release its version names.
- The plugin marketplace still declared 2.0.0.
@pasichDev
pasichDev merged commit 018164d into main Sep 22, 2026
7 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