io.github.domdomegg/starling-bank-mcp

Official

by domdomegg · TypeScript

Starling Bank

Allow AI systems to view and control your Starling Bank account via MCP.

View and control Starling Bank accounts programmatically.

Topics

mcp-servermodel-context-protocol

README.md3 KBView on GitHub

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:

Sign up for a Starling Developers account
Link your Starling Bank account to your Starling Developer account
Create the access token, selecting the scopes based on what you want the AI system to be able to access

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.

Advanced: HTTP Transport

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

bash

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:

Install Git and Node.js
Clone the repository
Install dependencies with npm install
Run npm run test to run tests
Build with npm run build

Releases

Versions follow the semantic versioning spec.

To release:

Use npm version <major | minor | patch> to bump the version
Run git push --follow-tags to push with tags
Wait for GitHub Actions to publish to the NPM registry.

Install

Configuration

Environment variables

STARLING_BANK_ACCESS_TOKENrequiredsecret

Starling Bank personal access token. Sign up for the Starling Developer Portal, link your account, and create a Personal Access Token.

STARLING_BANK_PRIVATE_KEY_UIDsecret

Optional: Key UID of the signing key for sending payments.

STARLING_BANK_PRIVATE_KEY_PEMsecret

Optional: PEM-encoded signing key for sending payments.

claude_desktop_config.json

{
  "mcpServers": {
    "starling-bank-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "starling-bank-mcp@1.2.0"
      ],
      "env": {
        "STARLING_BANK_ACCESS_TOKEN": "<YOUR_STARLING_BANK_ACCESS_TOKEN>",
        "STARLING_BANK_PRIVATE_KEY_UID": "<YOUR_STARLING_BANK_PRIVATE_KEY_UID>",
        "STARLING_BANK_PRIVATE_KEY_PEM": "<YOUR_STARLING_BANK_PRIVATE_KEY_PEM>"
      }
    }
  }
}