Gemini CLI

Works in the Gemini CLI on all plans. MCP servers are not supported in the Gemini web or mobile apps.

Connect Sumble MCP to the Gemini CLI as a custom MCP server.

Sumble MCP uses the streamable HTTP transport, so it goes in the httpUrl field of the Gemini CLI's mcpServers configuration.

Option 1: gemini mcp add (recommended)

1. Run the following command in your terminal:

gemini mcp add --transport http --scope user sumble https://mcp.sumble.com

1. Start the CLI by running gemini

2. Run /mcp auth sumble and complete the auth flow in your browser

3. Run /mcp list to confirm Sumble is connected, then use Sumble MCP in your Gemini CLI chat

Option 2: edit settings.json manually

1. Open your Gemini CLI settings file:

   • User-wide: ~/.gemini/settings.json

   • Project-only: .gemini/settings.json in your project directory

2. Add the sumble entry to the mcpServers object:

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

1. Start the CLI by running gemini

2. Run /mcp auth sumble and complete the auth flow in your browser

3. Run /mcp list to confirm Sumble is connected, then use Sumble MCP in your Gemini CLI chat

The Gemini CLI discovers Sumble's OAuth configuration automatically and stores the resulting tokens in ~/.gemini/mcp-oauth-tokens.json, refreshing them as needed. If your tools stop working, re-run /mcp auth sumble.

For more detail on MCP configuration options — tool filtering, timeouts, and per-project scopes — see Google's MCP servers with Gemini CLI documentation.

Once connected, see Try it for example prompts, Available tools for what each tool does, and Credits for how usage is billed.