Business operationsPublic source

Banking MCP Server

Unified banking MCP server with 15 tools across 3 backends — Plaid (US/Canada/EU), Mono (Africa), and Open Banking (UK/EU PSD2). Accounts, transactions, balances, payments, identity, and statements.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Unified schema — agents see consistent types regardless of backend

Multi-region — Plaid (US/Canada/EU), Mono (NG/KE/GH/ZA), Open Banking (UK/EU)

Financial governance — payment initiation requires approval gates

No credential exposure — tokens stay in env vars

Single binary — no Node.js, no Python

Architecture

How Banking MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Banking MCP Server

Validates the request and owns 15 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Banking MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Banking MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

15 named tools

list_accounts

List linked bank accounts

read only

get_account

Get a bank account by ID with balance

read only

get_balances

Get real-time balances for all linked accounts

read only

list_transactions

List transactions for an account with date range

read only

get_transaction

Get a single transaction by ID

read only

search_transactions

Search transactions by description, amount, or category

read only

categorize_transaction

Get or update the category of a transaction

read only

get_identity

Get account holder identity (name, address, email)

read only

list_institutions

List supported financial institutions

read only

get_institution

Get details about a financial institution

read only

initiate_payment

Initiate a bank transfer/payment (draft, requires approval)

financial action

get_payment_status

Get the status of a payment/transfer

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

14 read only1 financial action

Financial governance — payment initiation requires approval gates

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-banking --features all-backends

MCP client configuration

export PLAID_CLIENT_ID="your-client-id"
export PLAID_SECRET="your-secret"
export PLAID_ACCESS_TOKEN="access-sandbox-xxx"
export PLAID_ENV="sandbox"  # sandbox | development | production

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Api Reference ↗docs/api-reference.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring