LLM Connections

Connect Mad Fish Elements to ChatGPT

Add Mad Fish Elements to ChatGPT as a custom MCP app. Enable developer mode once, point ChatGPT to our server, and sign in safely with your Mad Fish Elements account.

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?
chatgpt.com (web browser)	✓ Yes — developer-mode MCP app with sign-in (OAuth)
ChatGPT desktop app (macOS / Windows)	✓ Yes — add a custom MCP under Plugins → MCPs using an API key
ChatGPT mobile apps	✗ Not yet

Two different flows

On the web you sign in with your Mad Fish Elements account (no key). The desktop app’s custom-MCP form is header-based, so there you’ll paste a personal API key instead. Both connect to the same server with the same permissions.

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.

1Check your ChatGPT plan and enable developer mode

Custom MCP apps require a paid ChatGPT plan. Developer mode applies to the web route (Option A below); the desktop app’s MCPs tab doesn’t require it. Capabilities differ by tier:

Plan	What you can do
Pro	Connect MCP apps with read/fetch tools (reporting and analysis).
Business	Full MCP support (beta). Admins enable developer mode for themselves under Settings → Apps → Advanced settings and publish apps to the workspace.
Enterprise / Edu	Full MCP support (beta). Admins grant access via Permissions & Roles → Connected Data; authorized users then enable developer mode in Settings → Apps → Advanced settings.

2Add the server

Option A — On the web (chatgpt.com), with sign-in

With developer mode on, go to Settings → Apps (workspace admins: Workspace settings → Apps → Create).
Create a new app/connector named Mad Fish Elements.
MCP server URL: https://funkadelic.madfishdigital.com/mcp
Authentication: choose OAuth. ChatGPT discovers our sign-in endpoints automatically — no client ID or secret needed.
Click Scan tools and complete the Mad Fish Elements sign-in when prompted. The tool list that appears reflects your own account permissions.
Click Create.

Option B — In the desktop app (macOS / Windows), with an API key

First, generate a personal API key on the portal’s My MCP page and copy the full value when it is issued. Then, in the ChatGPT desktop app:

Open Plugins (Manage plugins, skills, and MCPs) and select the MCPs tab.
Choose Connect to a custom MCP.

Fill in the form:

Field	Value
Name	`Mad Fish Elements`
Type	Streamable HTTP (not STDIO)
URL	`https://funkadelic.madfishdigital.com/mcp`
Bearer token env var	Leave empty
Headers	Click + Add header. Key: `Authorization` · Value: `Bearer <your-full-api-key>` (the word Bearer, a space, then the key)
Headers from environment variables	Leave empty

Click Save. Mad Fish Elements appears in your MCPs list and its tools become available in conversations.

Tip for advanced users

Instead of pasting the key into the Headers row, you can set an environment variable on your machine (e.g. MCP_BEARER_TOKEN) containing just the raw key and reference it in the Bearer token env var field — the key then never lives in the ChatGPT config. Use one approach or the other, not both.

3Test, then publish (workspace plans)

Open a draft chat with the app enabled and try a read-only request — “List the ad accounts I can access.”
On Business/Enterprise/Edu, an admin reviews and publishes the app from Drafts so teammates can use it. Each teammate signs in with their own Mad Fish Elements account on first use.

Note for Business plans

Published apps can’t be edited in place — to change tools you recreate and republish. Enterprise/Edu admins can update published apps.

Advanced: use an API key on the web 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.

In the web app’s authentication step choose API key / Bearer token, set the header name to Authorization, and paste Bearer <your-full-api-key> as the value. (The desktop app already uses this key-based method — see Option B above.)

Troubleshooting

Symptom	Fix
No “developer mode” option	Your plan doesn’t include it, or an admin hasn’t granted you access (Enterprise/Edu).
No MCPs tab in the desktop app’s Plugins screen	Update the desktop app to the latest version, or use the web route (Option A) instead.
Desktop: 401 after saving	Check the header row: Key must be exactly `Authorization` and the Value must start with `Bearer` followed by the full key. Confirm the key is active on the My MCP page, and that Type is Streamable HTTP.
401 during tool scan	Complete the sign-in pop-up; if using an API key, confirm the header value starts with `Bearer` .
Tools missing after publishing	Each user must connect (sign in) to the app themselves; tools mirror each user’s portal permissions.
Unexpected OAuth prompt when you configured a key	Remove the empty Authorization value — a blank header overrides sign-in.

Open the setup wizard

Other assistants: Claude · Gemini · Copilot · API keys