Mad Fish Elements
HomeTrust CenterGemini setup

Gemini setup

Configure Gemini CLI to discover and use Mad Fish Elements tools through its remote MCP connection.

Gemini surfaceGemini CLI remote MCP
User configuration~/.gemini/settings.json
Add Mad Fish Elements to Gemini CLI

Gemini CLI supports remote Streamable HTTP MCP servers and custom request headers. Register Mad Fish Elements at user scope when the same portal identity should be available across trusted projects, or use project scope when the connection should remain specific to one project.

The examples keep tool confirmations enabled with trust: false. Review each requested action, especially tools with Write or Delete capability.

1. Generate and scope the key

Use the Gemini operator's portal user

Create the key from the same Mad Fish Elements user who will run Gemini CLI. Label it clearly, such as Gemini CLI - Taylor.

Review connection capabilities

Confirm the user can see only the required connections and that Write or Delete is disabled unless the Gemini workflow needs it.

Protect the configuration

The Authorization header contains a live credential. Keep the settings file out of source control and restrict access to the user account that runs Gemini.

2. Add the server with Gemini CLI

Replace the placeholder with the full key and run the command from a terminal. Command-line arguments may be retained in shell history, so use the JSON method below when local history retention makes that inappropriate.

Add at user scopeTerminal
gemini mcp add --transport http --scope user --header "Authorization: Bearer <full-user-api-key>" mad-fish-elements https://funkadelic.madfishdigital.com/mcp

The user scope writes the server definition to your Gemini user configuration.

Configure settings directly~/.gemini/settings.json
{
  "mcpServers": {
    "mad-fish-elements": {
      "httpUrl": "https://funkadelic.madfishdigital.com/mcp",
      "headers": {
        "Authorization": "Bearer <full-user-api-key>"
      },
      "timeout": 30000,
      "trust": false
    }
  }
}

Merge the server entry into an existing mcpServers object rather than replacing other configured servers.

Configuration locations
PlatformUser configurationProject configuration
macOS / Linux~/.gemini/settings.json.gemini/settings.json
Windows%USERPROFILE%\.gemini\settings.json.gemini\settings.json

3. Verify the connection

List configured servers

Run gemini mcp list and confirm mad-fish-elements is connected. Inside Gemini CLI, use /mcp to inspect connection status and discovered tools.

Check the tool boundary

The discovered list should match the portal user's enabled connections and capabilities. Start with a read-only request and keep confirmation prompts enabled.

Reload after changes

If permissions or the key change, restart Gemini CLI or disable and re-enable the MCP server so it reconnects with current configuration.

Troubleshooting

Server is disconnected: verify httpUrl, JSON syntax, network access, and the Authorization header. Run gemini mcp list for detailed diagnostics.

401 Unauthorized: use the complete active key after Bearer . The shortened portal prefix cannot authenticate.

Tools are missing: confirm portal access, let synchronization finish, then reconnect or restart Gemini CLI.

Key was saved in project configuration: ensure .gemini/settings.json is ignored by version control, or move the server to user scope and rotate the exposed key.

Create a dedicated Gemini key

Use a clearly labeled user credential so the connection can be audited, rotated, or revoked independently.

Open Connections & Keys