Redbark

com.redbarkPublished by redbark.comOfficial publisherv2.1.0Updated Oct 24, 2026

Live AU/NZ bank (CDR) and brokerage data for AI agents, plus management of Redbark syncs and rules

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFinanceData & Analytics

Overview

AI-generated overview

Hosted MCP server giving AI assistants live Australian/NZ bank and brokerage data plus scoped management of Redbark syncs, destinations, rules and categories.

What you can do
  • Read accounts, balances, transactions, holdings and trades, plus connections, consents and institutions
  • Summarize spending and income by category, merchant, account or month, and get an account overview with consent expiry flags
  • Create, update, run, resync and cancel syncs, and diagnose failing runs
  • Manage destinations, categories, rulesets and rules, and event destinations
  • Redeliver events and create bank link sessions
  • Use composite tools and topic guides for setup, spending review and sync troubleshooting
When to use it
Useful when you want an assistant to answer questions about your own Australian or NZ bank and brokerage data, or to set up and maintain Redbark syncs to Google Sheets, Airtable, Notion, YNAB or webhooks without leaving the chat.
Requirements
Remote hosted endpoint over Streamable HTTP; nothing to install. OAuth 2.1 consent flow (or a personal API key sent as an Authorization Bearer header). A Redbark account on a Developer or Professional plan; brokerage tools need Professional.
Before you install
Grants an assistant access to personal financial data; grant only the read and write scopes you need, since write scopes let it change syncs, destinations, rules, categories and event destinations. Writes never touch the bank itself. An API key carries its own scopes and is a long-lived secret. Each tool call sends a context line used for product analytics. Revoke connected apps from the dashboard when done.

Installation

In SourceWeft

  1. Open Redbark in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.redbark%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

[Redbark logo]

Redbark MCP Server

Connect AI agents to your Australian and NZ bank and global brokerage data, and let them manage your Redbark syncs, destinations, rules and categories 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) 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):

json
{  "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):

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

Claude Code

bash
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

json
{  "mcpServers": {    "redbark": {      "url": "https://mcp.redbark.com/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.

FamilyExample toolsScopeExample prompt
Accountget_menone"Which plan am I on?"
Connections, consents, institutionslist_connections, get_connection, list_consents, list_institutions, revoke_connectionmcp:read, connections:write to revoke"Which of my bank connections expire this month?"
Accounts and balanceslist_accounts, get_account, get_account_balance, get_account_detailsmcp:read"What is the balance on my offset account?"
Transactionslist_transactions, get_transactionmcp:read"List my transactions over $500 since 1 July"
Holdings and tradeslist_holdings, list_tradesmcp:read + brokerage:read"What are my largest positions?"
Syncs and runslist_syncs, create_sync, update_sync, run_sync, resync_sync, list_sync_runs, cancel_sync_runmcp:read, syncs:write"Run the Notion sync now and tell me when it finishes"
Destinationslist_destinations, create_destination, list_destination_resources, rotate_destination_secretmcp:read, destinations:write"Which tabs does my Budget spreadsheet have?"
Categorieslist_categories, create_category, set_category_sources, list_provider_categoriesmcp:read, categories:write"Make a Subscriptions category and map streaming merchants to it"
Ruleslist_rulesets, create_rule, preview_ruleset, reorder_ruleset_rules, attach_sync_rulesetmcp:read, rules:write"Preview what my cleanup ruleset would do to last month"
Eventslist_events, get_event, redeliver_event, list_event_destinations, create_event_destinationmcp:read, events:write"Show the last failed sync run event and redeliver it"
Link sessionscreate_link_session, get_link_sessionconnections:write"Give me a link to connect another bank"
API keyslist_api_keys, get_api_keynot available over OAuthKeys are created in the dashboard. API-key clients with keys:write can manage keys

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:

ToolWhat it does
account_overviewEvery account with a live balance, grouped by connection, with consent expiry and reauthorisation flags
spending_summarySpend and income for a date range, grouped by category, merchant, account or month, with the largest transactions. Raw transactions are never returned
setup_syncChecks the destination, resolves its resources (Sheets tabs, YNAB accounts), builds the mappings and creates the sync
diagnose_syncLast runs, failure reason, related events, connection and consent state, and a recommended next action
connect_bankFinds the institution and creates a link session, returning the hosted URL to hand to the user

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:

ScopeGrants
mcp:readEvery read tool
brokerage:readHoldings and trades (Professional plan)
account:readget_me
connections:read, connections:writeConnections, consents, institutions; revoke, reauthorize, refresh, link sessions
data:readAccounts, balances, transactions, holdings, trades, provider categories
categories:read, categories:writeYour category taxonomy
destinations:read, destinations:writeDestinations and destination links
syncs:read, syncs:writeSyncs, runs, category mappings, ruleset attachment
rules:read, rules:writeRulesets and rules
events:read, events:writeEvents and event destinations

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

License

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

Source: README.md at commit fc27208

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.1.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts