MCP.so
Sign In

SynciVerifiedFeatured

@Synci

About Synci

Synci connects your real bank, brokerage, and crypto-exchange accounts to AI assistants, read-only. Ask about balances, transactions, holdings, and spending across all your accounts in one place.

Connection details

https://api.synci.io/mcp

Setup

claude mcp add synci --transport http https://api.synci.io/mcp

Overview

Your financial data, readable by your AI assistant

Synci gives you ownership of your banking and financial data: connect your banks, brokerages or crypto exchanges once, then fetch, transform, and transfer your financial data anywhere. The Synci MCP server brings that data to AI assistants, giving them secure, strictly read-only access to your real financial accounts so you can ask questions a spreadsheet can't answer quickly:

  • "What did I spend on groceries last month?"
  • "Which subscriptions am I paying for, and what do they cost per year?"
  • "How is my portfolio allocated across stocks, ETFs, and crypto?"
  • "Compare my checking account balance today with the start of the month."
  • "Are any of my bank connections failing?"

Coverage

Synci aggregates accounts across thousands of institutions:

  • Banks in Europe and the UK via GoCardless Bank Account Data
  • Banks in New Zealand via Akahu
  • Investment brokerages and crypto exchanges via SnapTrade

All connected accounts are visible through one MCP server, in their native currencies.

Tools

  • list_accounts — every connected financial account (bank, investment, crypto) with its institution, currency, category, and latest balances
  • get_account_balance — recent balance snapshots for one account, with timestamps so the assistant knows how fresh each figure is
  • list_transactions — transactions across accounts or for one account, filterable by date range; includes merchant, amount, booking status, and enrichment where available
  • list_holdings — investment and crypto positions (symbol, quantity, market value) held in brokerage and exchange accounts
  • list_connections — your provider connections and their health status

Security and privacy

  • Strictly read-only. The server cannot create, modify, or delete anything. Not in Synci and not at your bank. There is no write surface.
  • OAuth 2.1 sign-in. Clients authenticate with authorization-code + PKCE and dynamic client registration; you approve access in your browser with your Synci login. No API keys to copy around, and access is revocable from your Synci dashboard at any time.
  • Scoped tokens. MCP tokens carry a dedicated scope that grants nothing beyond these read tools; they are rejected by the rest of the Synci API.
  • Sensitive identifiers stay out of reach. IBANs, account numbers, card numbers, phone numbers, and owner names are never returned to the assistant.
  • Your data only. Every tool is scoped to the authenticated user's own accounts.

Good to know

  • Data reflects the most recent provider sync rather than real-time values; balance responses include an as_of timestamp so assistants can tell you how fresh a number is.
  • Requires a Synci account with an active subscription and at least one connected institution.
  • Remote server (Streamable HTTP) at https://api.synci.io/mcp

Docs: https://docs.synci.io · Help: https://help.synci.io

Frequently asked questions

What is the Synci remote MCP server?

The Synci remote MCP server is a hosted Model Context Protocol endpoint at https://api.synci.io/mcp, so AI assistants can connect to it without installing or running anything locally.

How do I connect to the Synci MCP server?

Add the endpoint https://api.synci.io/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

Does the Synci MCP server require authentication?

Yes. Synci uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

Which transport does the Synci MCP server use?

Synci exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments