LLM Connections

Generate API Key

Create, use, rotate, and revoke a personal Mad Fish Elements API key.

API key details

Portal locationAccount → My MCP

Request headerAuthorization: Bearer <your-full-api-key>

Personal credential

Create one key for each integration. An API key carries your own Mad Fish Elements permissions, so never share it with a teammate. Standard LLM connections use secure sign-in; use a key only for direct API access, automation, or a client that requires header-based authentication.

1 Open My MCP

Sign in to Mad Fish Elements with your own user account.
Open Account → My MCP or go directly to My MCP.
Find the My API keys table.

2 Generate the key

Select + Generate new key.
Enter a descriptive label that identifies where it will be used, such as ChatGPT Desktop — MacBook or Reporting script — BigQuery sync.
Select Generate.
Copy the full value immediately and store it in a password manager or secrets manager.

Copy it now

The complete key is displayed only once. The portal keeps only a fingerprint, so you cannot retrieve the full value later.

3 Use the key

Send the complete value in one of these request headers:

Authorization: Bearer <your-full-api-key>
X-API-Key: <your-full-api-key>

For an MCP client, use the first form unless its setup specifically asks for an API-key header. Do not configure an empty or stale Authorization header alongside OAuth sign-in; it overrides the sign-in token and causes a 401 response.

4 Manage keys safely

Action	When to use it
Pause	Temporarily stop an integration without reconfiguring it.
Rotate	Issue a new value after possible exposure or as routine security hygiene; update the integration immediately.
Revoke	Permanently disable a retired integration.
Rename	Update the key label without changing the key value.
Pause all keys	Emergency stop, such as after a lost device.

The portal shows status, last-used time, and calls this month. You can maintain up to five active keys; revoke an unused key before creating another if you reach the limit.

Keep it safe

Never commit a key to source control or paste it into shared documents, prompts, or chats. Use one key per integration so you can rotate or revoke only the affected connection. If a key is exposed, rotate it immediately; the old value stops working as soon as the replacement is issued.

Troubleshooting

Symptom	Fix
401 Unauthorized	Verify the full key, the `Bearer` prefix and space, and that the key is active in My MCP.
401 after successful OAuth sign-in	Remove the stale or empty Authorization header from the client.
Key works but tools are missing	Keys follow your user permissions; verify that your platforms are connected and enabled.
Cannot create another key	You have reached the five-key limit; revoke an unused key first.

Open My MCP