bg-mcp
Related Servers
Alternatives to bg-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying linked bank account balances and transactions through MCP tools, with manual sync and read-only access from any MCP client.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables reading C6 Bank account balances, statements, credit card bills, and investments via Open Finance Brasil. It is read-only and regulated by the Central Bank of Brazil.MIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only access to Wise Business API profiles, balances, account statements, and card-spending data through MCP tools.MIT
- AlicenseBqualityCmaintenanceEnables MCP clients such as Claude Code, Claude Desktop, and Cursor to read a user's own Open Finance Brasil data through Meu Pluggy — accounts, balances, transactions, card bills, investments, and spending by category — while remaining strictly read-only and never moving money or storing data.7MIT
- AlicenseBqualityCmaintenanceEnables read-only access to Questrade accounts, portfolios, market data, transactions, technical analysis, and order history through MCP.11MIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only access to personal European bank accounts through Enable Banking, allowing MCP clients to list accounts, retrieve balances, search and summarize transactions, and estimate spending with bounded, privacy-preserving tools.MIT
TDQS
Scored across 14 tools
Tools are scoped by resource and action, with clear separation between account listing, detail, transaction listing, and search. Minor overlap exists (e.g., pension balances in bg_get_account vs bg_get_pension, or spending aggregates in bg_spending_summary vs bg_get_card_categories), but descriptions differentiate them well.
Consistent bg_ prefix and snake_case throughout, with predictable verbs like list, get, and search, plus a clear bg_login_* auth sequence. Slight deviations such as bg_spending_summary and bg_session_status (noun phrases) are still readable and stylistically consistent.
14 tools is well within the typical 3-15 range for a banking integration. Each tool covers a distinct slice of the workflow, from authentication to account and transaction queries, with no redundant tools.
Core read-only banking workflows are covered: authentication, account listing/detail, savings and card transactions, card statements, categories, pension, spending summary, and search. Minor gaps exist (e.g., no explicit savings account statement or data-sync/refresh tool), but agents can work around them.