Errors and limits

This page lists the limits on Connie’s MCP server and the errors it returns. Messages are written for people, so your AI app usually shows them as they are. Search this page for the text you see. For setup problems in a specific app, see MCP troubleshooting.

Limits

What	Limit	What happens
Requests	300 per minute and 3,000 per hour for each sign-in or API key	”Too many requests to Connie in a short time. Nothing was run. Wait about N seconds and try again.” The response is HTTP 429 with a `Retry-After` header.
Open sessions	10 at once for each sign-in or API key	”This API key already has 10 open Connie sessions, the most allowed at once. Close chats you are not using, or restart your MCP client, then try again.” The message says API key even when you signed in with OAuth.
Idle session	Ends after 30 minutes without activity	Most apps reconnect by themselves. Otherwise: “This Connie session has ended or expired…”
Sign-in attempts	30 per person per hour	The app’s sign-in fails with a temporary error. Wait and try again.
OAuth access	Renewed automatically about every 8 hours; you stay signed in as long as the app is used at least once every 30 days	After 30 days without use, sign in again.
Connection links	A `https://connie.ai/connect/...` link for connecting a missing account works for 15 minutes	’Connection link unavailable’. Ask your AI app for a new link.
API keys	50 active keys per workspace	”A workspace can have up to 50 active API keys. Revoke one you no longer use.”

The server speaks MCP over Streamable HTTP at https://mcp.connie.ai and supports protocol versions 2025-11-25, 2025-06-18 and 2025-03-26.

Credits and billing errors

MCP actions use the workspace’s credits exactly as in the app. Looking up tools and skills is free.

Every result from running a tool includes a billing receipt. It shows the credits charged (0 for free actions) and a line per action. The final charge can differ from the estimate Get tool gave you. When a connected app may also bill you on its own side, the receipt says so.
Not enough credits: the action doesn’t run (“Not enough Connie credits… Nothing was charged.”). Your AI app gets one next step for you:
- Owners and admins get a link to the right fix, for example start a trial, choose a paid plan, add credits, or update the payment method if the last plan payment failed.
- Members and guests get “Ask a workspace owner or admin to add credits”.
- In ChatGPT, the link goes to connie.ai/pricing instead of a checkout page.
Low balance: after a successful action, if fewer than 100 credits are left and auto top-up is off, the app gets: “Low balance: Only N Connie credits are left in this workspace; paid calls stop when they run out.”
Guest budget used up: “Ask a workspace owner or admin to raise your guest credit budget”.

See Credits, Top-ups and Plans.

Running tools safely

Idempotency keys: when running a tool that changes data, contacts someone or spends credits, send an idempotency key. If a request times out and you retry with the same key, Connie returns the original result (marked as replayed) instead of running the action twice. Without a key, a retry can send the same email twice or charge twice.
Cost estimates: Get tool can return a price estimate without running anything: “Nothing was run and nothing was charged”.

Message	Fix
”Your Connie sign-in expired…”	Authenticate again in your app.
”Your Connie sign-in was revoked…”	Remove Connie in your app and add it again.
”This sign-in was issued for a different Connie address…”	Re-add Connie with exactly `https://mcp.connie.ai`.
”Your MCP client sent a refresh token where an access token was expected…”	Disconnect Connie in the app and connect again.
”Your Connie sign-in is no longer valid…”	Disconnect Connie in the app and connect again.
”Your Connie sign-in didn’t include access to Connie’s MCP server…”	Disconnect, connect again and click Allow access.
”Authorization session expired” (in the browser)	Restart the connection from your app and finish it within 10 minutes.
”Authorization request invalid” (in the browser)	Remove Connie from the app and add it again.

API key errors

Message starts with	Fix
”Connie needs an API key to connect…”	Add `Authorization: Bearer sk_…` to the server’s settings, or switch to OAuth sign-in.
”The Authorization header isn’t in the right format…”	Use `Authorization: Bearer sk_…`.
”This request sent two different Connie credentials…”	Send only one header.
”That doesn’t look like a complete Connie API key…”	Copy the full key again.
”Connie doesn’t recognise this API key…”	The key was deleted. Use a current key.
”The Connie API key … was revoked” / ”… expired”	Copy your Personal key or generate a new one.
”The Connie workspace this API key belongs to was deleted…”	Email support@connie.ai within 7 days of the deletion to restore the workspace, or use a key from another workspace.
”This API key acts with the permissions of someone who is no longer in the workspace…”	Use your own key, or have an admin change the key’s Permissions.
”This Connie API key isn’t linked to a workspace member…”	Use your Personal key, or have an admin set the key’s Permissions.
”This API key can’t be used with Connie’s MCP server…”	Use your Personal key or create a new one.
”Switching workspaces is not available with an API key…”	Use the other workspace’s key, or OAuth.

See API keys.

Workspace and permission errors

Message	Meaning and fix
”You are not a member of the requested workspace…”	The workspace isn’t one of yours. Pick one of your workspaces, or ask its admin for an invite.
”workspaceId must be a valid UUID. Call list-my-workspaces and copy the workspaceId exactly. Nothing was run.”	A workspace name was passed instead of its ID. List workspaces first.
”Workspace … was deleted on … and is closed to MCP access…” (or “This workspace was deleted on …”)	Email support@connie.ai within 7 days of the deletion to restore it, or use another workspace.
”… you are a guest in workspace …. Guests can read through this connector but not write…”	Ask an admin for member access, or use a read-only action.
”This tool is disabled in this workspace’s AI tool settings.”	An admin can turn the tool back on. See Tool permissions.

Server errors

Message	Fix
”Something went wrong on Connie’s side while handling this request (reference xxxxxxxx)…”	Try again. If it keeps happening, email support@connie.ai with the reference, your app and the time.
”Connie’s response could not be serialized for your client (reference …)”	Try again, or ask for a smaller result.
”Connie couldn’t check your credentials because of a temporary problem on our side. Nothing was run…”	Wait a minute and try again.
”Connie is handling a lot of connections right now. Please try again in a minute.”	Wait and try again.

Get started

Chat

Records

Automations

Inbox

Tools

Skills

Analytics

Notifications & email

Account & workspace

Billing & plans

Connie in your AI apps (MCP)

Developers

Help

Errors and limits

Limits

Credits and billing errors

Running tools safely

API key errors

Workspace and permission errors

Server errors

​Limits

​Credits and billing errors

​Running tools safely

​Sign-in errors (OAuth)

​API key errors

​Workspace and permission errors

​Server errors

​Related

Limits

Credits and billing errors

Running tools safely

Sign-in errors (OAuth)

API key errors

Workspace and permission errors

Server errors

Related