Skip to main content
Glama
AzeemWaqarRao

Splitwise MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SPLITWISE_API_KEYYesYour Splitwise API key from dev.splitwise.com
SPLITWISE_GROUP_IDNoOptional default group ID (from URL when opening a group on splitwise.com)

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_expensesA

List expenses, most recent first.

When group_id is omitted, the SPLITWISE_GROUP_ID default is used. Pass group_id=0 to list expenses across all groups and non-group expenses. Date filters (dated_after/before, updated_after/before) accept ISO 8601 strings, e.g. "2026-01-31T00:00:00Z".

get_expenseA

Get the full details of a single expense by its id.

create_expenseA

Create a new expense.

cost is a decimal string, e.g. "25.00". description is required.

Splitting:

  • Equal split (default): leave users empty; the cost is split evenly among everyone in the resolved group (group_id or SPLITWISE_GROUP_ID).

  • Custom split: pass users, a list of dicts each like {"user_id": 123, "paid_share": "25.00", "owed_share": "12.50"}. Identify a user by user_id, or by email/first_name/last_name. The paid_share values must sum to cost, and so must the owed_share values.

date accepts ISO 8601 (e.g. "2026-06-15T00:00:00Z"). currency_code is a 3-letter code (e.g. "USD"). category_id and details are optional.

update_expenseA

Update an existing expense. Only provided fields are changed.

Note: if you pass users (custom shares), it overwrites ALL existing shares on the expense — include every participant. See create_expense for the users format and split rules.

delete_expenseA

Delete an expense by id. Returns {"success": true} on success.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: create, delete, get, list, update. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., create_expense, list_expenses), making them predictable.

Tool Count5/5

5 tools is appropriate for the domain of expense management, covering core CRUD operations without unnecessary bloat.

Completeness5/5

The toolset covers all basic expense lifecycle operations (create, read, update, delete, list) with detailed split support, leaving no obvious gaps.

Maintenance

ActivitySlowing
ResponsivenessNo issues