> ## Documentation Index > Fetch the complete documentation index at: https://redbark.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshooting > Fix Redbark Advisor MCP sign-in, permission, billing and rate limit errors. ## How errors reach your AI client * **Sign-in and limit errors** stop the whole request. The server answers with an HTTP status, such as 401 or 429, and a JSON-RPC error with a plain message. * **Refused tool calls** come back as a tool result marked as an error. The text starts with the error code, for example `insufficient_scope: This call needs the clients:write scope.` * **Invalid arguments** come back as a JSON-RPC error, `Invalid tool arguments`, naming the argument that is not valid. The codes are the same as the REST API's. See [errors](https://redbark.com/docs/advisor/api-reference/errors.md). ## Connecting * **The client cannot connect, or reports 405.** Use Streamable HTTP. In Claude Code, set the type to `http`, not `sse`. The server only accepts `POST`. * **"This link cannot be used."** The app's sign-in request was not valid, so Advisor will not send you back to it. Remove the connector and add it again. * **"This request has expired or was already answered."** The consent page lasts 10 minutes and can be answered once. Start again from the app. * **"You are not in a firm that can be connected."** You signed in with an account that is not in a firm. Sign in with your firm account. * **The app is refused when it registers.** Hosted apps must use a sign-in return address Advisor knows. Today that is Claude, ChatGPT, Cursor and VS Code, and any app that signs in through `localhost`. Contact [support](mailto:support@redbark.com) to have an app added, or use an [API key](https://redbark.com/docs/advisor/mcp/setup.md#use-an-api-key). * **Tools are missing.** The tool list follows your access and your role. Connect again with **Read and change** for write tools. Admin-only tools need an admin. Restart the client after changing its settings. ## 401 Unauthorised The credential is missing or no longer works. Your AI client shows one of these messages. | Message | What to do | | - | - | | Send your API key as a bearer token: Authorization: Bearer \. | No credential was sent. Connect the app with OAuth, or send an API key. | | This access token is not valid. | Disconnect the app and connect it again. | | This access token was issued for a different API. | The app signed in for the REST API, not MCP. Remove it and add it again with the MCP server URL. | | This access token has expired. Refresh it or connect again. | Most clients refresh by themselves. If not, connect again. | | This connection was ended. Connect the app again. | The app was disconnected in Settings, or connected again elsewhere. Connect again. | | The person who connected this app is no longer a member of the organisation, so the connection was ended. | The person was removed from the firm. A current member connects instead. | | This organisation is not available. | The firm is being deleted. | | This API key is not valid. / This API key has been revoked. | Ask an admin for a new key. | To reconnect, remove or disconnect Redbark Advisor in your AI client, add it again and sign in. Connecting again replaces the old connection. ## 403 Forbidden | Code | What it means | What to do | | - | - | - | | `insufficient_scope` | The connection does not have the scope this tool needs. The message names it. | Connect again and choose **Read and change**. For an API key, an admin makes a key with that area. | | `admin_required` | Only an admin can use this tool. | Ask an admin, or ask an admin to change your role. See [team](https://redbark.com/docs/advisor/settings/team.md). | | `member_removed` | The person the call acts as is no longer in the firm. | The connection or key cannot be used. A current member connects again, or an admin makes a new key. | ## 402 Subscription required `subscription_required` means your firm needs a subscription to add clients, invite them or send checklists. Reading data still works. An admin can subscribe in **Settings > Billing**. See [billing](https://redbark.com/docs/advisor/settings/billing.md). ## 409 Client limit reached `client_limit_reached` means all 20 active clients on your plan are in use. Archive a client you no longer work with (`archive_client`), or contact Redbark at [support@redbark.com](mailto:support@redbark.com). ## 429 Too many requests The connection or key made more than 120 requests in a minute. The message is "Too many requests. The limit is 120 a minute." * Wait the number of seconds in the `retry-after` header, then try again. * The limit resets at the start of each minute. * You do not need to reconnect or make a new key. To use fewer requests, ask for one client at a time, or ask your AI client to use the list tools' `limit` and `cursor` rather than reading every item. ## Other errors * **413, "Request body exceeds size limit."** A request can be up to 64 KB. Upload files with `create_document_upload` and the address it returns, not through a tool argument. * **400, "A batch holds 1 to 10 messages."** Send at most 10 JSON-RPC messages in one request. * **`Unknown tool`.** The tool name is wrong, or the client's tool list is out of date. Restart the client. * **`invalid_cursor`.** Pass `next_cursor` back exactly as it was returned. * **`directory_unavailable`.** The team list could not be read. Try again in a moment. * **500, `internal_error`.** Something went wrong on our side. Try again. If it keeps happening, contact support. ## Getting help Email [support@redbark.com](mailto:support@redbark.com) with the tool name, the error code and the time it happened. Do not send API keys, tokens or client data. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.