Back to Browse

Starling Bank MCP Server

FinanceUse Caution4.8MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

4.8
Use Caution4.8High Risk

This is a well-structured MCP server for Starling Bank API integration with appropriate authentication and reasonable security practices. The server correctly requires API tokens for all operations and handles sensitive credentials via environment variables. Minor code quality observations exist around error handling breadth, but permissions align well with the financial API integration purpose and no critical vulnerabilities were identified. Supply chain analysis found 3 known vulnerabilities in dependencies (1 critical, 2 high severity). Package verification found 1 issue.

7 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

What You'll Need

Set these up before or after installing:

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

Environment variable: STARLING_BANK_ACCESS_TOKEN

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

Environment variable: STARLING_BANK_PRIVATE_KEY_UID

Optional: PEM-encoded signing key for sending payments.Required

Environment variable: STARLING_BANK_PRIVATE_KEY_PEM

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-domdomegg-starling-bank-mcp": {
      "env": {
        "STARLING_BANK_ACCESS_TOKEN": "your-starling-bank-access-token-here",
        "STARLING_BANK_PRIVATE_KEY_PEM": "your-starling-bank-private-key-pem-here",
        "STARLING_BANK_PRIVATE_KEY_UID": "your-starling-bank-private-key-uid-here"
      },
      "args": [
        "-y",
        "starling-bank-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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.

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.

Reviews

No reviews yet

Be the first to review this server!