> ## Documentation Index
> Fetch the complete documentation index at: https://docs.redbark.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Give AI agents read-only access to your banking and brokerage data

The Redbark MCP server connects AI assistants like Claude, ChatGPT, and Cursor directly to your bank accounts, balances, transactions, and brokerage data. Instead of syncing to a spreadsheet or app, the AI queries your data on demand.

<Info>
  MCP access requires an active **Developer** or **Professional** plan. Trial subscriptions, legacy accounts in their 14-day grace period, and grandfathered accounts also retain access. Brokerage data (holdings, trades) requires **Professional** (or an active trial).
</Info>

## What is MCP?

[Model Context Protocol](https://modelcontextprotocol.io) is an open standard that lets AI tools read data from external services. The Redbark MCP server provides **read-only** access -- your AI can view your data but can never modify, delete, or move anything. When connected, your AI assistant can answer questions like:

* "What bank accounts do I have connected?"
* "What's my current balance across all accounts?"
* "What did I spend on groceries this month?"
* "Show me my brokerage holdings and P\&L"

Data is fetched live from your banking provider on each request. Nothing is stored by Redbark or sent to the AI until you ask.

## How it's different from other destinations

|                     | Google Sheets, You Need a Budget, etc. | MCP Server                                 |
| ------------------- | -------------------------------------- | ------------------------------------------ |
| **When data moves** | On a schedule (every few hours)        | On demand, when you ask                    |
| **What moves**      | Transactions are written and stored    | Nothing is stored; data is fetched live    |
| **Set up in**       | Redbark dashboard                      | Your AI tool's config file                 |
| **Best for**        | Record-keeping, budgeting, automation  | Asking questions, analysis, ad-hoc lookups |

## Setup

<Steps>
  <Step title="Copy the MCP URL">
    Go to [Settings > AI Connectors](https://app.redbark.com/settings) in the Redbark dashboard and copy the MCP URL:

    ```text theme={null}
    https://mcp.redbark.com/mcp
    ```
  </Step>

  <Step title="Add the server to your AI tool">
    Paste the URL into Claude, ChatGPT, Cursor, or any remote MCP client. Your tool will open a Redbark OAuth consent screen.
  </Step>

  <Step title="Start asking questions">
    Open a conversation and ask about your accounts, balances, or transactions. The AI will call the MCP server automatically.
  </Step>
</Steps>

## Configuration

<Tabs>
  <Tab title="Claude (claude.ai, Desktop, Cowork, mobile)">
    Anthropic's Custom Connectors flow works the same in claude.ai, Claude Desktop, Cowork, and the mobile apps — once added, the connector is available everywhere you use Claude.

    **Pro / Max (personal):**

    1. Open **Customize > Connectors** in Claude.
    2. Click `+` then **Add custom connector**.
    3. Paste the URL:
       ```
       https://mcp.redbark.com/mcp
       ```
    4. Click **Add**, then **Connect** on the new `redbark` entry to run through the OAuth consent screen.

    **Team / Enterprise:** an owner adds the connector once at **Organization settings > Connectors > Add > Custom > Web**, pastes the same URL, and clicks **Add**. Members then go to **Customize > Connectors** and click **Connect**.

    Leave OAuth client ID/secret blank — Redbark uses dynamic client registration, so Claude provisions a client automatically. See Anthropic's [custom connectors guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) for screenshots.
  </Tab>

  <Tab title="Claude Code">
    Use the CLI (recommended):

    ```bash theme={null}
    claude mcp add --transport http redbark https://mcp.redbark.com/mcp
    ```

    Then run `/mcp` inside Claude Code to complete the OAuth flow.

    Or add the server to `.mcp.json` in your project root (or `~/.claude.json` for user scope):

    ```json theme={null}
    {
      "mcpServers": {
        "redbark": {
          "type": "http",
          "url": "https://mcp.redbark.com/mcp"
        }
      }
    }
    ```

    `"type": "streamable-http"` is an accepted alias for `"http"`.
  </Tab>

  <Tab title="Cursor">
    Add to `~/.cursor/mcp.json` (global) or `.cursor/mcp.json` (project):

    ```json theme={null}
    {
      "mcpServers": {
        "redbark": {
          "url": "https://mcp.redbark.com/mcp"
        }
      }
    }
    ```

    Cursor will open the Redbark OAuth consent screen on first connection. See [Cursor's MCP docs](https://cursor.com/docs/mcp).
  </Tab>

  <Tab title="ChatGPT">
    Custom MCP connectors require **Developer Mode** in ChatGPT. Available on Plus, Pro, Business, Enterprise, and Edu plans.

    1. Go to **Settings > Apps & Connectors > Advanced settings** and toggle **Developer Mode** on.
    2. Back in **Settings > Connectors**, click **Create**.
    3. Fill in:
       * **Connector name**: `Redbark`
       * **Description**: e.g. `Live bank and brokerage data from Redbark`
       * **Connector URL**: `https://mcp.redbark.com/mcp`
       * **Authentication**: OAuth
       * Tick **I trust this application**
    4. Click **Create**, then connect the new connector to run the OAuth flow.

    See OpenAI's [ChatGPT connector setup guide](https://developers.openai.com/apps-sdk/deploy/connect-chatgpt).
  </Tab>
</Tabs>

<Tip>
  API keys are still supported for direct REST API consumers and advanced local MCP setups, but OAuth is recommended for hosted AI connectors.
</Tip>

## What your AI can access

Once connected, these tools are available to your AI assistant:

| Tool                | What it does                                         | Plan                    |
| ------------------- | ---------------------------------------------------- | ----------------------- |
| `list_connections`  | Show all linked bank and brokerage connections       | Developer+              |
| `list_accounts`     | List all accounts with names, types, and currencies  | Developer+              |
| `list_balances`     | Fetch live balances for specific accounts            | Developer+              |
| `list_transactions` | Get transactions with date range and account filters | Developer+              |
| `list_holdings`     | Show brokerage holdings with prices and P\&L         | Professional (or trial) |
| `list_trades`       | List brokerage trades with date filters              | Professional (or trial) |

The AI chooses which tool to call based on your question. You don't need to know the tool names.

## Security

* **Read-only access**: the MCP server can only read your data. It cannot create, modify, or delete anything in your bank accounts, connections, or syncs.
* **Your data stays yours**: data is fetched live from your bank and returned to your AI tool. Redbark never stores transaction data.
* **OAuth auth**: hosted AI tools receive short-lived OAuth access tokens and refresh them without storing your Redbark API keys.
* **Plan-gated**: MCP access requires an active Developer or Professional plan; trial subscriptions, legacy accounts in their 14-day grace period, and grandfathered accounts also qualify. Brokerage tools are restricted to Professional (or an active trial).
* **Revocable**: you can revoke a connected app from the [dashboard](https://app.redbark.com/settings) at any time. The MCP server immediately stops accepting its tokens.

## Troubleshooting

| Problem                                                                         | Fix                                                                                                                                                                                           |
| ------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| "Missing Authorization header" / "Invalid or expired OAuth access token"        | Reconnect the Redbark MCP server from your AI tool so it can complete the OAuth flow again                                                                                                    |
| "MCP server not available" / 405 Method Not Allowed / connection fails silently | In Claude Code's `.mcp.json`, make sure `"type"` is `"http"` (or `"streamable-http"`), not `"sse"`. Our server is Streamable HTTP only and will reject SSE-style GET requests                 |
| "Add custom connector" button not visible in Claude                             | You're on the wrong screen — Custom Connectors live under **Customize > Connectors** (personal) or **Organization settings > Connectors** (Team/Enterprise owners), not Settings > Connectors |
| ChatGPT won't let you add a custom MCP server                                   | Toggle **Developer Mode** on first under **Settings > Apps & Connectors > Advanced settings**                                                                                                 |
| "Invalid or revoked API key"                                                    | If you are using legacy API-key auth, create a new key in [Settings > API Keys](https://app.redbark.com/settings)                                                                             |
| "Your plan does not include API access…" (error `code: plan_upgrade_required`)  | This is a plan gate, not a credentials problem — the MCP server needs the Developer or Professional plan. [Upgrade your plan](https://app.redbark.com/settings/billing) and reconnect         |
| "Brokerage endpoints require a Professional plan"                               | Holdings and trades need a Professional plan                                                                                                                                                  |
| "This OAuth connection does not include brokerage access"                       | The AI tool was connected without the `brokerage:read` scope. Disconnect and reconnect, and grant brokerage access on the consent screen                                                      |
| Server not responding                                                           | The server scales from zero; retry after a few seconds                                                                                                                                        |
| Tools not showing up                                                            | Restart your AI tool after editing the config file                                                                                                                                            |

<Tip>
  For the full technical reference (schemas, error formats, endpoint details), see the [API Reference > MCP Server](/api-reference/mcp) page.
</Tip>