Skip to main content
Glama
starling-bank-mcp

starling-bank-mcp

by domdomegg

starling-bank-mcp

MCP server for Starling Bank API integration, providing tools to interact with Starling Bank's developer API for account management and transactions.

https://github.com/user-attachments/assets/c2b23c22-bd23-487e-a4f5-c62e02280052

This is a 3rd party integration, and is not affiliated with Starling Bank.

WARNING

At time of writing, models make frequent mistakes and are vulnerable to prompt injections. As this MCP server gives the model some control of your bank account, mistakes could be costly. Use with caution and at your own risk.

Installation

Follow the instructions on install-mcp, which generates the right config for your MCP client (Claude Code, Claude Desktop, Cursor, Cline, VS Code, and more).

You'll need a Starling Bank personal access token. To create one:

Set it as STARLING_BANK_ACCESS_TOKEN (replacing the placeholder in the generated config). It'll probably begin something like eyJhbGciOiJQUzI1NiIsInppcCI6IkdaSVAifQ., and be moderately long.

If you want to be able to send payments, also see PAYMENT_SIGNING_SETUP.md.

Related MCP server: FreeAgent MCP Server

Advanced: HTTP Transport

By default, the server uses stdio transport (for Claude Desktop, Cursor, etc.). You can also run it as an HTTP server:

STARLING_BANK_ACCESS_TOKEN=eyJhb... MCP_TRANSPORT=http PORT=3000 npx starling-bank-mcp

The MCP endpoint will be available at http://localhost:3000/mcp.

WARNING

The HTTP transport has no authentication. Other processes on your machine—including websites in your browser—could potentially access the endpoint and control your bank account. Only use HTTP transport behind a reverse proxy or in another secured setup.

Contributing

Pull requests are welcomed on GitHub! To get started:

  1. Install Git and Node.js

  2. Clone the repository

  3. Install dependencies with npm install

  4. Run npm run test to run tests

  5. Build with npm run build

Releases

Versions follow the semantic versioning spec.

To release:

  1. Use npm version <major | minor | patch> to bump the version

  2. Run git push --follow-tags to push with tags

  3. Wait for GitHub Actions to publish to the NPM registry.

Available Tools

24 tools
account_balance_getGet account balanceA
Read-only

Get the balance for a specific account. Shows both cleared balance (settled transactions) and effective balance (including pending transactions).

Inputs: accountUid (required). Returns: amount, clearedBalance, effectiveBalance, acceptedOverdraft, +3 more

account_holder_getGet account holder detailsA
Read-only

Get detailed information about the logged in account holder including name, address, and other personal details.

Inputs: no named parameters. Returns: business, individual, jointAccount, accountHolder, +1 more

account_identifiers_getGet account identifiersB
Read-only

Get an account's bank identifiers (sort code, account number, BIC, IBAN, etc.)

Inputs: accountUid (required). Returns: bic, iban, bankIdentifier, accountIdentifier, +1 more

accounts_listGet all accountsA
Read-only

Get all accounts associated with the logged in account holder. This is typically the first call to make to get account information. An account holder (e.g. a person or business) can have multiple accounts (e.g. a GBP and EUR account).

Inputs: no named parameters. Returns: accounts

card_lock_updateLock or unlock cardC

Enable or disable (lock/unlock) a card

Inputs: cardUid (required), enabled (required). Returns: enabled

cards_listList all cardsA
Read-only

Get all the cards for an account holder

Inputs: no named parameters. Returns: cards

direct_debits_listList direct debitsB
Read-only

Get all direct debit mandates for an account

Inputs: accountUid (required). Returns: mandates

feed_item_attachment_downloadDownload transaction attachmentB
Read-only

Download a specific attachment from a feed item (transaction). Returns the attachment as base64 encoded data.

Inputs: accountUid (required), categoryUid (required), feedItemUid (required), feedItemAttachmentUid (required).

feed_item_attachment_uploadUpload transaction attachmentB

Upload an attachment to a feed item (transaction). Provide either base64 encoded attachment data or a file path (recommended).

Inputs: accountUid (required), categoryUid (required), feedItemUid (required), filePath, +2 more. Returns: feedItemAttachmentUid

feed_item_getGet transaction detailsA
Read-only

Get details of a specific feed item (transaction) including any attachments

Inputs: accountUid (required), categoryUid (required), feedItemUid (required). Returns: amount, source, status, country, +25 more

feed_item_note_updateUpdate transaction noteC

Update the user note for a transaction

Inputs: userNote (required), accountUid (required), categoryUid (required), feedItemUid (required). Returns: success

feed_item_spending_category_updateUpdate transaction spending categoryC

Update the spending category for a transaction

Inputs: accountUid (required), categoryUid (required), feedItemUid (required), spendingCategory (required). Returns: success

payee_createCreate new payeeC

Create a new payee (person/company you can send payments to)

Inputs: payeeName (required), payeeType (required), countryCode (required), bankIdentifier (required), +3 more. Returns: errors, success, payeeUid

payee_deleteDelete payeeC

Delete a payee

Inputs: payeeUid (required). Returns: success

payees_listList all payeesA
Read-only

Get all payees (people/companies you can send payments to) for the account holder.

Inputs: no named parameters. Returns: payees

payment_createCreate paymentC

Create a payment to an existing payee

Inputs: amount (required), reference (required), accountUid (required), categoryUid (required), +1 more. Returns: paymentOrderUid

savings_goal_createCreate savings goalC

Create a new savings goal

Inputs: name (required), currency (required), accountUid (required), target. Returns: success, savingsGoalUid

savings_goal_deleteDelete savings goalC

Delete a savings goal

Inputs: accountUid (required), savingsGoalUid (required). Returns: success

savings_goal_depositDeposit to savings goalC

Add money to a savings goal

Inputs: amount (required), accountUid (required), savingsGoalUid (required). Returns: success, transferUid

savings_goals_listList savings goalsB
Read-only

Get all savings goals for an account

Inputs: accountUid (required). Returns: savingsGoalList

savings_goal_updateUpdate savings goalC

Update an existing savings goal

Inputs: name (required), currency (required), accountUid (required), savingsGoalUid (required), +1 more. Returns: success, savingsGoalUid

savings_goal_withdrawWithdraw from savings goalC

Withdraw money from a savings goal

Inputs: amount (required), accountUid (required), savingsGoalUid (required). Returns: success, transferUid

standing_orders_listList standing ordersB
Read-only

Get all standing orders for an account category

Inputs: accountUid (required), categoryUid (required). Returns: standingOrders

transactions_listList transactionsC
Read-only

Get transaction feed items for an account category. Use the default category UID for main account transactions.

Inputs: accountUid (required), categoryUid (required), maxTransactionTimestamp (required), minTransactionTimestamp (required). Returns: feedItems

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and the entity_action naming makes intent clear. The main ambiguity is between transactions_list and the feed_item_* family, which both concern transactions, though descriptions clarify that a feed item is a transaction. savings_goal_deposit vs withdraw and payment_create vs payee_create are clearly distinguishable.

    Naming Consistency4/5

    Nearly all tools follow a consistent noun_verb pattern (accounts_list, payment_create, card_lock_update, savings_goal_delete). The only deviations are inconsistent pluralization of the entity prefix (accounts_list vs account_balance_get, savings_goals_list vs savings_goal_create), which is a minor blemish rather than a convention break.

    Tool Count4/5

    24 tools is on the heavier side but justified by the breadth of the banking domain (accounts, feed items, payees, payments, cards, direct debits, standing orders, savings goals). Each tool maps to a real operation, with little redundancy, though the set sits at the upper end of what stays manageable.

    Completeness4/5

    Coverage is strong: savings goals have full CRUD plus deposit/withdraw, feed items support read/update/attachment workflows, and read-only surfaces exist for accounts, cards, direct debits, and standing orders. Gaps remain around payments (create only, no list/cancel) and standing orders/direct debits (list only), but these are minor and workable.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers