Troubleshooting

Errors surface at two layers: the HTTP layer (the connection cannot be established at all — 401, 403, 429) and the tool layer (the connection works but a single tool call returns an error).

401 — Authentication errors

Symptom: `Missing or malformed Authorization header`

Cause: The request has no Authorization header, or it is not in Bearer TOKEN form.
Fix: Verify that your client configuration sends the header exactly as Authorization: Bearer cnfg_.... Setup blocks: /docs/en/mcp/setup

Symptom: `Invalid API key`

Cause: The key was not found — it may have been copied incorrectly, be missing characters, or never have been created.
Fix: Generate the key again under Profile → API Keys and make sure you copy all of it (including the leading cnfg_).

Symptom: `API key has been revoked`

Cause: The key has been revoked.
Fix: Generate a new key under Profile → API Keys and update your client configuration.

Symptom: `API key has expired`

Cause: The key's expiry date has passed.
Fix: Generate a new key; choose a non-expiring one if needed.

OAuth-capable clients such as claude.ai discover the authorization server automatically via the WWW-Authenticate header in the 401 response and redirect you to the Connfig login screen. If you use claude.ai, most 401s are solved by re-authorizing the connector.

403 — Subscription blocks

Symptom: `API access requires an active subscription`

Cause: Your subscription is in a blocking state (canceled, passive, or deactivated).
Fix: Check your subscription status in the app; renew it from the pricing page if needed.

Symptom: `Subscription has expired`

Cause: The subscription period ended and renewal did not happen.
Fix: Check your payment method and renew the subscription. After renewal, your key keeps working unchanged.

Symptom: `No Connfig account exists for this user` (OAuth only)

Cause: No Connfig account is linked to the user who signed in via OAuth.
Fix: In the claude.ai connector, make sure you sign in with the same account you used to register with Connfig.

429 — Rate limit

Symptom: `Rate limit exceeded. Try again in a minute.`

Cause: The 120-requests-per-minute-per-key limit was exceeded.
Fix: Wait a minute and continue. Check that the assistant is not stuck in a loop calling the same tool repeatedly.

Symptom: `RATE_LIMITED: Too many start_scrape calls. Try again in a minute.`

Cause: Heavy tools (start_scrape, create_and_send_campaign, send_test_mail) are limited to 10 calls per minute per tool. Test mail has additional rules: 20 per day and a 60-second cooldown between sends.
Fix: Wait for the time indicated in the error message.

Tool-layer errors

These come back with HTTP 200, but the tool result contains an error in the form CODE: message.

Code	Example message	Cause and fix
`QUOTA_EXCEEDED`	`Monthly lead quota reached (25/25).`	Your monthly scrape quota is used up — wait for the period reset or upgrade the plan.
`QUOTA_EXCEEDED`	`Monthly mail limit reached (500/500 in the last 30 days).`	The 30-day mail limit is used up. If the limit is `0`, the message says campaign sending is not included in your plan — upgrade.
`QUOTA_EXCEEDED`	`CRM record limit reached (25/25). Upgrade the plan or remove manual records.`	The manual CRM record limit is used up.
`QUOTA_EXCEEDED`	`Seat limit reached (1/1). Upgrade the plan to invite more members.`	The seat limit is used up — upgrade the plan to invite members.
`QUOTA_EXCEEDED`	`Workspace limit reached (1/1). Upgrade the plan or remove a workspace.`	The workspace limit is used up.
`SCRAPE_IN_PROGRESS`	`A lead-generation job is already running for this account.`	Only one scrape runs at a time — wait for it to finish via `get_scrape_status` or `list_scrape_jobs`.
`FORBIDDEN`	`Leads enrichment is only available on Pro and Team plans`	Enrichment is a Pro/Team feature.
`FORBIDDEN`	`You do not have access to this workspace`	The workspace is not yours or you are not a member — see what you can access with `list_workspaces`.
`FORBIDDEN`	`Only the workspace owner can manage members`	The action requires ownership or an extra permission (e.g. `can_manage_tasks`).
`NOT_FOUND`	—	No record exists with the given ID; the assistant may have used a wrong ID — have it verify with a list tool first.
`INVALID_INPUT`	—	The tool parameters do not match the schema; rephrase the instruction more precisely and retry.
`INTERNAL_ERROR`	`Something went wrong`	Unexpected server-side error — retry shortly; contact support if it persists.

Other

Symptom: 405 `Method not allowed`

Cause: A GET or DELETE request hit the endpoint. Connfig MCP only accepts Streamable HTTP (POST); it does not support the legacy SSE transport.
Fix: Make sure the transport type in your client configuration is http (Streamable HTTP).

Symptom: Connection established but no tools show up

Fix: Restart the client and check that you typed https://mcp.connfig.com/mcp correctly (including the trailing /mcp).

If the problem persists, query your subscription and quota status through the assistant with get_my_subscription and get_workspace_usage — the cause of most blocks shows up in those two outputs.

On this page