Redbark MCP Server

Connect AI agents to your Australian bank and global brokerage data — live balances, transactions, holdings, and trades over the Model Context Protocol.

Website · Documentation · Dashboard

Redbark syncs bank and brokerage accounts to Google Sheets, Airtable, Notion, YNAB, and webhooks. The Redbark MCP server gives MCP-compatible AI agents — Claude, Cline, Cursor, ChatGPT, VS Code, and others — secure, read-only access to the same live financial data.

Australian banking data is sourced through the regulated Consumer Data Right (CDR / open banking) framework. Your banking credentials are never shared with Redbark or your AI agent, and Redbark never stores your banking data — every request is proxied live from the source.

Quickstart

The server is remote and hosted — there is nothing to install or run.

https://mcp.redbark.com/mcp

• Transport: Streamable HTTP
• Auth: OAuth 2.1 (automatic — your client opens a browser consent flow), or a personal API key as a fallback
• Requirements: a Redbark account on a Developer or Professional plan (API access is included in the free trial)

Cline

Add to cline_mcp_settings.json (Cline → MCP Servers → Configure):

{
  "mcpServers": {
    "redbark": {
      "type": "streamableHttp",
      "url": "https://mcp.redbark.com/mcp"
    }
  }
}

Cline discovers the OAuth authorization server automatically and opens a browser window to approve access. To use an API key instead (created at app.redbark.com → Settings → API Keys):

{
  "mcpServers": {
    "redbark": {
      "type": "streamableHttp",
      "url": "https://mcp.redbark.com/mcp",
      "headers": {
        "Authorization": "Bearer rbk_live_YOUR_API_KEY"
      }
    }
  }
}

Claude Code

claude mcp add --transport http redbark https://mcp.redbark.com/mcp

Claude (desktop / web)

Settings → Connectors → Add custom connector → paste https://mcp.redbark.com/mcp.

Cursor

{
  "mcpServers": {
    "redbark": {
      "url": "https://mcp.redbark.com/mcp"
    }
  }
}

Tools

All tools are read-only. The server cannot move money, modify accounts, or change your Redbark configuration.

Example prompts once connected:

"What did I spend on groceries across all my accounts last month?" "What's my total cash balance right now?" "Show my share purchases this financial year and summarise them in a table."

Authentication & scopes

OAuth (recommended). The server implements the standard MCP authorization flow (OAuth 2.1 with Dynamic Client Registration and PKCE). Clients that support MCP OAuth need only the server URL — registration, browser consent, and token refresh are automatic. Granted scopes:

You can review and revoke any connected agent at any time from Connected Apps in your Redbark settings.

API key (fallback). For clients without OAuth support, create a key at app.redbark.com → Settings → API Keys and send it as Authorization: Bearer rbk_live_....

Security

• No stored banking data. Redbark proxies data live from providers at request time; customer banking data is never persisted to Redbark's database.
• Regulated data access. Australian bank connections run on the CDR (open banking) framework — credentials go to your bank, never to Redbark or your agent.
• Read-only by design. No tool can initiate payments or mutate accounts.
• Scoped, revocable access. OAuth tokens carry only the scopes you consent to and can be revoked in one click.
• Requests are rate-limited pre- and post-authentication, and every request is auditable.

Pricing

MCP access requires a Developer or Professional plan and is included in the free trial. Brokerage tools (list_holdings, list_trades) require Professional.

Support

• Docs: docs.redbark.com/api-reference/mcp
• Email: support@redbark.com

License

This repository (documentation and assets) is MIT licensed. The hosted service is governed by the Redbark terms.