Three relevant product surfaces
| Surface | MCP path | Primary audience |
|---|---|---|
| Gemini CLI | Configures local or remote MCP servers and can install extensions that bundle them. | Developers working in a terminal. |
| Gemini Enterprise | Can add approved custom remote MCP servers as data sources/connectors; some capabilities are preview features. | Organizations building governed search and agent experiences. |
| Gemini API | Current Interactions API tooling can connect to remote MCP servers. | Developers building their own Gemini-powered applications. |
Gemini CLI terminology
An MCP server exposes tools, resources, and prompts. A Gemini CLI extension is the larger installable package and may bundle MCP servers with commands, prompts, hooks, skills, subagents, and themes. The extension is not the protocol endpoint.
Gemini CLI supports local stdio and remote HTTP transports. Configuration lives under mcpServers in layered settings or can be managed through CLI commands. Server aliases may prefix tool names to prevent collisions.
Authentication and controls
- Remote CLI servers can use OAuth where supported; interactive flows depend on a usable browser and callback path.
- Headless, container, and remote-SSH environments may need a different authorization approach or forwarding.
- CLI server trust defaults should remain conservative. Tool include/exclude lists and server-level filtering help limit the active capability surface.
- Gemini Enterprise adds Cloud IAM, organization policy, OAuth client configuration, data-source controls, and preview-specific constraints.
- The Gemini API’s remote MCP support is an application integration, not proof that the consumer Gemini interface exposes an “add any MCP server” setting.
Progressive tool exposure
Current Gemini CLI documentation describes connecting to configured servers, fetching definitions, validating schemas, and registering tools. That is eager discovery. Resource discovery helpers concern MCP resources, not necessarily deferred action-tool schemas. Until Google documents a distinct deferred tool-search mechanism, large catalogs should be filtered explicitly.
Good fit
Use Gemini CLI for development workflows and local/remote engineering tools. Use Gemini Enterprise when the requirement is governed organizational access to approved data and agent capabilities. Use the API path when you own the application and need remote MCP inside a custom Gemini experience.