Skip to main content
The Redbark MCP server connects Claude, ChatGPT, Cursor, and other AI assistants to your Redbark account. Ask about accounts, balances, transactions, and brokerage data, or manage syncs, destinations, rules, and categories. Model Context Protocol lets AI tools call external services. Redbark’s MCP server exposes API v2 operations as tools, plus workflows that combine several calls.

​
Get connected

Add this URL to your AI client and complete the OAuth consent screen:
Follow the setup guide for Claude, Claude Code, Cursor, or ChatGPT. Read access and security for plan requirements and permissions.

​
What you can ask

  • “What bank accounts do I have connected?”
  • “What is my current balance across my banking accounts?”
  • “What did I spend on groceries this month?”
  • “Show me my brokerage holdings and P&L”
  • “Create a sync from my everyday account to the Budget sheet and run it now”
  • “Add a rule that tags Uber transactions as Travel”
MCP reads data on demand and returns it to your AI client. Unlike a scheduled destination such as Google Sheets or YNAB, it does not create a recurring export. Banking reads may use Redbark’s short-lived gateway cache; see data handling.

​
Browser tools

Browsers implementing the experimental WebMCP API can use page-specific tools directly on Redbark’s website. These are separate from the remote MCP server above. Other browsers behave normally. On public pages, browser tools can search supported connections and compare plans. In the signed-in app, they can search institutions, prepare a connection or sync for review, inspect sync status, and request a manual run. Preparing a connection or sync only fills the visible interface. Connecting an account, creating a sync, and running a sync still require your confirmation.

​
Explore MCP