Skip to main content
Each generated MCP tool corresponds to an API v2 operation. The AI chooses tools from your request. The server’s tools/list response is the authoritative input schema, filtered to your permissions.

Available operations

For permissions, see scopes. For tools that combine several calls, see workflows.

Tool arguments and pagination

Use the exact names in the tool schema; they differ between operations. Copy public ids returned by discovery tools, not database UUIDs, account numbers, or names. Replace these illustrative ids with ids from your own responses. For a bulk balance read, call list_balances with {"account":["acct_9Lk2Mn4pQr6sTu8vWx1yZb","acct_3Cd5Ef7gHi9jKl1mNo2pQr"]}. It accepts up to 100 banking-account ids. Check the account’s category first. Balances are banking-only, not available for brokerage or Documents accounts. Product details are available only for Australian Fiskil accounts; Plaid and Akahu return not_supported, while brokerage and Documents return wrong_endpoint_for_category. Use holdings and trades for brokerage accounts. account_overview uses list_balances to collect banking balances across accounts. For lists, limit is 1–100 (default 20). Extract the opaque page query parameter from next_page_url and pass it to the same tool. Stop when next_page_url is null. Do not invent a token or pass the whole URL. Filters are locked to the first call: omit optional filters on later pages, retain required arguments such as account for holdings and trades, and do not change their values. Start a new walk to change filters. Transaction dates accept YYYY-MM-DD or RFC 3339 timestamps with a timezone. A bare date is an inclusive calendar boundary in your Redbark timezone, matching the returned transaction date; an RFC 3339 value is an instant. from must be on or before to. Omitting from selects the last 30 days, including for Documents accounts. Request explicit dates for older imports. Banking history is limited to seven years; Documents imports have no history floor. list_transactions and get_transaction return the same transaction fields as API v2, including reference and extended_description. Each is null when unavailable; neither is guaranteed to be unique.
Do not use v1 aliases such as accountId, accountIds, connectionId, or offset. If a call returns invalid_arguments, correct the named argument using the current schema before retrying. See troubleshooting.

Default and admin toolsets

The generated registry contains 63 core tools and 19 admin tools. Composite tools and guides and get_profile, which identifies the connected Redbark account, are listed alongside them. The server only lists tools permitted by your scopes. The admin toolset adds list_api_keys, create_api_key, get_api_key, update_api_key, revoke_api_key, rotate_api_key, list_consents, get_consent, list_sync_category_mappings, set_sync_category_mappings, reset_categories, enable_event_destination, disable_event_destination, ping_event_destination, rotate_event_destination_secret, rotate_destination_secret, enable_destination, duplicate_ruleset, and reorder_ruleset_rules. Enable it by adding ?toolsets=admin to your server URL:
This does not grant additional permissions. API-key management is not available over OAuth.