How to add an MCP server to Gemini CLI

Gemini CLI reads its MCP servers from ~/.gemini/settings.json and connects to them over stdio (a local process), Streamable HTTP and HTTP+SSE. 123,036 of the 123,036 servers we can write a config for work in it.

A local server

A local server runs on your machine, started by Gemini CLI from its package. It needs Node.js installed first. For example, Azure MCP Server goes in ~/.gemini/settings.json:

{
  "mcpServers": {
    "azure": {
      "command": "npx",
      "args": ["-y", "@azure/[email protected]", "server", "start"]
    }
  }
}

Every step for this server in Gemini CLI

A remote server

A remote server runs on its publisher's machines, and Gemini CLI connects to its address. Nothing needs installing. For example, Context7 goes in ~/.gemini/settings.json:

{
  "mcpServers": {
    "context7": {
      "httpUrl": "https://mcp.context7.com/mcp"
    }
  }
}

Every step for this server in Gemini CLI

Which servers work in Gemini CLI

Gemini CLI can send a key in a header, so the 3,251 servers that need one work in it.

Runs	Servers	In Gemini CLI?
Local (stdio)	85,194	Works
Remote, Streamable HTTP	30,880	Works
Remote, Streamable HTTP, key in a header	3,204	Works
Remote, HTTP+SSE	3,711	Works
Remote, HTTP+SSE, key in a header	47	Works

If the server does not show up

Matches the official docs The configs follow Gemini CLI's MCP docs, read on 2026-10-31.

Gemini CLI on plug.directory · Best MCP servers for Gemini CLI