The Gemini CLI is Google’s open-source command-line agent. It connects to MCP servers defined in its settings and discovers OAuth on a remote server on its own.
Run gemini. The CLI discovers that StackOne uses OAuth and opens your browser. If it does not, authenticate from inside the session:
/mcp auth stackone
Sign in, pick the project and the linked accounts the connector should reach, then Authorize.
Walk through the consent screen
Sign in to StackOne. If you are already signed in to the dashboard you skip straight to the next step.
Select a project. Select the project you would like to associate the connection with.
Select accounts and actions. Existing linked accounts are shown. New accounts can be linked by clicking + Link Account. You can either select the whole account (all actions will be granted) or refine by toggling individual actions.
(Optional) Load tools when needed. On by default, and the toggle that puts the connection into Advanced Tool Search. Leave it on for large action sets. Turn it off to hand the agent every selected action up front.
Authorize. Completes the connection; you can return to your client.
Select a project
Select accounts
Toggle actions
If you see a sentence where the Load tools when needed toggle should be, an admin has already settled it for the whole project. See project settings.
3
Verify
Run /mcp to list connected servers and their tools.
To change which accounts or actions the CLI can reach, re-run the flow with /mcp auth stackone. To revoke it, use Connected Apps in the StackOne dashboard.
Connecting with a session token instead
A session token URL carries its own credential, so it covers the cases OAuth can’t: a shared server, a scheduled job, or anywhere nobody is present to approve a consent screen.Generate one from Connectors, open a connector, then Use in Agent. Pick a linked account, set the expiry (one year by default), and copy the URL:
One URL covers one linked account, and anyone holding it has that access until it expires, so treat it like a password. See Choosing a connection method for the comparison with OAuth.There is no consent screen to set Advanced Tool Search on, so add the tool-mode query parameter instead: