MCP in Gemini

~14 min · gemini, mcp, integrations

Level 0🌱 Novice

0 XP0/70 lessons0/11 achievements

0/120 XP to next level120 XP to go0% complete

Same protocol, Gemini's perspective

Gemini implements MCP just like Claude Code and Codex. gemini mcp add registers servers; transports are stdio / HTTP; scopes are user / project. The catalog of available servers (Sentry, GitHub, Notion, Slack, Postgres, etc.) is identical — that's the whole point of the standard.

Code

Add three servers + use them·bash

# HTTP servers
gemini mcp add --transport http github  https://api.githubcopilot.com/mcp/
gemini mcp add --transport http sentry  https://mcp.sentry.dev/mcp

# Local stdio server
gemini mcp add --transport stdio db -- npx -y @bytebase/dbhub \
  --dsn "postgresql://readonly:pw@localhost:5432/analytics"

# OAuth from inside the REPL
gemini
> /mcp

# List
gemini mcp list

Project-scoped .mcp.json·json

{
  "mcpServers": {
    "github": { "type": "http", "url": "https://api.githubcopilot.com/mcp/" },
    "sentry": { "type": "http", "url": "https://mcp.sentry.dev/mcp" },
    "db": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@bytebase/dbhub", "--dsn", "${DATABASE_URL}"]
    }
  }
}

External links

Gemini MCP docs

Exercise

Add 2 MCP servers to Gemini that you've already configured for another CLI. Confirm they work identically. Note the cross-tool portability dividend.

Progress

Progress is local-only — sign in to sync across devices.

← PreviousSlash Commands — /tools, /memory, /chat, /save Next →Extensions — Bundled Tool Sets

Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)

No comments yet — be the first.