Skip to main content
Glama
Open Banking MCP Server

Open Banking MCP Server

by tkom04

Open Banking MCP Server

A Model Context Protocol (MCP) server for Open Banking integration with TrueLayer API.

🚀 Quick Start

1. Setup Credentials

Copy your real credentials to mcp.local.json (kept out of version control) or export them as environment variables before running the server. The committed mcp.json intentionally keeps placeholder values so no secrets are stored in the repo:

{
"mcpServers": {
    "openbanking-mcp": {
      "command": "py",
      "args": ["server.py"],
      "cwd": "C:\\1 Projects\\Cursor Projects\\GPT Experimentation\\OPEN BANKING MCP BUISNESS\\openbankingMCP",
      "env": {
        "TRUELAYER_CLIENT_ID": "your-real-client-id",
        "TRUELAYER_CLIENT_SECRET": "your-real-client-secret"
      }
    }
  }
}

Alternatively, set the variables directly in your shell or process manager (example shown for POSIX shells):

export TRUELAYER_CLIENT_ID="your-real-client-id"
export TRUELAYER_CLIENT_SECRET="your-real-client-secret"

2. Install Dependencies

# No additional dependencies required - uses Python standard library

3. Test the Server

# Test minimal server
echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/list", "params": {}}' | py minimal_mcp.py

# Test full server
echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/list", "params": {}}' | py server.py

4. Configure Cursor

Use mcp.local.json for your local Cursor configuration (contains real credentials).

Related MCP server: monzo-mcp

🛠️ Available Tools

  • get_accounts: List all bank accounts

  • get_transactions: Get transaction history for a specific account and date range

🔒 Security

  • Real credentials are stored in mcp.local.json (gitignored)

  • Placeholder credentials in mcp.json for version control

  • Never commit real API keys or secrets

🐞 Debugging

If MCP tools don't appear in Cursor:

  1. Check Cursor Developer Console (Ctrl+Shift+I)

  2. Look for startup messages: 🚀 OpenBanking MCP server starting...

  3. Verify Python path and working directory in MCP config

  4. Test server manually outside Cursor first

Available Tools

9 tools
complete_code_exchangeB

Complete PKCE OAuth authorization code exchange with state validation.

Inputs: code (required), state (required). Returns: content

exchange_codeA

Exchange OAuth authorization code for access and refresh tokens (legacy alias).

Inputs: code (required). Returns: content

export_hmrc_csvA

Export transactions as HMRC-ready CSV with categorization and summary.

Inputs: end_date (required), account_id (required), start_date (required), filename. Returns: content

get_accountsB

List all user bank accounts.

Inputs: no named parameters. Returns: content

get_transactionsB

Get transactions for a specific account within a date range.

Inputs: end_date (required), account_id (required), start_date (required), page, +2 more. Returns: content

list_accountsA

Return 1-2 dummy accounts with proper schema validation.

Inputs: no named parameters. Returns: content

list_consentsA

List all active user consents with their purposes and expiration dates.

Inputs: no named parameters. Returns: content

list_transactionsD

Read sample CSV, normalize rows → Transaction[] with schema validation.

Inputs: end_date (required), account_id (required), start_date (required). Returns: content

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.8/5.0

    Scored across 9 tools

    Disambiguation2/5

    exchange_code and complete_code_exchange overlap almost entirely (one is a legacy alias), and get_accounts/list_accounts plus get_transactions/list_transactions have similar names but differ in real vs. dummy behavior, creating confusion. An agent could easily select the wrong tool without careful description inspection.

    Naming Consistency3/5

    The pattern is mostly verb_noun, but the use of both get_ and list_ prefixes for closely related actions, along with exchange_code versus complete_code_exchange, shows inconsistent verb choice. The 'legacy alias' note further muddies the name convention.

    Tool Count5/5

    With 9 tools, the server is well-scoped for Open Banking operations covering auth, accounts, transactions, consents, and export. Each tool has a place, and the count is neither too small nor excessive.

    Completeness4/5

    The surface covers the core lifecycle: OAuth authorization, code exchange, account listing, transaction retrieval, CSV export, and consent listing. Notable gaps include consent revocation and token refresh, which are minor but would round out the workflow.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables read-only access to personal bank accounts via the TrueLayer API, allowing querying of accounts, balances, transactions, and generating financial analytics such as spending by category, subscriptions, and monthly summaries.
      9
      1
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables interaction with Monzo bank accounts for balance checking, transaction management, pot operations, and reconciliation through natural language.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to interact with Up Bank accounts and transactions, including reading balances, summarizing spending, and categorizing or tagging transactions.
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude to read UK bank account data—balances, transactions, cards, standing orders, direct debits, and identity—through TrueLayer's Data API, with local caching and optional live refreshes. It is read-only by design, requiring consent and never moving money.
      12
      1
      MIT