About Fio Bank MCP
Fio Bank MCP is an MCP server that lets AI assistants access account information from the FIO Bank API in the Czech Republic. Its transaction tool retrieves transactions for a requested date range along with account and payment details.
Key features
- 01Retrieve transactions for a date range
- 02Return account details and balance
- 03Include payment and transaction information
- 04Accept an API token or environment variable
Use cases
- 01Review FIO Bank transactions for a selected period
- 02Provide account and payment details to an AI assistant
MCP support
The MCP server exposes the fio_get_transactions tool, which accepts a date range and returns account information and transactions. It uses a supplied token or the FIO_API_TOKEN environment variable.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEFIO Bank MCP Server
An MCP (Model Context Protocol) server for FIO Bank API in the Czech Republic. Allows AI assistants like Claude to access FIO Bank account transactions.
Installation
pnpm install
pnpm build
Configuration
Getting an API Token
- Log in to your FIO Bank internet banking
- Go to Settings → API
- Create a new token (requires SMS or push notification)
- Wait 5 minutes before using the token
Token Properties
- Each token is valid for one account only
- Maximum validity: 180 days
- Can auto-renew on each login to internet banking
Usage
With Claude Desktop
Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"fio-bank": {
"command": "node",
"args": ["/path/to/fio-bank-mcp/dist/index.js"],
"env": {
"FIO_API_TOKEN": "your-64-character-token-here"
}
}
}
}
Available Tools
fio_get_transactions
Get account transactions for a specific date range.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
dateFrom | string | Yes | Start date (YYYY-MM-DD) |
dateTo | string | Yes | End date (YYYY-MM-DD) |
token | string | No | API token (uses FIO_API_TOKEN env var if not provided) |
Returns:
- Account info (IBAN, BIC, balance)
- List of transactions with:
- Transaction ID, date, amount, currency
- Counter account (number, name, bank)
- Payment symbols (variable, constant, specific)
- Message for recipient, comments
- Transaction type
Testing Locally
Use the MCP Inspector to test the server with a web UI:
npx @modelcontextprotocol/inspector node dist/index.js
This opens a browser where you can see available tools, call them with parameters, and view responses.
To pass the API token:
FIO_API_TOKEN=your-token npx @modelcontextprotocol/inspector node dist/index.js
API Rate Limits
1 request per 30 seconds per token. The server automatically waits if needed.
Data Access
- Data up to 90 days old: accessible immediately
- Data older than 90 days: requires temporary unlock in internet banking (Settings → API → click lock icon, valid for 10 minutes)
Error Codes
| Code | Description |
|---|---|
| 404 | Invalid URL or token |
| 409 | Rate limit exceeded (wait 30 seconds) |
| 413 | Too many transactions in response |
| 422 | Invalid request data |
| 500 | Internal server error |
Development
pnpm install # Install dependencies
pnpm build # Build TypeScript
pnpm lint # Run ESLint
pnpm typecheck # Type check without emitting
Resources
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.