Which Gemini CLI settings connect a remote Montage server?
Gemini CLI documents remote MCP servers through settings.json and uses httpUrl for Streamable HTTP. Treat its configuration scope and installed release as part of the connection: a server saved for one environment may not be active in another terminal session. The workflow below uses documented OAuth discovery and MCP authentication controls without assuming every release exposes identical commands or consent screens.
{
"mcpServers": {
"montage": {
"httpUrl": "https://app.montages.co/mcp"
}
}
}Use Montage signals_status only and describe the actual workspace response. Stop if authentication or transport is unavailable.Identify the settings scope
Find the settings.json that applies to your current Gemini CLI session using the official configuration documentation. Check existing mcpServers entries before editing. A project configuration and a user configuration may have different reach, so decide whether this connection should accompany a repository or remain personal. Do not overwrite unrelated assistant or server settings.
Use httpUrl for this transport
Merge the montage entry shown below into mcpServers. The httpUrl property selects the documented Streamable HTTP connection rather than a local command-based server. Keep the complete https://app.montages.co/mcp address. An executable name, an SSE-specific URL, or a web documentation link is not a substitute for this hosted MCP endpoint.
Use the installed authentication controls
Inspect Gemini CLI's /mcp controls and its documented /mcp auth workflow for the installed version. OAuth discovery can identify the server's authorization requirements, but you still need to approve the appropriate account and requested scope. If those controls are absent or reject the flow, consult that release's documentation instead of fabricating an access token.
Inspect the active server tools
After authorization, confirm the montage server is active in the same session where you intend to ask questions. Review the available tool names and keep the initial request limited to status. A discovered tool definition describes an interface; it does not establish that the account has permission to execute it in the desired workspace.
End with a real signals_status call
Request Montage signals_status and read the returned workspace information before proceeding. If it reports unauthorized access, revisit /mcp auth and verify the account and scope. If no tools appear, recheck the effective settings file, httpUrl spelling and client version. Record an unresolved connection as blocked, not connected, and do not replace the status check with a collection request.
Keep the boundaries clear.
- OAuth behavior and configuration precedence depend on the Gemini CLI version and active scope.
- This is documented configuration, not evidence that a particular installed client completed consent.
- No API key is included in this example; authentication must use the client's supported path.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.