Skip to content

Update MCP authentication section: clarify OAuth #305

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

Open
mesumali-dev wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update MCP authentication section: clarify OAuth #305

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
4 changes: 2 additions & 2 deletions ...ndscape/06-gemini-cli-installation-and-basics/06-mcp-servers-and-integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -517,7 +517,7 @@ Think of it like this: When you give your house key to a contractor, you:
Some MCP servers need **authentication** to access protected systems (like your Google Drive or GitHub account).

**When you need OAuth**:
- MCP server accesses your cloud accounts (Google Drive, GitHub)
- MCP server accesses your cloud accounts (Google Drive, etc.)
- API requires login credentials
- Database access is protected

Expand All @@ -534,7 +534,7 @@ Lists servers that need authentication.
```

What happens:
1. Your browser opens to the login page (Google, GitHub, etc.)
1. Your browser opens to the login page (Google, etc.)
2. You log in and approve access
3. Gemini stores the token securely in `~/.gemini/mcp-oauth-tokens.json`
4. Tokens auto-refresh—you never touch them manually
Expand Down