Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
santiagomed merged 1 commit into from
Jun 29, 2026
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,12 @@

All user-visible bugs and enhancements should be recorded here.

## v1.2.2 - 2026-06-29

### Fixed

- [2026-06-29] `mcp --help` no longer contradicts the bridge's behavior. The v1.2.1 help text still said the bridge "never opens a browser itself; if no token exists it exits with that instruction", but v1.2.1 changed the bridge to open the browser for a first-run OAuth2 login when no token is cached. The help now documents that, and points remote/headless hosts to `xurl auth oauth2 [--app NAME] --headless`.

## v1.2.1 - 2026-06-29

### Changed
Expand Down
9 changes: 5 additions & 4 deletions cli/mcp.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -736,10 +736,11 @@ session id is maintained across requests.

The access token is resolved exactly like 'xurl token': an existing token is
refreshed automatically as it expires (including a forced refresh on a 401).
Authenticate once before starting the bridge with 'xurl auth oauth2 [--app NAME]'
(add --headless on a remote/headless machine). The bridge never opens a browser
itself; if no token exists it exits with that instruction. All diagnostics go to
stderr so stdout stays a clean JSON-RPC channel.
If no token is cached, the bridge opens the browser for an interactive OAuth2
login on startup and blocks until it completes, so a first run needs no separate
'xurl auth oauth2' step. On a remote/headless machine without a browser,
authenticate first with 'xurl auth oauth2 [--app NAME] --headless'. All
diagnostics go to stderr so stdout stays a clean JSON-RPC channel.

If URL is omitted it defaults to ` + defaultMCPURL + `.

Expand Down
Loading