amazing-splitwise-mcp
Related Servers
Alternatives to amazing-splitwise-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA local MCP server that exposes the Splitwise API as tools, enabling conversational management of expenses, groups, and friends. It runs entirely locally over stdio with no hosting required.445 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage Splitwise expenses through natural language, including reading balances, splitting costs, and handling authentication and rate limits automatically.7MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes every endpoint from Splitwise's public self-serve API docs as MCP tools, covering 27 operations for managing expenses, users, and groups.445 npmMIT
- AlicenseAqualityBmaintenanceEnables natural-language interaction with Splitwise to explain balances, find missing or duplicate expenses, plan settlements, and safely add expenses with confirmation.103 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language management of Splitwise expenses, groups, and friends via the Model Context Protocol, with dual authentication and fuzzy name resolution.15MIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible AI hosts to manage Splitwise accounts, including expenses, groups, friends, and balances, with built-in guards against duplicate charges and unconfirmed destructive actions.1718 PyPI1MIT
TDQS
Scored across 33 tools
The descriptions are unusually explicit, with When to Use / When NOT to Use sections, so most tools are clearly distinguishable. However, a few retrieval pairs overlap in output—splitwise_get_group_balances and splitwise_get_group both expose group debts/member balances, and splitwise_get_expense already includes comments while splitwise_get_comments is separate—so occasional misselection is possible.
All 33 tools use the same splitwise_ prefix and snake_case, with a consistent verb_noun pattern (get_, create_, update_, delete_, undelete_, add_, remove_, resolve_). Even the few non-verb forms are predictable within the set.
33 tools is well above the 3-15 typical range and exceeds the 25+ threshold for 'too many' in this dimension. While the Splitwise domain is broad and many tools map to distinct API endpoints, there are singular/batch duplicates and overlapping balance readers that could be consolidated.
The surface covers the domain broadly: CRUD plus delete/undelete for expenses and groups, comments create/read/delete, friend lifecycle, group membership, balances, categories, currencies, notifications, user profile, and resolve helpers. No obvious lifecycle gap is apparent; missing update operations such as group rename or comment edit appear unsupported by the Splitwise API.