How it works
When you use the CLI or MCP server for the first time, you’ll be redirected to your PickFu account to authorize the app. Once you approve, the tool handles tokens automatically.CLI
OAuth (recommended)
Run the login command to authenticate:--headless to print the URL instead of opening a browser:
API key
For CI pipelines, scripts, and automation, you can authenticate with an API key instead of OAuth:--token flag > PICKFU_API_KEY environment variable > stored OAuth token.
Check status
MCP server
The MCP server authenticates through your MCP client. When you first connect, your client prompts you to sign in to your PickFu account via OAuth. For example, Cursor prompts for WorkOS login automatically — no manual token setup required. See the MCP server guide for client-specific setup instructions.Token management
Both tools handle token storage and refresh automatically. You don’t need to manage tokens manually.- CLI — Tokens are stored in
~/.config/pickfu/config.jsonand refreshed when they expire. Runpickfu auth loginagain if you need to re-authenticate. - MCP server — Your MCP client manages the OAuth session. Re-authorize through your client if needed.
