Bring Expense Tracking
to Pydantic AI
Learn how to connect Splitwise to Pydantic AI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Splitwise MCP Server?
What you can do
- Track Expenses: Give your AI agent the ability to check who owes who across your distinct groups.
- Log Bills: Ask your AI to calculate receipts and accurately add the expense directly into Splitwise with automatic percentage or custom splits.
- Manage Friends & Groups: Easily pull details of group members.
How it works
1. Log into your Splitwise account. 2. Navigate to your Developer Applications settings to generate a personal API token. 3. Insert your Splitwise API Key directly into Vinkius vault.Who is this for?
Perfect for roommates, travel groups, and everyday individuals using AI tools like Claude/Cursor to parse complex grocery or travel receipts and directly sync them to Splitwise.Built-in capabilities (10)
Expects a stringified JSON object containing details like cost, description, format details (e.g. users__0__user_id=123, users__0__paid_share=5.00, etc. or JSON). Create an expense
Delete an expense
Get current user details
Get a specific expense
List expenses
Get friend details
List all friends
Get group details
List all groups
Get user details by ID
Why Pydantic AI?
Pydantic AI validates every Splitwise tool response against typed schemas, catching data inconsistencies at build time. Connect 10 tools through Vinkius and switch between OpenAI, Anthropic, or Gemini without changing your integration code. full type safety, structured output guarantees, and dependency injection for testable agents.
- —
Full type safety: every MCP tool response is validated against Pydantic models, catching data inconsistencies before they reach your application
- —
Model-agnostic architecture. switch between OpenAI, Anthropic, or Gemini without changing your Splitwise integration code
- —
Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors
- —
Dependency injection system cleanly separates your Splitwise connection logic from agent behavior for testable, maintainable code
Splitwise in Pydantic AI
Splitwise and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Splitwise to Pydantic AI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Splitwise in Pydantic AI
The Splitwise MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Pydantic AI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Splitwise for Pydantic AI
Every tool call from Pydantic AI to the Splitwise MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can the agent distribute the bill unequally?
Yes! When creating an expense, the AI agent can pass detailed users configuration in JSON to specify exact dollar amounts for each involved party.
How far back does the expense log go?
The agent typically limits the reading to the 20 most recent expenses to keep memory manageable, but can be instructed to pull earlier ones.
Can the bot settle debts?
Currently, the agent interacts with expenses. To log a debt settlement, the agent submits a specific 'payment = true' expense wrapper via the splitwise schema.
How does Pydantic AI discover MCP tools?
Create an MCPServerHTTP instance with the server URL. Pydantic AI connects, discovers all tools, and generates typed Python interfaces automatically.
Does Pydantic AI validate MCP tool responses?
Yes. When you define result types as Pydantic models, every tool response is validated against the schema. Invalid data raises a clear error instead of silently corrupting your pipeline.
Can I switch LLM providers without changing MCP code?
Absolutely. Pydantic AI abstracts the model layer. your Splitwise MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.
MCPServerHTTP not found
Update: pip install --upgrade pydantic-ai