How to connect Splitwise to OpenClaw
Connect Splitwise to OpenClaw with ClawLink in one click — 27 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
SplitwiseOAUTH2MCPTrack and settle shared expenses and group bills. Once connected, OpenClaw can read and act on Splitwise from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Splitwise access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Splitwise setup: install one ClawHub skill, connect Splitwise in the browser, and OpenClaw can call real Splitwise actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Splitwise skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Splitwise" (hith3sh/splitwise) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/splitwise
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Splitwise.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Splitwise
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Splitwise?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Splitwise in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Pull the relevant data from Splitwise, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Splitwise is connected in the dashboard, that agent calls the same 27 Splitwise tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Splitwise MCP for OpenClaw
Looking for a Splitwise MCP server for OpenClaw? ClawLink connects Splitwise to OpenClaw and exposes 27 Splitwise tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Splitwise integration works the same way.
What the OpenClaw Splitwise integration can do
27 Splitwise tools are ready for OpenClaw once the account is connected. The 22 below are the ones people reach for most; your agent can call all 27.
22 of 27 Splitwise tools for OpenClaw
| Tool | What it does |
|---|---|
Get categories splitwise_get_categories | Retrieve expense categories |
Get comments splitwise_get_comments | Retrieve all comments associated with a specific expense |
Get currencies splitwise_get_currencies | Retrieve a list of supported currencies |
Get current user splitwise_get_current_user | Retrieve information about the current authenticated user |
Get expense splitwise_get_expense | Retrieve detailed information about a specific expense by ID |
Get expenses splitwise_get_expenses | List the current user's expenses from Splitwise account |
Get friend splitwise_get_friend | Retrieve detailed information about a specific friend |
Get friends splitwise_get_friends | List current user's friends on Splitwise |
Get group splitwise_get_group | Retrieve detailed information about a specific group |
Get groups splitwise_get_groups | Retrieves all groups the authenticated user belongs to, including group details, members |
Get notifications splitwise_get_notifications | Retrieve recent activity notifications from the user's Splitwise account |
Get user splitwise_get_user | Retrieves basic profile information about any Splitwise user by their ID |
Add friend splitwise_add_friend | Add a new friend to Splitwise |
Add user to group splitwise_add_user_to_group | Add a user to a group |
Create comment splitwise_create_comment | Create a comment on a specific expense |
Create expense splitwise_create_expense | Create a new Splitwise expense |
Create friends splitwise_create_friends | Add multiple friends at once to Splitwise |
Create group splitwise_create_group | Create a new group in Splitwise |
Undelete expense splitwise_undelete_expense | Restore a previously deleted expense and its associated records |
Undelete group splitwise_undelete_group | Restore a previously deleted group and all its associated records |
Update expense splitwise_update_expense | Update an existing Splitwise expense |
Update user splitwise_update_user | Update user account details including name, email, password, and preferences |
Try it: find the Splitwise tool you need
Browse the 22 Splitwise tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Splitwise, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Splitwise, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Splitwise, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Splitwise, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Splitwise working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Splitwise app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Splitwise through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Splitwise. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Splitwise actions to the runtime in a format your agent can reliably use. | 27 tools for Splitwise are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Splitwise to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Splitwise in the browser, and the 27 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Splitwise skill but can't call the tools
The ClawHub skill teaches OpenClaw about Splitwise, but the calls run through the ClawLink plugin and your connected account. Make sure Splitwise is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Splitwise from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Splitwise tools
Splitwise tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Splitwise call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Splitwise returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting Splitwise and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Splitwise integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Splitwise: link your Splitwise account once in the browser and OpenClaw can call the Splitwise API through 27 ready-made tools — no custom code or token handling.
How do I add Splitwise to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Splitwise skill from ClawHub, then you click Connect in the dashboard to authorize Splitwise. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Splitwise to OpenClaw?
About two minutes. Sign in, click Connect next to Splitwise in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Splitwise up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Splitwise working from chat.
OpenClaw installed the Splitwise skill but can't call the tools
The ClawHub skill teaches OpenClaw about Splitwise, but the calls run through the ClawLink plugin and your connected account. Make sure Splitwise is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
