ChatGPT setup

Create a custom MCP app in ChatGPT and connect it to Mad Fish Elements with user-scoped authorization.

ChatGPT surfaceCustom MCP app in developer mode

Server URLhttps://funkadelic.madfishdigital.com/mcp

Create a custom Mad Fish Elements app

ChatGPT workspaces with custom MCP app access can connect to the remote Mad Fish Elements server, scan its tools, and make the approved app available in conversations. Workspace plan, role, developer-mode, and publishing requirements determine who can create or use the app.

Use a dedicated portal user key when the app setup offers API-key or Bearer authentication. If your workspace requires OAuth instead, choose OAuth and complete the Mad Fish Elements authorization and consent flow; do not paste the portal key into OAuth client ID or client secret fields.

1. Enable custom MCP apps

Confirm workspace availability

Custom MCP app availability varies by ChatGPT plan and workspace policy. Business and Enterprise/Edu administrators can manage developer access and app publishing; some plans or modes may limit write actions.

Turn on developer mode

In ChatGPT, open Settings → Apps → Advanced settings and enable developer mode when that control is available. Workspace administrators may first need to grant permission.

Generate the user credential

In Mad Fish Elements, create a key for the person whose connections ChatGPT should use. Confirm that user's connection access and capabilities before scanning tools.

2. Create the appSettings or Workspace settings → Apps → Create

App field	Value	Notes
Name	`Mad Fish Elements`	Use a recognizable workspace app name.
MCP endpoint	`https://funkadelic.madfishdigital.com/mcp`	ChatGPT must be able to reach this remote HTTPS endpoint.
Authentication	`API key` or `Bearer token`	Select the token-based option offered by your workspace.
Header	`Authorization`	If the setup asks for a custom header name, use Authorization.
Credential	`Bearer <full-user-api-key>`	If scheme and token are separate fields, choose Bearer and enter only the full key in the token field.

3. Scan, test, and publish

Scan tools

Select Scan tools and wait for discovery to complete. A token-authenticated scan should not open an external provider consent page.

Test the draft app

Create a new chat, select the draft Mad Fish Elements app from the tools menu, and begin with a read-only request. Review confirmation prompts before allowing writes.

Publish with workspace controls

Administrators can review and publish the app, restrict who can access it, and control actions where the workspace plan supports those controls. Each distinct portal user should authenticate with their own identity rather than sharing one key.

Troubleshooting

Create or developer mode is missing: confirm the ChatGPT plan, workspace role, and administrator policy allow custom MCP apps.

Tool scan returns 401: verify the full key and Bearer scheme, then confirm the key is active. Rotate it if the original value is no longer available.

Expected tools are absent: enable the connections for that portal user, verify capabilities, wait for synchronization, and scan again.

ChatGPT opens OAuth authorization: the app was configured for OAuth rather than API-key authentication. Complete that flow or recreate the draft using the token option supported by the workspace.

Prepare the ChatGPT app identity

Create a dedicated portal credential and verify its connection permissions before scanning the MCP server.

Open Connections & Keys