splitwise-mcp-server
Provides a Rust-based MCP (Model Context Protocol) server and an optional HTTP JSON-RPC endpoint that exposes Splitwise account functionality (users, groups, expenses, friends, and utilities like currencies/categories) to AI agents. Supports local stdio MCP usage and a remote HTTP deployment protected by a bearer token.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README recommends using environment variables, claims the server stores API keys in memory during runtime, and advises strong tokens and HTTPS for production. Scope granularity is not described (likely coarse bearer token for all operations). No details are provided about logging redaction, secure defaults for remote transport, or input validation.
⚡ Reliability
Best When
You want an agent to manage Splitwise data through structured tool calls (MCP stdio or remote HTTP) and you can securely host the service with appropriate tokens.
Avoid When
You need fine-grained authorization per operation/user, or you cannot enforce HTTPS and token hygiene for remote access.
Use Cases
- • AI-assisted expense tracking and reporting from Splitwise
- • Creating/updating/deleting Splitwise expenses and groups via agent tool calls
- • Checking friend balances and generating summaries for a time period
- • Automating personal finance workflows through MCP-compatible clients
Not For
- • Production use without reviewing security posture and Splitwise API terms/permissions
- • Use cases requiring real-time guarantees or strict idempotency semantics
- • Environments where outbound HTTPS to Splitwise and maintaining API keys are not allowed
Interface
Authentication
HTTP endpoint uses Authorization: Bearer <token> per README examples. The README does not describe fine-grained scopes; auth appears coarse at the server level.
Pricing
Self-hosted open-source project; costs are infrastructure plus Splitwise API usage (Splitwise terms not provided here).
Agent Metadata
Known Gotchas
- ⚠ Remote HTTP endpoint requires Authorization bearer token; agents may omit headers unless configured.
- ⚠ Create/update/delete operations may not be idempotent; repeated calls on retries could create duplicate expenses unless the implementation includes safeguards (not documented).
- ⚠ Rate limiting is mentioned only at a high level; agents may need guidance to throttle or cache.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for splitwise-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.