Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@splitwise-mcp Add a $45 dinner split equally with Sarah"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server for Splitwise — manage shared expenses directly from Claude, Cursor, or any MCP-compatible AI assistant.
No well-maintained Splitwise MCP existed. This one does.
Tool | Description |
| List expenses — filter by group, friend, date range |
| Get a single expense by ID |
| Create a new expense with per-user splits |
| Delete an expense by ID |
| List all friends with IDs and balances |
| List all groups with members and debts |
| Pre-computed net balance summary (who owes you, who you owe) |
| Get your Splitwise user ID |
Related MCP server: Splitwise MCP Server
Go to splitwise.com/apps
Register an app (or use existing) → copy the API Key
Set env var: SPLITWISE_API_KEY=your_api_key
Go to splitwise.com/apps → register an app
Copy Consumer Key and Consumer Secret
Complete the OAuth 1.0 flow to get an access token and secret
Set env vars:
SPLITWISE_CONSUMER_KEY=your_consumer_key
SPLITWISE_CONSUMER_SECRET=your_consumer_secret
SPLITWISE_ACCESS_TOKEN=your_access_token
SPLITWISE_ACCESS_TOKEN_SECRET=your_access_token_secretAdd to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
{
"mcpServers": {
"splitwise": {
"command": "npx",
"args": ["splitwise-mcp"],
"env": {
"SPLITWISE_API_KEY": "your-api-key-here"
}
}
}
}Restart Claude Desktop — you'll see the Splitwise tools available.
"What do I owe on Splitwise?"
"Show me all expenses from last month"
"Add a $60 dinner split equally between me and Alice"
"Which of my friends owes me the most?"
"Show me all expenses in my Roommates group"
git clone https://github.com/SaharshPatel24/splitwise-mcp
cd splitwise-mcp
npm install
npm run build
# Run with your API key
SPLITWISE_API_KEY=your_key node dist/index.jsMIT
Create a new Splitwise expense with explicit per-user splits. Always confirm split details with the user before calling.
Inputs: description (required), cost (required), date (required), users (required), +2 more.
Delete a Splitwise expense by ID.
Inputs: id (required).
Get the currently authenticated Splitwise user — useful to find your own user ID when creating expense splits.
Inputs: no named parameters.
Get a single Splitwise expense by ID with full split details.
Inputs: id (required).
List Splitwise expenses. Filter by group, friend, date range, or limit. Returns cost, description, date, who paid, and splits.
Inputs: group_id, friend_id, dated_after, dated_before, +2 more.
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.
Inputs: no named parameters.
List all Splitwise friends with their IDs, names, emails, and current balances. Use this to look up user IDs before creating expenses.
Inputs: no named parameters.
List all Splitwise groups with member details, group IDs, and current debts within each group.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Split bills and collect payments through PayNow (Singapore) from your AI. MCP server for SplitBill.
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
MCP server for Gainium — manage trading bots, deals, and balances via AI assistants
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
