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 library3. 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.py4. Configure Cursor
Use mcp.local.json for your local Cursor configuration (contains real credentials).
🛠️ Available Tools
get_accounts: List all bank accountsget_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.jsonfor version control - Never commit real API keys or secrets
🐞 Debugging
If MCP tools don't appear in Cursor:
- Check Cursor Developer Console (
Ctrl+Shift+I) - Look for startup messages:
🚀 OpenBanking MCP server starting... - Verify Python path and working directory in MCP config
- Test server manually outside Cursor first
