Fix API key and MCP connection problems

Work through API key and MCP connection failures in order: confirm your role, check the key's status and permissions, re-copy or rotate a key whose secret was lost, and reconnect an assistant with the right connector URL and preset.

Purpose

Find the visible reason an API key or MCP assistant connection is failing and apply the safest fix, from confirming your role to rotating a key or reconnecting an assistant with the right permissions.

Who this is for

Admins and developers whose API key or assistant connection has stopped working or will not connect.

Prerequisites

A signed-in session on the workspace that owns the key or connection.
An admin or developer role if you need to create, rotate, or revoke a key.
The name of the failing integration or assistant and the key it uses.

Steps

Open the API and integrations area and find the key the integration uses in the keys list.
Confirm your role can manage keys; if creating or rotating is blocked, ask a workspace owner or admin.
Check the key's status and permissions, and confirm they match what the integration needs.
If the secret was lost or never copied, rotate the key and copy or download the new secret once before closing the panel.
For an assistant, recheck the connector URL and the assistant or MCP preset, then reconnect.
Open the key's activity to confirm its requests are arriving, and revoke any key you no longer trust.

Expected result

You know why the key or connection failed, the integration connects again with a workspace-owned key using only the permissions you chose, and its requests appear in the key's activity.

Verification

The key shows an active status with the permissions the integration needs.
The integration's recent requests appear in the key's activity.
A reconnected assistant reads context and requests actions within your plan limits.

If something goes wrong

Creating or rotating a key is blocked: Your role can view keys but not change them; ask a workspace owner or admin to make the change.
You lost the secret or closed the panel before copying it: A secret is shown in full only once and never again; rotate the key, then copy or download the new secret before you close the panel.
An assistant or integration cannot connect: Confirm the key is active, its permissions or preset match what the integration needs, and you are using the correct connector URL, then reconnect.
Requests are being limited or rejected: Check the key's activity and your plan's request limits; reduce request volume or upgrade if you are over the limit.
A key looks compromised or belongs to a retired integration: Revoke it immediately to stop its access, then create a replacement with only the permissions the integration needs.

Permissions

Viewing keys and their activity is available to integration roles; creating, rotating, and revoking keys needs an admin or developer role, and the access you manage is always workspace-owned and separate from platform administration.

Support

If a key is active with the right permissions but an approved integration still cannot connect, ask your workspace admin first. LumenReach support can help with connection requirements without ever asking for or exposing your key's secret or platform credentials.