LLM Connections

Connect Mad Fish Elements to Claude

Add Mad Fish Elements to Claude as one custom connector in your Claude account. Now you can set it up once to avoid editing any configuration files, and use the same connection on claude.ai, in the desktop app, and on mobile, with secure sign-in that keeps setup simple for you on every device.

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?
claude.ai (web browser)	✓ Yes — set up and use here
Claude desktop app (macOS / Windows)	✓ Yes — set up and use here; same connector, no separate setup
Claude mobile apps (iOS / Android)	✓ Yes — the connector you add syncs here automatically

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 Claude plan

Custom connectors are available on all Claude plans — Free (limited to one connector), Pro, Max, Team, and Enterprise. On Team and Enterprise plans, an organization Owner adds the connector once and every member can then connect with their own sign-in.

2Add the connector

Pro, Max, and Free plans

You can do these steps on claude.ai in a browser or in the desktop app — the settings are the same and the result applies to both, plus mobile.

In Claude, open Settings → Connectors.
Click Add custom connector.
Name it Mad Fish Elements and paste the server URL: https://funkadelic.madfishdigital.com/mcp
Click Add. Leave the Advanced settings (OAuth client ID/secret) empty — they aren’t needed.

Team and Enterprise plans (Owner, one time)

Open Organization settings → Connectors.
Click Add, hover over Custom, and choose Web.
Paste the server URL above and click Add.
Members then go to Settings → Connectors, find Mad Fish Elements, and click Connect.

3Sign in when prompted

The first time you connect, Claude opens the Mad Fish Elements sign-in page. Sign in with your portal account and approve the request. That’s it — Claude receives its own scoped credential, and you never see or handle a key.

4Use it in a chat

In any conversation, click the + (or sliders) button near the message box, open Connectors, and toggle on Mad Fish Elements. Then just ask — for example, “Pull last week’s Google Ads performance for my accounts.”

Advanced: Claude Desktop config file with a user API key (desktop app only)

This fallback applies only to the desktop app — a config file can’t add a server to claude.ai in the browser or to mobile. Use the connector flow above for those.

Connection details

Production MCP endpoint https://funkadelic.madfishdigital.com/mcp

Authentication Authorization: Bearer <your-user-api-key>

Each person should connect Claude Desktop with an API key generated for their own Mad Fish Elements user. The key resolves to that user’s organization, visible connections, and Read, Write, and Delete permissions. Do not share an administrator’s key with another user.

1. Generate the user API key

Use the correct user account. Generate the key while signed in as the person who will use Claude Desktop.
Confirm connection access. Only connections enabled for that user will be available through the MCP server. An administrator can adjust connection access and capability permissions in the portal.
Sign in to the portal, open Connections & Keys, and generate a key with a recognizable label such as Claude Desktop - Taylor.
Copy the complete key when it is shown — for security, it cannot be displayed again later. The prefix alone is not a credential.

2. Open the Claude Desktop configuration

Platform	Configuration file	How to open it
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`	Claude Desktop → Settings → Developer → Edit Config
Windows	`%APPDATA%Claudeclaude_desktop_config.json`	Claude Desktop → Settings → Developer → Edit Config

If the file is empty, use the first example. Replace <paste-your-full-api-key> with the full key and keep the Bearer prefix, including the space.

New Claude Desktop config — use this complete object when no other MCP servers are configured:

{
  "mcpServers": {
    "mad-fish-elements": {
      "url": "https://funkadelic.madfishdigital.com/mcp",
      "headers": {
        "Authorization": "Bearer <paste-your-full-api-key>"
      }
    }
  }
}

Merge with existing servers — if the file already contains an mcpServers object, add only the mad-fish-elements entry inside it. Do not create a second mcpServers property or remove existing servers:

{
  "mcpServers": {
    "existing-server": {
      "command": "existing-command"
    },
    "mad-fish-elements": {
      "url": "https://funkadelic.madfishdigital.com/mcp",
      "headers": {
        "Authorization": "Bearer <paste-your-full-api-key>"
      }
    }
  }
}

3. Restart and verify Claude

Validate and save the JSON. Use straight quotation marks, keep braces balanced, and remove trailing commas. Save the file as plain UTF-8 JSON.
Fully restart Claude Desktop. Quit the application completely, then reopen it so the desktop client reloads the configuration.
Confirm the tools are available. Open the Connectors control from the conversation composer and select Mad Fish Elements. You can also review the MCP connection status and logs in Claude Desktop’s Developer settings.

Troubleshooting the config-file route

Symptom	Fix
Server does not appear	Confirm the file is valid JSON, verify it is saved at the platform-specific path above, and restart Claude Desktop completely.
401 Unauthorized	Confirm the full key was pasted after `Bearer` , the key is active, and it belongs to the intended user. Generate a fresh key if the original value is unavailable.
Connection appears but tools are missing	Ask an administrator to enable the required connections and capabilities for that user, then allow the portal sync job to complete before reconnecting.
Key was exposed	Revoke or rotate it immediately in Connections & Keys, replace the value in the JSON file, and restart Claude Desktop.

Troubleshooting

Symptom	Fix
Sign-in window never appears	Pop-up blocked — allow pop-ups for claude.ai, then click Connect again.
“401” or “authentication failed” after signing in	Your portal account may be inactive or have no platforms enabled. Check the My MCP page.
Connector added but no tools appear	Toggle the connector on for the conversation (the + menu), and confirm your parent account has platforms enabled for your user.
Repeated re-authorization prompts	Remove and re-add the connector to refresh its stored token.

Open the setup wizard

Other assistants: ChatGPT · Gemini · Copilot · API keys