splitwise-mcp

Purpose: Connecting AI assistants to Splitwise expense-management data and actions.

Inferred · not functionally tested

Audience: developers building AI assistants and MCP integrations

Inferred · not functionally tested

Functions: Unknown

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: API, WEB · deployment: browser, self_hosted, cli, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

In the Frameworks & SDKs space, splitwise-mcp takes a focused approach. Inferred · not functionally tested: It focuses on connecting AI assistants to Splitwise expense-management data and actions. Inferred · not functionally tested: It is built as an open-source project for developers building AI assistants and MCP integrations. Basis unknown · not verified: splitwise-mcp is open source under the Open Source license. Basis unknown · not verified: It runs on the web, the command line, and API, and it can be self-hosted.

It is developed by Chris Chall. Inferred · not functionally tested: Among its 4 catalogued features are MCP server, splitwise integration, and expense access. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.