MCP setup guide

Gemini CLI

Gemini CLI reads MCP servers from project and user settings. It can use OAuth or API-key-based servers, and it shows the configured tools in its MCP management view.

Paths checked against the client's docs · November 2026

Surfaces

CLI

Scope

Project or global

Project config.gemini/settings.json
Installer agentgemini-cli
1 / How it works

How Gemini CLI handles MCP

Gemini CLI reads MCP servers from project and user settings. It can use OAuth or API-key-based servers, and it shows the configured tools in its MCP management view.

Project or global. Project scope keeps the server with the repository; global scope makes it available in every workspace.

Best for

Terminal workflows in the Google ecosystem.

Installer flag-a gemini-cli
2 / Where it goes

Where the MCP config lives

The installer writes this file for you. Use the paths below when you want to inspect, edit, or remove a server by hand.

Project
.gemini/settings.json
Global
~/.gemini/settings.json

Project paths are relative to the workspace. Global paths are per user. On Windows, ~ means your user folder; use %USERPROFILE% in Explorer or PowerShell. A project config is shared with the team; a global config is personal.

3 / Install

Add a remote server

Start with a server in the MCP directory, or use your provider's endpoint. The examples use https://mcp.example.com/mcp so you can see the shape; replace it with the real URL.

  1. 01

    Find the endpoint

    Open a server page and copy its hosted endpoint. Do not use a local command or an npm package name for a remote server; those are different connection types.

    Open the MCP directory
  2. 02

    Run the installer

    Use the project config for a repository-specific server, or the global config for every workspace. The server name becomes example in the config.

    Gemini CLI · project
    # Add this to Gemini CLI MCP settings:
    {
      "mcpServers": {
        "example": {
          "httpUrl": "https://mcp.example.com/mcp"
        }
      }
    }
    Gemini CLI · global
    # Add this to Gemini CLI MCP settings:
    {
      "mcpServers": {
        "example": {
          "httpUrl": "https://mcp.example.com/mcp"
        }
      }
    }

    If the server page says SSE instead of HTTP, add --transport sse:

    SSE variant
    # Add this to Gemini CLI MCP settings:
    {
      "mcpServers": {
        "example": {
          "url": "https://mcp.example.com/mcp"
        }
      }
    }
  3. 03

    Authorize if the provider asks

    The first connection may open a browser for OAuth. Sign in with the provider and approve only the scopes you need. If the server uses an API key, create it in the provider's dashboard and add it through the client's auth flow or config.

    Never paste a provider token into a project config you will commit. Prefer the client's secret store or a user-level config for credentials.

  4. 04

    Reload and verify

    Run `/mcp` inside a session, or `gemini mcp list` in a terminal.

    Then ask for a task, not a tool: “Find the open issues assigned to me” or “Summarize the latest release.” The client decides which advertised tool to call.

4 / Use

What changes in the chat

Once the server is connected, its tools appear in the client's tool list. You still talk to the agent normally; MCP is plumbing, not a different chat interface.

Read

“Find the customer notes mentioning the migration and summarize the blockers.”

Write

“Create a draft page with this outline, but do not publish it yet.”

Investigate

“Check the failed deployment and list the last three changes that touched it.”

Verify

“Which MCP tools do you have available for this task?”

If the agent ignores the server, check that the server is enabled and that its tools are approved. Some clients require a per-tool confirmation before the first call.

5 / Troubleshooting

When it does not connect

The server is missing

Confirm the file exists at the path above, the JSON or TOML is valid, and you restarted the client or opened a new session.

It connects but tools are empty

Enable the server in the client's MCP UI, approve its tools, and check that the provider has not revoked your token.

OAuth keeps reopening

Remove the server from the client, revoke the app's access in the provider's account settings, then add it again.

A project server is ignored

Some clients require you to trust the folder before loading project MCP config. Trust the repository, then start a new session.

6 / Notes

What to watch for in Gemini CLI

  • Run `gemini mcp list` to inspect the configured servers.
  • OAuth credentials are stored by the client, not in the MCP settings file.
  • Use global scope for a personal server; use project scope for a shared repo.
7 / Remove

Remove or reset the server

Remove the server when it is no longer needed, or reset it when a credential or connection state gets stuck.

  1. Remove the server entry from the Gemini CLI MCP config.
  2. Start a new Gemini CLI session and run /mcp.
  3. Confirm that the server is gone.

Remove the entry, restart the CLI, and add the server again if authentication is stale.

Sources

Official documentation

Client behavior changes. These links are the source of truth for paths, flags, and approval behavior.

Next setup guideAntigravity