split-bill-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | debug | info | warn | error | info |
| SPLITBILL_EMAIL | Yes | Service-user email | |
| SPLITBILL_BASE_URL | Yes | SplitBill origin, e.g. http://localhost:3000 | |
| SPLITBILL_PASSWORD | Yes | Service-user password | |
| SPLITBILL_TIMEOUT_MS | No | HTTP timeout per request (ms) | 15000 |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_billA | Create a SplitBill bill. mode=ready_split takes pre-split participants with totals; mode=raw_receipt takes receipt positions with consumers and splits them. |
| list_billsA | List my SplitBill bills with filters by payment status, my role, title search, date range, and pagination. |
| get_billA | Get one SplitBill bill by ID with participants and payment statuses. |
| update_paymentC | Update a participant payment status (paid, unpaid, pending_confirmation) on a bill. |
| search_usersB | Search SplitBill users by name or email (to resolve participant IDs). |
| list_friendsB | List my SplitBill friends (for picking bill participants). |
| get_dashboard_statsB | Get SplitBill dashboard totals: bill count, amounts owed and owing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools target distinct resources: bills, payments, users, friends, and stats. The only slight overlap is search_users versus list_friends, but their descriptions clarify that one resolves arbitrary users while the other picks from existing friends.
All tool names follow a consistent verb_noun pattern in snake_case: create_bill, list_bills, get_bill, update_payment, search_users, list_friends, get_dashboard_stats. Pluralization is handled idiomatically per resource without mixing conventions.
Seven tools is well-scoped for a split-bill domain. Each tool covers a distinct, necessary operation without redundancy or bloat.
The core bill workflow is covered: create, list, get, and update payment status. However, there is no update_bill or delete_bill operation, so editing or canceling a bill would be impossible through this server.