healthLABSCO SUMMARY
Settling up without opening the app.
The awkward part of a shared trip — entering who paid and how it splits — becomes a sentence, and the balance comes back computed rather than argued over.
What it is
A bridge to Splid, the shared-expenses app, built on the reverse-engineered splid-js client. It works against one group by default, and takes member names rather than IDs, resolving them case-insensitively.
What you get
- An expense created with its payers and its shares, written in the names people go by in the group
- Recent entries in a group listed, up to a hundred at a time
- The group's balances and summary, computed by Splid itself
Requirements
Node.js and a Splid invite code, set as CODE in a .env file; any call can override the group with a different code or ID. It serves Streamable HTTP on the port you set, and it reaches Splid through a reverse-engineered client rather than an official API.
Setup effort
Build from source
USE CASES
01
Logging a dinner someone just paid for
Say who paid and how it splits, in names. Shares have to add up to one, so a bad split is refused rather than silently recorded.
02
Checking who owes whom before a trip ends
The summary comes back as balances, with the recent entries beside it if someone disputes a number.
03
Catching an expense that was missed or entered twice
List what is in the group, spot the gap or the duplicate, and put the correcting entry in from the same place.
5 tools
Listed in project docs. Your client may show a different list.
whoamicreateExpenselistEntriesgetGroupSummaryBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
CODE in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/mxxfun/splid_mcp
cd splid_mcp
npm installCreate a .env file in the project root containing CODE=<YOUR_CODE> (your Splid group's invite code) and PORT=8000.
TERMINAL
npm run build
npm run devConnect your MCP client to http://localhost:8000/mcp over Streamable HTTP — no auth headers are needed.
