io.github.SamuelMoraesF/mcp-organizze
Related Servers
Alternatives to io.github.SamuelMoraesF/mcp-organizze
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceAn MCP server providing full integration with the Lunch Money API to manage financial data including transactions, budgets, assets, and categories. It enables AI assistants to perform CRUD operations on financial records through a standardized HTTP interface.26MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for the Pluggy Open Finance Brazil API, enabling connection to bank accounts and management of financial data including transactions, accounts, investments, and payment intents through natural language.10 npmMIT
- AlicenseAqualityAmaintenanceAn MCP server implementation that provides programmatic access to personal finance data through LunchMoney's API, enabling AI assistants to manage transactions, budgets, categories, and assets.5910,833 npm107MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for personal finance via Open Finance, consolidating accounts and cards and answering spending questions with aggregated numbers. Provides tools for category spending, recurring subscriptions, budgets, card bills, and installment forecasts, with data stored locally in an encrypted SQLite database.1-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact directly with Lunch Money's financial API, allowing users to query transactions, access budget information, and perform financial analysis through natural language.-
- AlicenseNot gradedqualityFmaintenanceMCP server to connect Conta Azul ERP to AI agents, enabling natural language management of clients, products, sales, contracts, finances, and NF-e via OAuth.11MIT
TDQS
Scored across 33 tools
Most tools are clearly separated by resource and action, but the budget trio (getBudgets, getYearBudgets, getMonthBudgets) and invoice trio (getCreditCardInvoices, getCreditCardInvoice, getCreditCardInvoicePayment) are closely related and could be misselected without careful reading. Plural vs singular naming helps, but descriptions are needed to fully disambiguate.
All tools follow a consistent verb + resource convention, using plural for list operations and singular for detail operations (e.g., getAccounts vs getAccount). The pattern is uniform across all resources, with no mixed casings or irregular verbs.
With 33 tools, the server is well beyond the typical well-scoped range of 3-15. The count reflects a full CRUD API for many resources, but it feels heavy and could be consolidated (e.g., merging budget list variants).
Accounts, credit cards, transactions, transfers, and categories have full CRUD coverage, but budgets are read-only with no create/update/delete operations. Invoice management is also limited to reading and payment lookup, leaving notable gaps in budget management workflows.