Skip to main content
Glama
splitwise-mcp

splitwise-mcp

by prakhar083

Related Servers

Alternatives to splitwise-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables local-first expense logging, editing, and analysis through natural language conversation, backed by a SQLite database and accessible via MCP over stdio.
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language management of Splitwise expenses, groups, and friends via the Model Context Protocol, with dual authentication and fuzzy name resolution.
      18
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server that lets LLM clients track, query, and summarize personal expenses using a local SQLite database.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables families to manage shared expenses, income, budgets, and financial reports through natural language, with all data stored in PostgreSQL and exposed as MCP tools to compatible LLM clients.
      -
    • A
      license
      A
      quality
      C
      maintenance
      A standalone MCP server that provides complete access to the Splitwise API, enabling natural language management of expenses, groups, friends, and notifications in MCP-compatible clients like Claude Desktop and VS Code Copilot.
      9
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for querying group expense splits and balances from a self-hosted receipt splitting app.
      -

    TDQS

    A4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Each tool targets a distinct resource and action, and the descriptions actively steer usage (e.g. get_balances before settle_up, search_expenses for text lookup). There is mild overlap between list_expenses/search_expenses and between the balance information returned by list_groups, get_group and get_balances, but the boundaries remain clear enough to choose correctly.

    Naming Consistency5/5

    Eleven of twelve tools follow a strict verb_noun snake_case pattern (get_current_user, list_groups, get_group, list_friends, get_balances, list_expenses, get_expense, search_expenses, create_expense, update_expense, delete_expense). The single outlier, settle_up, is still a recognizable verb phrase and fits the domain naturally.

    Tool Count5/5

    Twelve tools is well within the sweet spot and each one has a clear job: identity, three read views of the social graph, three expense readers, full expense CRUD, and settle_up. Nothing feels redundant or padded.

    Completeness4/5

    The core lifecycle is covered end to end: read groups/friends/balances, search and read expenses, create/update/delete expenses, and record settlements. Gaps are secondary — there is no way to create a group, add or remove group members, add friends, or comment on an expense, so some workflows dead-end at the web app.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues