Redbark MCP Server

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) live access to the same financial data, plus scoped management of your Redbark account: syncs, destinations, rules, categories and event destinations. It is a thin layer over the Redbark API v2: every API operation is one tool, under the same name as the operation id.

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 read 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"
    }
  }
}

Related MCP server: akahu-mcp

Tools

Every Redbark API v2 operation is a tool, named after its operation id (81 tools, 62 listed by default), plus five composite tools. Reads fetch banking data live. Writes change Redbark configuration only (syncs, destinations, rules, categories, event destinations), never your bank. The AI only gets the scopes you grant on the consent screen; tools outside those scopes refuse and say which scope to grant.

Ids are the public ids from the API (acct_..., conn_..., sync_..., dest_...). Lists are paginated the same way as the API: the AI passes limit and follows the page token. The full list of tools, with every argument, is the API reference.

Composite tools

Five tools combine several API calls so common questions take one step:

Default and admin toolsets

By default the server lists the core tools (62 API operations, the composites and redbark_guide). Nineteen admin tools (API keys, consents, sync category mappings, category reset, ruleset duplicate/reorder, event destination enable/disable/ping/rotate, destination rotate_secret/enable) are hidden but still callable; add ?toolsets=admin to the server URL to list them. The list is also filtered to the scopes you granted.

Prompts and guides

Clients that support MCP prompts get set_up_sync, monthly_spending_review, fix_failing_sync and connect_bank. redbark_guide returns a topic guide (onboarding, syncs and destinations, rules and categories, events and webhooks, errors and scopes, API conventions) generated from the docs, and the server sends short usage instructions on connect.

Every tool takes a context argument: a one-line statement of the goal the user is trying to reach. It is used for product analytics and never contains your banking data.

Example prompts once connected:

"What did I spend on groceries across all my accounts last month?" "What's my total cash balance right now?" "Create a sync from my everyday account to the Budget sheet and run it now." "Add a rule that tags Uber transactions as Travel."

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. Scopes offered on the consent screen:

keys:write is never offered over OAuth: an OAuth-connected agent cannot create API keys. Write scopes are optional. Leave one unticked and the matching tools refuse with a message that names the scope.

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_.... The key's own scopes apply.

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.

• Scoped access. The AI can only use the scopes you grant. Reads and each write family are separate. Nothing can touch your bank itself; writes change Redbark syncs, destinations, rules, categories and event destinations only.

• Revocable. Revoke a connected app from the dashboard at any time. The server immediately stops accepting its tokens.

• Traceable. Every error carries a request id you can quote to support.

• 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.