LLM Connections

Connect Mad Fish Elements to Gemini

Google’s consumer Gemini app does not yet accept custom MCP servers, so choose Gemini CLI, included with Google AI Pro and Ultra subscriptions, for native MCP and secure sign-in. Gemini Enterprise customers can also have a Google admin register Mad Fish Elements centrally as a custom MCP connector for every team.

Connection details

Server URL https://funkadelic.madfishdigital.com/mcp

Requires an active Mad Fish Elements account with at least one platform connected (run the setup wizard if you haven’t).

Where this works

Surface	Supported?
gemini.google.com (web browser)	✗ Not supported — the consumer Gemini web app doesn’t accept custom MCP servers
Gemini mobile / desktop apps	✗ Not supported
Gemini CLI (terminal, included with AI Pro/Ultra)	✓ Yes — full support with sign-in; follow the steps below
Gemini Enterprise (Business/Enterprise editions)	✓ Yes — your Google Workspace admin adds it as a custom MCP connector

Native sign-in (OAuth)

Sign in, don’t paste keys. Mad Fish Elements supports native sign-in (OAuth) for MCP connections. When your assistant asks you to authorize, you’ll sign in with your Mad Fish Elements portal account — no API key to copy, store, or rotate. Your access is scoped to your own user permissions, and your team admin can revoke it from the portal at any time.

1Install Gemini CLI

Install: npm install -g @google/gemini-cli (requires Node.js 20+).
Run gemini once and sign in with the Google account tied to your AI Pro/Ultra subscription.

2Add the server

One command — no key, no header:

gemini mcp add --transport http --scope user mad-fish-elements https://funkadelic.madfishdigital.com/mcp

Or merge this into ~/.gemini/settings.json:

{
  "mcpServers": {
    "mad-fish-elements": {
      "httpUrl": "https://funkadelic.madfishdigital.com/mcp",
      "timeout": 30000
    }
  }
}

3Sign in

Start a session: gemini
Run /mcp auth mad-fish-elements. Gemini CLI discovers our sign-in endpoints automatically and opens your browser.
Sign in with your Mad Fish Elements portal account and approve. Tokens are stored securely in ~/.gemini/mcp-oauth-tokens.json and refresh automatically.

4Verify

Run gemini mcp list — mad-fish-elements should show as connected. Then just ask: “Summarize yesterday’s GA4 traffic for my properties.”

Advanced: connect with an API key instead of sign-in

Some setups can’t use sign-in (locked-down workspaces, service accounts, or older clients). In that case, generate a personal API key in the portal’s My MCP page and authenticate with a header:

Authorization: Bearer <your-full-api-key>

Treat the key like a password. Each key is tied to your user account and can be paused, rotated, or revoked from the portal.

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

The header holds a live credential — keep settings.json out of version control and shared folders.

Troubleshooting

Symptom	Fix
Server shows “disconnected”	Run `/mcp auth mad-fish-elements` to (re)authenticate, and confirm the URL ends in `/mcp`.
Browser sign-in never opens	Copy the printed URL into a browser manually (common over SSH/headless sessions).
401 with an API key configured	Confirm the header value starts with `Bearer` and the key is active on the My MCP page.
Tools missing	Tools mirror your portal permissions — check which platforms your account has enabled.

Open the setup wizard

Other assistants: Claude · ChatGPT · Copilot · API keys