Repository navigation
v2.5.0
Browser authorization, driven through MCP
Re-authorizing a containerized pCloud server is now a tool call instead of a runbook. Nothing is copied by hand.
Added
pcloud_auth_status— whether the server holds a usable credential, and if not, what is missing. Verifies a stored token against pCloud rather than assuming its presence means it works.pcloud_auth_start— returns the URL to open. The user approves in a browser; pCloud redirects back and the token is stored server-side.pcloud_auth_result— what the last redirect did, for when status alone cannot tell whether one ever arrived.- A
/callbackroute on the server's own HTTP port via FastMCP'scustom_route. This is what removes the copy-and-paste step: the exchange happens before the page renders. No second listener, no extra port. PCLOUD_OAUTH_REDIRECT_URIis now read by the server as well as the CLI.
Security
- The CSRF
stateoutlives the tool call in a single-slot holder: expires after 10 minutes, single-use, and superseded rather than duplicated when a second authorization starts. Two outstanding valid states would be two ways in. - A redirect's reported region is honoured only when it is a known pCloud endpoint, so it cannot aim the client at an arbitrary host.
Tool count is now 18.
Full Changelog: v2.4.0...v2.5.0