Skip to main content
Glama
chrischall

splitwise-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to splitwise-mcp

No user-submitted related servers found.

    Related Servers

    • Splitwise MCP Server

      bhvkmuni
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      1
      MIT

    • goodwill-mcp

      dc28vivek
      A
      license
      A
      quality
      B
      maintenance
      Enables natural-language interaction with Splitwise to explain balances, find missing or duplicate expenses, plan settlements, and safely add expenses with confirmation.
      10
      151 npm
      MIT

    • open-splitwise

      nnishad
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to manage Splitwise expenses through natural language, including reading balances, splitting costs, and handling authentication and rate limits automatically.
      7
      MIT

    • ExpensifyAI

      udaysrinu
      A
      license
      A
      quality
      B
      maintenance
      Enables managing Splitwise expenses and generating premium spending analytics with category breakdowns, trends, and settlement optimization through natural language.
      42
      MIT

    • splitwise-mcp

      tarunn2799
      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.
      13
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 27 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair (group, friend, expense, comment, user, category, currency, receipt, notification, healthcheck). Singular/plural naming clearly separates single-item retrieval from list operations, and current_user vs get_user avoids self/other confusion.

    Naming Consistency5/5

    All tools share the sw_ prefix and use a consistent snake_case verb_noun pattern (list_*, get_*, create_*, update_*, delete_*, undelete_*, add_*, remove_*). The only minor deviation is sw_healthcheck, which still reads as a clear command.

    Tool Count2/5

    At 27 tools, the surface exceeds the 25+ threshold for too many, making it heavy for an agent to scan. While the Splitwise domain is broad, the set could benefit from consolidation or splitting into more focused servers.

    Completeness4/5

    Core lifecycle coverage is strong: groups, friends, expenses (including undelete, receipts, and comments), and user profile all have meaningful operations. Minor gaps include no group update and no explicit settle-up/payment operation.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources