Splitwise FAQs

Question 1

Does the server improve performance for Splitwise API calls?

Accepted Answer

Yes, it includes in-memory TTL (Time-To-Live) caching for improved performance. This means frequently requested data can be served faster without always hitting the Splitwise API, and it also features fuzzy name-to-ID resolution for convenience.

Question 2

What types of Splitwise actions can I perform?

Accepted Answer

The server exposes 35 tools across categories like Users, Expenses (CRUD), Groups (CRUD, user management), Friends (CRUD), Comments, Notifications, Resolution (for fuzzy matching names to IDs), Utilities, and even basic Arithmetic for calculations within prompts.

Question 3

How do I authenticate the Splitwise MCP Server?

Accepted Answer

You can authenticate using either a Splitwise personal API key or an OAuth 2.0 access token. These credentials can be provided via environment variables in your client's configuration (e.g., in `.mcp.json` for Claude Code/Cursor).

Question 4

What is the Splitwise MCP Server?

Accepted Answer

The Splitwise MCP Server is a Ruby-based server that exposes 35 Splitwise API tools via the Model Context Protocol (MCP). It allows AI-powered clients to directly interact with Splitwise for managing expenses, groups, and more.

Question 5

Which AI clients are compatible with this server?

Accepted Answer

This server is compatible with major MCP clients, including Claude Code, Claude Desktop, and Cursor. It's designed to work with any client that supports the Model Context Protocol.

Splitwise

Splitwise

Key Features

Use Cases

Key Features

Use Cases