Skip to main content
Glama
Zesty0wl

Starling Bank MCP

by Zesty0wl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Starling Bank MCP

No user-submitted related servers found.

    Related Servers

    • openbanking-mcp

      Beennnn
      A
      license
      A
      quality
      B
      maintenance
      MCP server for read-only access to bank accounts via Open Banking (DSP2/AIS). It retrieves balances, transactions, and forecasts upcoming debits to prevent overdrafts, with optional daily Todoist briefs.
      6
      1
      MIT
    • FinLynq by finlynq

      FinLynqofficial

      finlynq
      A
      license
      B
      quality
      A
      maintenance
      open-source personal finance app with a first-party MCP server. 91 HTTP tools (OAuth 2.1 + DCR) and 87 stdio tools cover transactions, budgets, accounts, portfolio analytics, FX conversion, loans, subscriptions, goals, importers, and rules. Users self-host with Docker + PostgreSQL or use the managed cloud
      89
      22
      AGPL 3.0

    • openfinance-analyst

      meloluan
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for personal finance via Open Finance, consolidating accounts and cards and answering spending questions with aggregated numbers. Provides tools for category spending, recurring subscriptions, budgets, card bills, and installment forecasts, with data stored locally in an encrypted SQLite database.
      1
      -

    • starling-bank-mcp

      domdomegg
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Starling Bank API integration, enabling AI agents to manage accounts, view transactions, and send payments via natural language.
      115 npm
      6
      MIT

    • plaid-mcp

      Studio-Saelix
      A
      license
      B
      quality
      A
      maintenance
      A read-only MCP server that connects AI clients to your own bank, credit card, loan, and brokerage data through Plaid or Teller, letting you query accounts, balances, transactions, holdings, liabilities, identity, income, and run debt avalanche/snowball payoff analysis. Credentials and access tokens stay locally in a chmod-600 SQLite file, with outbound calls limited to the provider's API.
      24
      1
      MIT

    • personal-finance-mcp

      JosueM1109
      A
      license
      A
      quality
      C
      maintenance
      Self-hosted, read-only MCP server that connects banks, credit cards, loans, and brokerage accounts via Plaid. 9 tools for balances, transactions, recurring charges, liabilities, and investment holdings.
      9
      8
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 54 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., list_transactions vs list_settled_transactions vs get_feed_changes_since), and descriptions provide guidance. However, some overlap exists: get_savings_goal vs get_savings_goal_recurring_transfer, and multiple payment history tools (list_payment_order_payments, list_payee_payments) require careful differentiation. With 54 tools, some ambiguity is inevitable, but it's manageable.

    Naming Consistency4/5

    The vast majority of tools follow a consistent verb_noun pattern (list_*, get_*, check_*, export_*, download_*). A few tools break the pattern slightly (e.g., get_financial_overview, summarise_spending, find_recurring_payments use non-standard verbs but remain descriptive), and there's a mix of British and American spellings (summarise vs list) but overall consistency is high.

    Tool Count3/5

    54 tools for a banking API is heavy and may overwhelm an agent, though each tool targets a distinct resource or operation. The count is borderline excessive; consolidation of some read-only tools (e.g., separate getters for account holder details by type) would improve usability.

    Completeness4/5

    The surface covers a wide range of banking operations: accounts, transactions, payments, direct debits, standing orders, savings goals, spaces, cards, payees, and user profiles. However, there are notable gaps: no tools for creating payees, creating direct debit mandates, or updating spending categories (recategorisation is only mentioned in list_spending_categories). Also, no tool for making payments is explicitly present (only checking payment orders), which seems like a core missing operation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources