splitwise-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPLITWISE_API_KEY | No | Your Splitwise API Key (simplest setup option) | |
| SPLITWISE_ACCESS_TOKEN | No | Your Splitwise Access Token for OAuth 1.0 | |
| SPLITWISE_CONSUMER_KEY | No | Your Splitwise Consumer Key for OAuth 1.0 | |
| SPLITWISE_CONSUMER_SECRET | No | Your Splitwise Consumer Secret for OAuth 1.0 | |
| SPLITWISE_ACCESS_TOKEN_SECRET | No | Your Splitwise Access Token Secret for OAuth 1.0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_expensesA | List Splitwise expenses. Filter by group, friend, date range, or limit. Returns cost, description, date, who paid, and splits. |
| get_expenseA | Get a single Splitwise expense by ID with full split details. |
| create_expenseA | Create a new Splitwise expense with explicit per-user splits. Always confirm split details with the user before calling. |
| delete_expenseC | Delete a Splitwise expense by ID. |
| get_friendsA | List all Splitwise friends with their IDs, names, emails, and current balances. Use this to look up user IDs before creating expenses. |
| get_groupsA | List all Splitwise groups with member details, group IDs, and current debts within each group. |
| get_friend_balancesA | Get a pre-computed net balance summary — who owes you, who you owe, and your overall net position across all friends. Much faster than manually summing raw balances. |
| get_current_userA | Get the currently authenticated Splitwise user — useful to find your own user ID when creating expense splits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Every tool has a distinct purpose with clear boundaries: create/delete/get expense operations, user/friend/group retrieval, and balance summaries. No overlap exists between tools like get_expenses (list) and get_expense (single), or between get_friend_balances (summary) and get_friends (detailed list).
All tools follow a consistent verb_noun pattern (e.g., create_expense, get_expenses, get_friend_balances) with no deviations in style. The naming is predictable and readable throughout the set.
With 8 tools, the count is well-scoped for managing Splitwise expenses, users, friends, groups, and balances. Each tool serves a clear and necessary function without redundancy, fitting a typical utility server range.
The toolset covers core Splitwise operations: CRUD for expenses, retrieval of user/friend/group data, and balance summaries. A minor gap exists in updating expenses (e.g., update_expense), but agents can work around this by deleting and recreating, and other workflows are well-supported.