Mad Fish Elements
HomeTrust CenterLLM Connections

LLM Connections

Connect supported AI clients to the Mad Fish Elements MCP server with a user-scoped key generated in the portal.

Production MCP endpointhttps://funkadelic.madfishdigital.com/mcp
AuthenticationAuthorization: Bearer <your-user-api-key>
One governed connection for the LLMs your team uses

Mad Fish Elements exposes connected business systems through a remote Model Context Protocol (MCP) server. A compatible LLM client connects to that endpoint, presents a portal-generated user API key, discovers the tools available to that user, and invokes only the operations their account permits.

The key is an identity credential for the gateway, not a Google, Microsoft, CRM, finance, or commerce password. Provider credentials remain in the platform's protected credential store while the gateway applies organization, user, connection, and capability policy to every request.

01

Generate

Create a key while signed in as the person who will use the LLM client.

02

Scope

An administrator enables that user's connections and Read, Write, or Delete capabilities.

03

Connect

Add the MCP endpoint and the full key to the supported client's connection settings.

04

Enforce

The gateway resolves the key to one organization and user before exposing or running tools.

Desktop client

Claude Desktop

Add the remote server to Claude's JSON configuration and verify its tools.

Microsoft agent

Copilot Studio

Add the MCP endpoint as a tool with header-based API-key authentication.

Workspace app

ChatGPT

Create a custom MCP app, scan its tools, and control workspace availability.

Command-line client

Gemini CLI

Register the HTTP server in Gemini settings with an Authorization header.

Key and access requirements

Use one key per person and client

Generate the key from the intended user's Connections & Keys page. Do not distribute one administrator key across a team or move a key between client accounts.

Connection visibility is assigned separately

A valid key does not automatically expose every organization connection. Members see only connections an administrator enables for them, and viewers remain limited by their assigned role.

Capabilities follow portal policy

Read, Write, and Delete controls determine which tools can be used. Some LLM clients also request confirmation before write or destructive actions.

Rotate after exposure

A key is displayed only when generated. If it is pasted into logs, chat, source control, or another unsafe location, rotate or revoke it and replace the client configuration.

Generate a user-scoped key

Open Connections & Keys, confirm the user's connection access, and create the credential used by the selected LLM client.

Open Connections & Keys