Splitwise Mcp

Returns information about the authenticated user: id, name, email, default currency, locale, registration status.

No parameter schema in public metadata yet.

Returns public information about another Splitwise user by id.

Update the authenticated user's profile (first_name, last_name, email, password, default_currency, locale, etc.).

**Note**: Expenses that are not associated with a group are listed in a group with ID 0.

No parameter schema in public metadata yet.

Returns full details for a group: members, balances, simplified-debts setting, group type, avatar.

Creates a new group. Adds the current user to the group by default. **Note**: group user parameters must be flattened into the format `users__{index}__{property}`, where `property` is `user_id`, `first_name`, `last_name`, or `email`. The user's email or ID must be provided.

Delete an existing group. Destroys all associated records (expenses, etc.)

Restores a deleted group. **Note**: 200 OK does not indicate a successful response. You must check the `success` value of the response.

**Note**: 200 OK does not indicate a successful response. You must check the `success` value of the response.

Remove a user from a group. Does not succeed if the user has a non-zero balance. **Note:** 200 OK does not indicate a successful response. You must check the success value of the response.

**Note**: `group` objects only include group balances with that friend.

No parameter schema in public metadata yet.

Returns details about a single friendship including balances by currency and any pending expenses with that friend.

Adds a friend. If the other user does not exist, you must supply `user_first_name`. If the other user exists, `user_first_name` and `user_last_name` will be ignored.

Add multiple friends at once. For each user, if the other user does not exist, you must supply `users__{index}__first_name`. **Note**: user parameters must be flattened into the format `users__{index}__{property}`, where `property` is `first_name`, `last_name`, or `email`.

Given a friend ID, break off the friendship between the current user and the specified user. **Note**: 200 OK does not indicate a successful response. You must check the `success` value of the response.

Returns a list of all currencies allowed by the system. These are mostly ISO 4217 codes, but we do sometimes use pending codes or unofficial, colloquial codes (like BTC instead of XBT for Bitcoin).

No parameter schema in public metadata yet.

Returns full details for a single expense by id: payers, splits, shares, comments count, group, and audit metadata.

List expenses visible to the authenticated user. Supports filters: group_id, friend_id, dated_after, dated_before, updated_after, updated_before, limit, offset.

Creates an expense. You may either split an expense equally (only with `group_id` provided), or supply a list of shares. When splitting equally, the authenticated user is assumed to be the payer. When providing a list of shares, each share must include `paid_share` and `owed_s...

Updates an expense. Parameters are the same as in `create_expense`, but you only need to include parameters that are changing from the previous values. If any values is supplied for `users__{index}__{property}`, _all_ shares for the expense will be overwritten with the provide...

**Note**: 200 OK does not indicate a successful response. The operation was successful only if `success` is true.

**Note**: 200 OK does not indicate a successful response. The operation was successful only if `success` is true.

Returns the comments on a given expense. `expense_id` is required.

Add a comment to an existing expense by expense_id.

Deletes a comment. Returns the deleted comment.

Return a list of recent activity on the users account with the most recent items first. `content` will be suitable for display in HTML and uses only the `<strong>`, `<strike>`, `<small>`, `<br>` and `<font color="#FFEE44">` tags. The `type` value indicates what the notificatio...

Returns a list of all categories Splitwise allows for expenses. There are parent categories that represent groups of categories with subcategories for more specific categorization. When creating expenses, you must use a subcategory, not a parent category. If you intend for an...

No parameter schema in public metadata yet.