is-bankasi-mcp
# is-bankasi-mcp
MCP server for Isbank (Is Bankasi) developer API (Turkey). Access accounts, balances, transactions, exchange rates, transfers, and credit cards via OAuth 2.0 authentication.
## Tools (8)
| Tool | Description |
|---|---|
| `get_accounts` | List bank accounts |
| `get_account_balance` | Get account balance |
| `get_transactions` | Get account transactions |
| `get_exchange_rates` | Get current exchange rates |
| `initiate_transfer` | Initiate EFT/FAST/havale transfer |
| `get_transfer_status` | Check transfer status |
| `get_credit_cards` | List credit cards |
| `get_card_transactions` | Get credit card transactions |
## Quick Start
```json
{
"mcpServers": {
"isbank": {
"command": "npx",
"args": ["-y", "@theyahia/is-bankasi-mcp"],
"env": {
"ISBANK_CLIENT_ID": "<YOUR_CLIENT_ID>",
"ISBANK_CLIENT_SECRET": "<YOUR_CLIENT_SECRET>"
}
}
}
}
```
## Environment Variables
| Variable | Required | Description |
|---|---|---|
| `ISBANK_CLIENT_ID` | Yes | OAuth client ID from Isbank developer portal |
| `ISBANK_CLIENT_SECRET` | Yes | OAuth client secret from Isbank developer portal |
## Demo Prompts
- "Show me all my Isbank accounts"
- "What is the balance of account ACC001?"
- "List transactions from March 2026 for my main account"
- "What is the current USD/TRY exchange rate?"
- "Transfer 5000 TRY to IBAN TR123456 via FAST"
- "Show my credit card transactions for this month"
## License
MIT
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: accounts, balances, transactions, exchange rates, transfers, and cards are clearly separated. There is no overlap between getting account transactions versus card transactions, and transfer initiation/status checking are unambiguous.
Seven of eight tools follow the 'get_' verb-noun pattern, making the set highly predictable. 'initiate_transfer' deviates by using an action verb rather than 'get_', which is a minor inconsistency but does not cause confusion.
With 8 tools, the server is well-scoped for a banking API covering accounts, transactions, cards, exchange rates, and transfers. Each tool serves a distinct purpose, and the number feels appropriate without being overwhelming or sparse.
The toolset covers core banking workflows: listing accounts, checking balances, viewing transactions, managing transfers, and accessing card data. Minor gaps exist, such as lacking a dedicated transfer history or card details endpoint, but agents can work around these using existing tools.