starling-bank-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STARLING_BANK_ACCESS_TOKEN | Yes | Your Starling Bank personal access token. Create one at https://developer.starlingbank.com/personal/token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| accounts_listA | 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). |
| account_balance_getA | Get the balance for a specific account. Shows both cleared balance (settled transactions) and effective balance (including pending transactions). |
| transactions_listC | Get transaction feed items for an account category. Use the default category UID for main account transactions. |
| account_holder_getA | Get detailed information about the logged in account holder including name, address, and other personal details. |
| payees_listA | Get all payees (people/companies you can send payments to) for the account holder. |
| account_identifiers_getB | Get an account's bank identifiers (sort code, account number, BIC, IBAN, etc.) |
| cards_listA | Get all the cards for an account holder |
| card_lock_updateC | Enable or disable (lock/unlock) a card |
| direct_debits_listB | Get all direct debit mandates for an account |
| standing_orders_listB | Get all standing orders for an account category |
| feed_item_getA | Get details of a specific feed item (transaction) including any attachments |
| feed_item_spending_category_updateC | Update the spending category for a transaction |
| feed_item_note_updateC | Update the user note for a transaction |
| feed_item_attachment_uploadB | Upload an attachment to a feed item (transaction). Provide either base64 encoded attachment data or a file path (recommended). |
| feed_item_attachment_downloadB | Download a specific attachment from a feed item (transaction). Returns the attachment as base64 encoded data. |
| payment_createC | Create a payment to an existing payee |
| payee_createC | Create a new payee (person/company you can send payments to) |
| payee_deleteC | Delete a payee |
| savings_goals_listB | Get all savings goals for an account |
| savings_goal_createC | Create a new savings goal |
| savings_goal_updateC | Update an existing savings goal |
| savings_goal_deleteC | Delete a savings goal |
| savings_goal_depositC | Add money to a savings goal |
| savings_goal_withdrawC | Withdraw money from a savings goal |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
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.
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.
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.
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.