Build solutions, not workarounds.
What do you want Splitwise and SMS.to to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Splitwise can start in SMS.to
When New Expense in Splitwise
then List messages in SMS.to
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Splitwise and SMS.to
Triggers and actions 1 trigger · 2 actions
Trigger
New ExpenseTriggers when a new expense is created. Optionally, filter for a specific group.
Action
Create ExpenseCreates a new expense, optionally in a group or with a specific set of friends.
Action
List messagesLists messages sent from the SMS.to account, newest first, optionally filtered by status, recipient or creation date range (at most 31 days of data).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Splitwise
Splitwise to StripeStripe is a payment processing platform for online businesses.
Splitwise to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Splitwise to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Splitwise to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Splitwise to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
Splitwise to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
More into SMS.to
HubSpot to SMS.toHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SMS.toSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SMS.toSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SMS.toGoogle Sheets
Gmail to SMS.toGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SMS.toGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Splitwise and SMS.to, answered
What can start an automation from Splitwise?
Any of Splitwise's 1 trigger in the catalog, including New Expense. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SMS.to when something happens in Splitwise?
Any of SMS.to's 1 action, including List messages. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SMS.to to Splitwise?
SMS.to has no triggers in the catalog today, so automations start in Splitwise. If you need the other direction, ask: your agent reads SMS.to's API documentation and adds it.
Do I have to build a connector for Splitwise or SMS.to?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.