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
- AlicenseAqualityBmaintenanceEnables 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.15MIT
TDQS
Scored across 28 tools
Tools are organized around distinct resources (user, group, friend, expense, comment, receipt, categories, currencies) with clear verb distinctions, and the get vs list vs create vs update vs delete vs undelete pattern is easy to follow. The only real overlap is that sw_update_expense can also attach a receipt, which duplicates part of sw_attach_receipt's purpose, and sw_get_user vs sw_get_current_user require reading descriptions to separate.
Every tool uses the same sw_ prefix and a predictable verb_noun pattern (sw_get_x, sw_list_x, sw_create_x, sw_update_x, sw_delete_x, sw_undelete_x), including compound cases like sw_add_user_to_group. No mixing of camelCase or alternative verb styles.
28 tools is on the heavy side and sits at the upper edge of the 16-25 'heavy' band, but each tool maps to a genuine Splitwise operation (soft-delete/undelete pairs, receipt handling, lookup tables). The surface feels slightly large rather than padded, so it is defensible.
Coverage is strong: full CRUD plus soft-delete/undelete for groups, expenses and comments, friendship management, plus support lookups (categories, currencies, notifications, healthcheck). Minor gaps exist — there is no update_group or update_friend, and user creation is intentionally delegated to the app, which are workable omissions.