> ## 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

> Resolve MCP connection, authentication, permission, and input errors.

## Connection and setup

* **405 Method Not Allowed or SSE connection failure:** use Streamable HTTP. In Claude Code, set `type` to `http` or `streamable-http`, not `sse`. The data endpoint accepts `POST /mcp`.
* **Claude's Add custom connector button is missing:** use **Customize > Connectors** for personal plans, or **Organization settings > Connectors** for Team and Enterprise owners.
* **ChatGPT cannot add a connector:** use ChatGPT on the web and check your plan and workspace permissions before enabling **Developer Mode**. See the plan-specific requirements below.
* **Tools do not appear after editing configuration:** restart the AI client. Some tools need the [admin toolset](/docs/mcp/tools#default-and-admin-toolsets); others require additional scopes.

See [setup](/docs/mcp/setup) for complete client instructions.

### ChatGPT plan and workspace requirements

OpenAI's [MCP apps help article](https://help.openai.com/en/articles/12584461-developer-mode-and-mcp-apps-in-chatgpt) distinguishes these cases:

* **Personal Pro:** enable Developer Mode in your own settings. The help article describes read/fetch MCP access, not the full write-action beta. Personal accounts do not need workspace-admin approval.
* **Business:** an admin or owner must enable Developer Mode for themselves and create and publish the custom app under **Workspace settings > Apps**. Ordinary members use the published app.
* **Enterprise/Edu:** an admin or owner grants Developer Mode access through **Permissions & Roles > Connected Data**. Authorised members can then enable it in their own settings; only admins/owners publish apps and control workspace access.

Full MCP support, including write actions, is described in that help article for Business and Enterprise/Edu. OpenAI's [developer guide](https://developers.openai.com/api/docs/guides/developer-mode) lists broader plan eligibility and a newer **Settings > Security and login > Developer mode** path, while the help article uses **Settings > Apps > Advanced Settings**. Availability and menus are changing: check the controls shown in your account rather than assuming every plan exposes the same tools.

## Authentication and permissions

* **Missing Authorization header or expired OAuth token:** reconnect Redbark from the client to complete OAuth again.
* **Invalid or revoked API key:** create a replacement in [Settings > API & MCP](https://app.redbark.com/settings/api-mcp).
* **`plan_upgrade_required`:** this is a plan gate, not a credentials problem. Check [plan requirements](/docs/mcp/security#plans) and [billing](https://app.redbark.com/settings/billing).
* **`insufficient_scope` or a missing named scope:** disconnect and reconnect the client, granting that permission. Brokerage reads require `brokerage:read` as well as an eligible plan.

## Invalid arguments

Refresh the client's tool schema and correct the named argument before retrying. Use the [checked examples](/docs/mcp/tools#tool-arguments-and-pagination) as a guide.

* Copy public ids from discovery responses. Do not substitute names, account numbers, or database UUIDs.
* Use `account` for balances, details, transactions, holdings, and trades. `get_account` uses `id`; `list_accounts` uses `connection` to filter.
* Use the opaque `page` token for pagination, not `offset` or the whole next-page URL.
* Check account eligibility. Banking balance tools cannot read brokerage or Documents accounts.
* Keep `from` on or before `to`, and use supported date formats.

Repeating the unchanged call will not fix validation, an unsupported account type, or a missing workflow prerequisite.

## Getting help

When an API error includes a request id, quote it to [support](mailto:support@redbark.com) along with the tool name and error code. Do not include banking payloads or access tokens.

For error formats and endpoint details, see the [API v2 error reference](/docs/api-reference/v2/errors).