Splitwise MCP Server

If you already use Splitwise MCP, the splitwise mcp mcp server is the piece that lets your assistant work with it directly. I was about to head on a trip with friends and already dreading the expense tracking.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• get_current_user — Your Splitwise profile
• list_currencies — All currencies Splitwise supports
• list_groups — All your groups with member IDs
• get_group — Group details — members, balances, debts
• list_expenses — Recent expenses in a group
• get_expense — Full details of one expense
• create_expense — Add expense (equal, exact, or percentage split)
• update_expense — Edit description, cost, currency, or date
• delete_expense — Remove an expense
• create_payment — Record a settlement between two people

Credentials and setup notes

Configuration is passed through the environment: SPLITWISE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Splitwise MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Splitwise MCP's toolset — get_current_user, list_currencies, list_groups and 7 more — is a fair guide to whether it matches your workflow. It is maintained by bhvkmuni; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.