splitwise-mcp
Related Servers
Alternatives to splitwise-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables conversational control of Splitwise accounts through Claude AI, allowing users to add expenses, check group balances, record settlements, and manage payment splits using natural language commands. Supports multiple currencies and flexible splitting methods including equal, exact, and percentage-based divisions.1MIT
- AlicenseAqualityBmaintenanceEnables natural-language interaction with Splitwise to explain balances, find missing or duplicate expenses, plan settlements, and safely add expenses with confirmation.108 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage Splitwise expenses through natural language, including reading balances, splitting costs, and handling authentication and rate limits automatically.7MIT
- AlicenseAqualityCmaintenanceEnables managing Splitwise expenses and generating premium spending analytics with category breakdowns, trends, and settlement optimization through natural language.42MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for Splitwise. Enables creating and managing expenses, splits, and groups directly from Claude without manual entry.-
- AlicenseNot gradedqualityDmaintenanceEnables natural language management of Splitwise expenses, groups, and friends via the Model Context Protocol, with dual authentication and fuzzy name resolution.19MIT
TDQS
Scored across 31 tools
Most tools have clearly distinct purposes, but receipt attachment can be done via sw_attach_receipt or sw_update_expense/sw_create_expense, and sw_batch overlaps with individual write tools. Descriptions help mitigate, but minor ambiguity remains.
Tools follow a consistent sw_ verb_noun pattern (e.g., sw_get_user, sw_list_groups, sw_create_expense), with only minor deviations like sw_healthcheck and sw_confirm that lack a noun component. Still very readable and predictable overall.
With 31 tools, the server exceeds the 25+ threshold for 'too many' tools. While each tool serves a role in the broad Splitwise domain, the surface could be consolidated to reduce cognitive load and improve usability.
Core CRUD operations for expenses, groups, friends, comments, and receipts are well-covered, plus read-only categories, currencies, and notifications. Minor gaps exist (e.g., no group or friend update), but these are not critical for typical workflows.