Connects Claude to Starling Bank's developer API so you can check balances, view transactions, and manage your account through conversation. Requires a personal access token with scoped permissions, which you generate through Starling's developer portal. The README warns that current models make mistakes and are vulnerable to prompt injection, so you're giving AI real control over financial operations. Payment signing requires additional setup documented separately. Built as a third party integration with stdio transport by default, though it supports HTTP mode if you need it behind a reverse proxy. Reach for this when you want to automate banking queries or build financial workflows, but understand the risks of letting an LLM touch your account.
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.
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.
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.
Pull requests are welcomed on GitHub! To get started:
npm installnpm run test to run testsnpm run buildVersions follow the semantic versioning spec.
To release:
npm version <major | minor | patch> to bump the versiongit push --follow-tags to push with tagsSTARLING_BANK_ACCESS_TOKEN*secretStarling Bank personal access token. Sign up for the Starling Developer Portal, link your account, and create a Personal Access Token.
STARLING_BANK_PRIVATE_KEY_UIDsecretOptional: Key UID of the signing key for sending payments.
STARLING_BANK_PRIVATE_KEY_PEMsecretOptional: PEM-encoded signing key for sending payments.