Sign in
Use the portal account for the person who will use the LLM client.
Connect supported AI clients to the Mad Fish Elements MCP server with secure sign-in, while dedicated API keys remain available for desktop and locked-down environments.
https://funkadelic.madfishdigital.com/mcpMad Fish Elements exposes connected business systems through a remote Model Context Protocol (MCP) server, where supported AI clients sign in with the user's portal account, discover that user's available tools, and invoke only the operations their role allows.
Desktop and locked-down environments can use a dedicated API key instead, while provider credentials remain protected and the gateway still enforces organization, user, connection, and capability policy.
Use the portal account for the person who will use the LLM client.
An administrator enables that user's connections and Read, Write, or Delete capabilities.
Add the MCP endpoint and complete the selected client's setup flow.
The gateway resolves the connection to one organization and user before exposing or running tools.
Add the secure Mad Fish Elements connector and sign in with your portal account.
Have one administrator publish a shared agent, then let each teammate sign in with their own account.
Create a custom MCP app, complete secure sign-in, and control workspace availability.
Register the remote MCP server, sign in, and verify the tools available to your account.
Create, use, rotate, or revoke a personal key for header-based clients.
Generate fallback keys for the intended user and never distribute one administrator key across a team.
Members see only the connections an administrator enables for them, and viewers remain limited by role.
Read, Write, and Delete controls determine which tools can be used by each AI client.
If a key reaches logs, chat, source control, or another unsafe place, revoke it and replace the client configuration.
Connect at least one platform, confirm your access, then follow the guide for the AI assistant your team uses.