Troubleshooting
What each Archee MCP error means and how to fix it.
Every result carries a call_id. Quote it when you ask for help.
Connecting
| You see | Do this |
|---|---|
401 with a browser prompt |
Sign in when the client opens Archee. |
401 with a token |
Check the token was copied whole and has not expired or been revoked. |
| The client cannot reach the server | Use the full URL including the path: https://mcp.archee.studio/mcp. |
| “MCP access is not included in your plan” | Upgrade on the Billing page. |
| The browser never opens | Your client may not support remote sign-in; use a personal access token. |
Calling
| You see | Do this |
|---|---|
403 insufficient_scope or ScopeDenied |
The connection lacks a scope, for example deliver. Reconnect and approve it, or create a token with it. Some scopes need a plan that includes them. |
| “Not enough credits” | Top up on the Billing page; the message says how much the program needs. |
BudgetExceeded |
The program spent its allowance. Split the work or raise timeout_s. |
[timed out after N s] |
Raise timeout_s (up to 120), or move long work to archee.agent.run. |
| “MCP sandboxes in use” or a rate limit | Wait the number of seconds shown and retry. |
duplicate_call |
The client resent a call that already ran. Send a new call. |
| Results look cut off | Return less; write large data to a file and return its link. |
Unavailable or BridgeTimeout |
A service was busy. Retry after a few seconds. |
Still stuck
Write to the Archee team from archee.studio with the call_id, the client you use and what you expected.