Splitwise MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for WebSocket mode (default 4001) | 4001 |
| SPLITWISE_ACCESS_TOKEN | Yes | Access token for Splitwise API |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| splitwise_get_groupsA | List all groups for the current user. Groups represent collections of users who share expenses together (e.g., household, trip, etc.). |
| splitwise_get_groupA | Get detailed information about a specific group, including members, balances, and settings. |
| splitwise_get_expensesC | List expenses with optional filters. Can filter by group, friend, date range, or update time. |
| splitwise_get_expenseA | Get detailed information about a specific expense, including all users involved and their shares. |
| splitwise_create_expenseA | Create a new expense. Can split equally among group members or specify custom shares for each user. For custom shares, provide users array with paid_share and owed_share for each user. |
| splitwise_update_expenseA | Update an existing expense. Only include fields that are changing. If users array is provided, all shares will be overwritten. |
| splitwise_delete_expenseB | Delete an expense permanently. |
| splitwise_restore_expenseB | Restore a deleted expense. |
| splitwise_get_categoriesA | Get a list of all expense categories supported by Splitwise. Use subcategory IDs when creating expenses. |
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 9 tools
Each tool targets a distinct resource and action: groups vs expenses vs categories, and within expenses, the CRUD operations are clearly separated. There is no ambiguity between tools.
All tools follow a consistent 'splitwise_verb_noun' pattern using snake_case, with verbs like get, create, update, delete, restore, and nouns like groups, group, expenses, expense, categories. No mixing of conventions.
9 tools is well-scoped for an expense sharing server. It covers group retrieval, expense management (CRUD + restore), and categories without being too sparse or overwhelming.
The tool set provides robust expense management (create, read, update, delete, restore) and group info retrieval. However, missing group CRUD (create/update/delete) and friend management, which are minor gaps for the core expense tracking domain.