Skip to content

docs(mcp): correct mcp --help to document first-run browser login (v1.2.2)#81

Merged
santiagomed merged 1 commit into
mainfrom
fix/mcp-help-browser-text
Jun 29, 2026
Merged

docs(mcp): correct mcp --help to document first-run browser login (v1.2.2)#81
santiagomed merged 1 commit into
mainfrom
fix/mcp-help-browser-text

Conversation

@santiagomed

Copy link
Copy Markdown
Collaborator

What

Fixes the xurl mcp command's --help (Long) text, which shipped in v1.2.1 still claiming:

The bridge never opens a browser itself; if no token exists it exits with that instruction.

That contradicts the v1.2.1 behavior (Option A): bootstrap() now opens the browser for a first-run OAuth2 login when no token is cached. The stale help could mislead no-install (npx … mcp) users into thinking they must run xurl auth oauth2 first.

Change

  • cli/mcp.go: rewrite the Long help to document the first-run browser login and point remote/headless hosts at xurl auth oauth2 [--app NAME] --headless.
  • CHANGELOG.md: add a v1.2.2 entry.

Docs-only; no behavior change.

Verification

  • go build ./... && go vet ./... && go test ./... all green.
  • Validated the fresh-user (no install, no ~/.xurl) path end-to-end: npx @xdevplatform/xurl@1.2.1 mcp in an isolated HOME with creds in env → bridge reported no valid OAuth2 token; opening the browser, completed login, then handshook and listed all 27 tools.

The v1.2.1 'mcp' help text still claimed the bridge 'never opens a
browser itself; if no token exists it exits with that instruction',
but v1.2.1 changed bootstrap() to open the browser for a first-run
OAuth2 login when no token is cached. Update the help to describe that
behavior and point remote/headless hosts at 'xurl auth oauth2 --headless'.

Docs-only; no behavior change. Add a v1.2.2 CHANGELOG entry.
@santiagomed santiagomed merged commit bfb0f36 into main Jun 29, 2026
2 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.

2 participants