Skip to content
Splitwise logo

Splitwise MCP server

Splitwise is a expense splitting app that helps you track and settle bills with friends, family, and roommates.

Splitwise is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
1
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
August 2026

About the Splitwise MCP server

Connect Splitwise once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Splitwise and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Splitwise tools your AI can run

Once connected, your assistant can call any of these Splitwise actions by asking in plain language.

  • Create Expense

    Creates a new expense, optionally in a group or with specific friends

    10 fields

Triggers

Splitwise events your agent can watch

These start a run the moment something happens in Splitwise, so work gets picked up on its own.

  • New Expense

    Triggers when a new expense is created. Optionally, filter for a specific group.

    1 field

Give your assistant Splitwise

Connect Splitwise once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Splitwise MCP, answered.

No. That is the point of it. One Activepieces server exposes Splitwise alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Splitwise in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 1 tool, including Create Expense, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.