https://api.ledgersyncappv2.com/mcp
Sandbox
Add this address as a second connector, then connect FinBank, MX Bank or Ledgersync Bank with the test sign-ins in Testing in sandbox.Who can connect
- Firms that use the LedgerSync app: the firm owner signs in with the LedgerSync app login (email or username, password, and the two-step code if the account has one). No new plan.
- New firms: on the LedgerSync sign-in page, a new email gets Create your LedgerSync account. The owner
fills in the sign-up form and pays on the order page, then our team reviews the firm once. Until then the
connector answers
firm_under_reviewwhen asked to connect a bank; clients can be added. On live, sign-up needs a work email. - Approved developer accounts: type the developer portal email on the LedgerSync sign-in page. It sends you to the developer portal sign-in. The account must be approved for that environment; live also needs the payment step. An application still waiting for its first approval cannot connect yet.
- Only the firm owner can connect for now. A teammate gets For now, only the firm owner can use LedgerSync in their own Claude or ChatGPT.
- ChatGPT needs a paid plan (Plus or higher), the web version on chatgpt.com, and Developer mode turned on (Settings, then Security and login). Without Developer mode, Create MCP App does not appear. On ChatGPT Business, Enterprise or Edu, only the workspace admin can add it for everyone.
- On Claude Team and Enterprise, an Owner first adds it under Organization settings > Connectors (Add, then Custom, then Web). Members then open Connectors, find LedgerSync and click Connect. The Claude Free plan allows one custom connector. Once added, it also works in Claude Desktop, the Claude mobile apps, and Claude Code signed in with the same account.
- AI apps other than Claude and ChatGPT are not supported yet (they are blocked). Ask support if you need one.
Tools
The live connector offers 17 tools. The sandbox connector offers the first 15 (no desktop app tools).
A bank or connection that needs the desktop app for refreshes carries
requires_desktop_app: true in the
search, connection and refresh-status results; the field is left out otherwise. A connection that is not
working on such a bank also gets a next_step that says so.
Security
Security
- Bank sign-ins only happen on LedgerSync pages. Connect links expire after 72 hours.
- Statement download links expire after 10 minutes and work once; if a download fails, ask for a new link.
- The connector cannot see or change API keys, webhooks or account settings.
- Firms that sign in with the LedgerSync app login: changing the LedgerSync password, or turning off two-step sign-in, turns off every AI app connected with that login within a minute.
- Developer accounts: disconnecting in the portal’s Connected apps page cuts the app off at once; adding it again signs in fresh. The page lists only the apps of the environment picked in the portal’s Sandbox / Live switch, so pick Live to see the live connector’s apps. Anyone with the account’s LedgerSync login can add it again. To turn it off for good, email support: support turns off the account’s access for that environment, which stops every connected app and, on live, the account’s API keys too.
- Linking the desktop app needs the code the app shows, and the AI asks you to confirm first. The code is never logged or repeated back.
- The desktop app is linked to the account owner’s LedgerSync login, the one the connector acts as. Linking a computer replaces any computer linked before: only one computer is connected at a time. Every link is recorded and the LedgerSync team is alerted at once.
Refreshes and limits
Refreshes and limits
- LedgerSync refreshes every working connection about once a day. A refresh you ask for takes a few minutes; see Keeping data fresh.
- A connection refreshed in the last 30 minutes is skipped unless you ask for a new pull anyway.
- Each AI app can start 50 refreshes a day on live (20 on sandbox). They also count against your firm’s daily budget of 500 on live (100 on sandbox), shared with API keys, which is the number the AI shows as refreshes left.
- Per connected AI app: 50 new clients a day, 30 connect links an hour, and 120 tool calls a minute on sandbox (60 on live).
- Long lists of connections, accounts, transactions and statements come back in pages.
- A refresh stopped by the desktop app (
desktop_app_requiredordesktop_app_route_choice) never reached the bank. It counts against neither daily refresh limit, and the 30-minute skip does not block trying again. - Linking the desktop app: 10 tries an hour and 20 a day per LedgerSync account (UTC hours and days), whether the code works or not. A code that is not 7 letters or digits is refused without counting.
Error codes
Error codes
Every error has a
code, the same as the API’s (see Errors). Access errors (except
firm_under_review, whose message is the whole sentence), desktop app errors and the per-minute limit
also carry a next_step sentence the AI reads out. So does a connection
or refresh stopped by the desktop app, in its result.The 15 codes you are most likely to see are listed below. The connector can also answer
invalid_request, internal_error, idempotency_conflict or upstream_unavailable (LedgerSync could not
check the firm just now; try again in a minute).