Starling Bank MCP Server

Allow AI systems to view and control your Starling Bank account via MCP. The starling bank mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

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

Adding it to your client

The server ships on npm as starling-bank-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration

You will need one environment variable: STARLING_BANK_ACCESS_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by domdomegg; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the starling bank mcp server does with a few real requests.