# How to integrate Splitwise MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Splitwise MCP with Vercel AI SDK v6", "toolkit": "Splitwise", "toolkit_slug": "splitwise", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/splitwise/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/splitwise/framework/ai-sdk.md", "updated_at": "2026-05-12T10:26:49.209Z" } ``` ## Introduction This guide walks you through connecting Splitwise to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Splitwise agent that can add a new friend using their email, create a dinner expense split equally, list all groups i'm part of through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Splitwise account through Composio's Splitwise MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Splitwise with - [OpenAI Agents SDK](https://composio.dev/toolkits/splitwise/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/splitwise/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/splitwise/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/splitwise/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/splitwise/framework/codex) - [OpenClaw](https://composio.dev/toolkits/splitwise/framework/openclaw) - [Hermes](https://composio.dev/toolkits/splitwise/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/splitwise/framework/cli) - [Google ADK](https://composio.dev/toolkits/splitwise/framework/google-adk) - [LangChain](https://composio.dev/toolkits/splitwise/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/splitwise/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/splitwise/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/splitwise/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Splitwise integration - Using Composio's Tool Router to dynamically load and access Splitwise tools - Creating an MCP client connection using HTTP transport - Building an interactive CLI chat interface with conversation history management - Handling tool calls and results within the Vercel AI SDK framework ## What is Vercel AI SDK? The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state. Key features include: - streamText: Core function for streaming responses with real-time tool support - MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp - Step Counting: Control multi-step tool execution with stopWhen: stepCountIs() - OpenAI Provider: Native integration with OpenAI models ## What is the Splitwise MCP server, and what's possible with it? The Splitwise MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Splitwise account. It provides structured and secure access to your expenses and group data, so your agent can perform actions like creating expenses, adding friends, retrieving categories, and managing your account on your behalf. - Expense tracking and creation: Quickly have your agent record new expenses, split bills, or log payments—either between you and friends or within groups. - Friend and contact management: Easily add new friends with their email and name, or remove existing friends to keep your network current. - Group info and collaboration: Retrieve details about any group you belong to, making it simple to manage shared costs and stay organized with your housemates, travel buddies, or teams. - Expense category and currency lookup: Ask the agent to fetch available expense categories or supported currencies, helping you record transactions accurately and consistently. - Account and profile insights: Let your agent pull your current user details so you can quickly review account information or verify profile data as needed. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `SPLITWISE_ADD_FRIEND` | Add Friend | Tool to add a new friend to Splitwise. Use when you have the friend's email and name details ready. | | `SPLITWISE_ADD_USER_TO_GROUP` | Add User to Group | Tool to add a user to a group. Use when you need to add an existing Splitwise user to a specific group. Note: 200 OK does not indicate success; always check the response 'success' field. | | `SPLITWISE_CREATE_COMMENT` | Create Comment | Tool to create a comment on a specific expense. Use when you need to add a comment or note to an existing expense. | | `SPLITWISE_CREATE_EXPENSE` | Create Expense | Tool to create a new Splitwise expense. Use when you need to record a payment or bill in a group or between users. Provide exactly one of split_equally or users for shares — supplying both or neither causes a validation error and no expense is created. | | `SPLITWISE_CREATE_FRIENDS` | Create Friends | Tool to add multiple friends at once to Splitwise. Use when you need to add several friends in a single operation. | | `SPLITWISE_CREATE_GROUP` | Create Group | Tool to create a new group in Splitwise. Use when you need to create a group for tracking shared expenses. The current user is automatically added to the group. You can optionally add other members during creation. | | `SPLITWISE_DELETE_COMMENT` | Delete Comment | Tool to delete a comment by its ID. Use after confirming you have a valid comment ID. | | `SPLITWISE_DELETE_EXPENSE` | Delete Expense | Tool to delete an existing expense by its ID. Deletion is irreversible — no undelete capability exists. Use after confirming you have the correct expense ID. Inspect the response's `success` and `error` fields to verify deletion succeeded; failures (e.g., user lacks owner/participant permissions) are surfaced there. | | `SPLITWISE_DELETE_FRIEND` | Delete Friend | Tool to delete an existing friend by ID. Use when you need to remove a friend relationship by its user ID. Call after confirming the correct friend ID. | | `SPLITWISE_DELETE_GROUP` | Delete Group | Tool to delete a group and all associated records by its ID. Use when you need to permanently remove a group and its expenses. Call after confirming the correct group ID. | | `SPLITWISE_GET_CATEGORIES` | Get Categories | Tool to retrieve expense categories. Use when you need to list available categories before creating an expense. | | `SPLITWISE_GET_COMMENTS` | Get Comments | Tool to retrieve all comments associated with a specific expense. Use when you need to view comments on an expense, including both system-generated updates and user-authored messages. | | `SPLITWISE_GET_CURRENCIES` | Get Currencies | Tool to retrieve a list of supported currencies. Use when you need to display or validate currency options. | | `SPLITWISE_GET_CURRENT_USER` | Get Current User | Tool to retrieve information about the current authenticated user. Use when you need profile details of the logged-in user. | | `SPLITWISE_GET_EXPENSE` | Get Expense | Tool to retrieve detailed information about a specific expense by ID. Use when you need to view expense details including participants, shares, and repayments. | | `SPLITWISE_GET_EXPENSES` | Get Expenses | Tool to list the current user's expenses from Splitwise account. Use when you need to view expenses with optional filters like date ranges, groups, or friends. | | `SPLITWISE_GET_FRIEND` | Get Friend Details | Tool to retrieve detailed information about a specific friend. Use when you need to get profile details and balance information for a friend by their user ID. | | `SPLITWISE_GET_FRIENDS` | Get Friends | Tool to list current user's friends on Splitwise. Use when you need to view all friends, their balances, and shared groups. | | `SPLITWISE_GET_GROUP` | Get Group Details | Tool to retrieve detailed information about a specific group. Returns full group details including members, balances, debts (both original and simplified), avatar URLs, and group settings. Use this when you need comprehensive information about a particular group, such as viewing who owes what to whom. Use group ID of 0 to get non-group expenses. | | `SPLITWISE_GET_GROUPS` | Get Groups | Retrieves all groups the authenticated user belongs to, including group details, members, balances, and debt information. Returns a 'groups' array with no server-side filtering; all name- or ID-based filtering must be done client-side on the full response. Group names may share similar strings or differ in case/whitespace — normalize when matching and prefer group_id once identified. The groups array may be empty if the user belongs to no groups. | | `SPLITWISE_GET_NOTIFICATIONS` | Get Notifications | Tool to retrieve recent activity notifications from the user's Splitwise account. Returns notifications with HTML content suitable for display, with the most recent items first. Use when you need to view recent account activity or updates. | | `SPLITWISE_GET_USER` | Get User Information | Retrieves basic profile information about any Splitwise user by their ID. Returns the user's name, email, registration status, and profile picture. This endpoint only returns public user information. For the authenticated user's full profile (including notifications, currency preferences, and locale settings), use get_current_user instead. | | `SPLITWISE_REMOVE_USER_FROM_GROUP` | Remove User from Group | Tool to remove a user from a group. Use when you need to remove a user from a specific group. Note: User must have a zero balance in the group for removal to succeed. 200 OK does not indicate success; always check the response 'success' field. | | `SPLITWISE_UNDELETE_EXPENSE` | Restore Deleted Expense | Tool to restore a previously deleted expense and its associated records. Use when you need to recover an expense that was deleted. Call after confirming the correct expense ID. Not a guaranteed undo mechanism — treat deletion as high-impact and verify restoration completeness afterward. | | `SPLITWISE_UNDELETE_GROUP` | Restore Deleted Group | Tool to restore a previously deleted group and all its associated records. Use when you need to recover a group that was deleted. Call after confirming the correct group ID. | | `SPLITWISE_UPDATE_EXPENSE` | Update Expense | Tool to update an existing Splitwise expense. Use when you need to modify expense details such as cost, description, or participant shares. Only include fields you want to change. Note that a 200 OK response does not guarantee success - check that the errors object is empty. | | `SPLITWISE_UPDATE_USER` | Update User | Tool to update user account details including name, email, password, and preferences. Use when you need to modify the current user's profile information. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Splitwise MCP server is an implementation of the Model Context Protocol that connects your AI agent to Splitwise. It provides structured and secure access so your agent can perform Splitwise operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before you begin, make sure you have: - Node.js and npm installed - A Composio account with API key - An OpenAI API key ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install required dependencies First, install the necessary packages for your project. What you're installing: - @ai-sdk/openai: Vercel AI SDK's OpenAI provider - @ai-sdk/mcp: MCP client for Vercel AI SDK - @composio/core: Composio SDK for tool integration - ai: Core Vercel AI SDK - dotenv: Environment variable management ```bash npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's needed: - OPENAI_API_KEY: Your OpenAI API key for GPT model access - COMPOSIO_API_KEY: Your Composio API key for tool access - COMPOSIO_USER_ID: A unique identifier for the user session ```bash OPENAI_API_KEY=your_openai_api_key_here COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here ``` ### 4. Import required modules and validate environment What's happening: - We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio - The dotenv/config import automatically loads environment variables - The MCP client import enables connection to Composio's tool server ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); ``` ### 5. Create Tool Router session and initialize MCP client What's happening: - We're creating a Tool Router session that gives your agent access to Splitwise tools - The create method takes the user ID and specifies which toolkits should be available - The returned mcp object contains the URL and authentication headers needed to connect to the MCP server - This session provides access to all Splitwise-related tools through the MCP protocol ```typescript async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["splitwise"], }); const mcpUrl = session.mcp.url; ``` ### 6. Connect to MCP server and retrieve tools What's happening: - We're creating an MCP client that connects to our Composio Tool Router session via HTTP - The mcp.url provides the endpoint, and mcp.headers contains authentication credentials - The type: "http" is important - Composio requires HTTP transport - tools() retrieves all available Splitwise tools that the agent can use ```typescript const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); ``` ### 7. Initialize conversation and CLI interface What's happening: - We initialize an empty messages array to maintain conversation history - A readline interface is created to accept user input from the command line - Instructions are displayed to guide the user on how to interact with the agent ```typescript let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to splitwise, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); ``` ### 8. Handle user input and stream responses with real-time tool feedback What's happening: - We use streamText instead of generateText to stream responses in real-time - toolChoice: "auto" allows the model to decide when to use Splitwise tools - stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations - onStepFinish callback displays which tools are being used in real-time - We iterate through the text stream to create a typewriter effect as the agent responds - The complete response is added to conversation history to maintain context - Errors are caught and displayed with helpful retry suggestions ```typescript rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["splitwise"], }); const mcpUrl = session.mcp.url; const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to splitwise, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Conclusion You've successfully built a Splitwise agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback. Key features of this implementation: - Real-time streaming responses for a better user experience with typewriter effect - Live tool execution feedback showing which tools are being used as the agent works - Dynamic tool loading through Composio's Tool Router with secure authentication - Multi-step tool execution with configurable step limits (up to 10 steps) - Comprehensive error handling for robust agent execution - Conversation history maintenance for context-aware responses You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## How to build Splitwise MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/splitwise/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/splitwise/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/splitwise/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/splitwise/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/splitwise/framework/codex) - [OpenClaw](https://composio.dev/toolkits/splitwise/framework/openclaw) - [Hermes](https://composio.dev/toolkits/splitwise/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/splitwise/framework/cli) - [Google ADK](https://composio.dev/toolkits/splitwise/framework/google-adk) - [LangChain](https://composio.dev/toolkits/splitwise/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/splitwise/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/splitwise/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/splitwise/framework/crew-ai) ## Related Toolkits - [Stripe](https://composio.dev/toolkits/stripe) - Stripe is a global online payments platform offering APIs for managing payments, customers, and subscriptions. Trusted by businesses for secure, efficient, and scalable payment processing worldwide. - [Alpha vantage](https://composio.dev/toolkits/alpha_vantage) - Alpha Vantage is a financial data platform offering real-time and historical stock market APIs. Get instant, reliable access to equities, forex, and technical analysis data for smarter trading decisions. - [Altoviz](https://composio.dev/toolkits/altoviz) - Altoviz is a cloud-based billing and invoicing platform for businesses. It streamlines online payments, expense tracking, and customizable invoice management. - [Benzinga](https://composio.dev/toolkits/benzinga) - Benzinga provides real-time financial news and data APIs for market coverage. It helps you track breaking news and actionable market insights instantly. - [Brex](https://composio.dev/toolkits/brex) - Brex provides corporate credit cards and spend management tailored for startups and tech businesses. It helps optimize company cash flow, streamline accounting, and accelerate business growth. - [Chaser](https://composio.dev/toolkits/chaser) - Chaser is accounts receivable automation software that sends invoice reminders and helps businesses get paid faster. It streamlines the collections process to save time and improve cash flow. - [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time. - [Coinbase](https://composio.dev/toolkits/coinbase) - Coinbase is a platform for buying, selling, and storing cryptocurrency. It makes exchanging and managing crypto simple and secure for everyone. - [Coinranking](https://composio.dev/toolkits/coinranking) - Coinranking is a comprehensive cryptocurrency market data platform offering access to real-time coin prices, market caps, and historical data. Get accurate, up-to-date stats for thousands of digital assets in one place. - [Coupa](https://composio.dev/toolkits/coupa) - Coupa is a business spend management platform for procurement, invoicing, and expenses. It helps organizations streamline purchasing, control costs, and gain complete visibility over financial operations. - [CurrencyScoop](https://composio.dev/toolkits/currencyscoop) - CurrencyScoop is a developer-friendly API for real-time and historical currency exchange rates. Easily access fiat and crypto data for smart, up-to-date financial applications. - [Daffy](https://composio.dev/toolkits/daffy) - Daffy is a modern charitable giving platform with a donor-advised fund. Easily set aside funds, grow them tax-free, and donate to over 1.7 million U.S. charities. - [Eagle doc](https://composio.dev/toolkits/eagle_doc) - Eagle doc is an AI-powered OCR API for invoices and receipts. It delivers fast, reliable, and accurate document data extraction for seamless automation. - [Elorus](https://composio.dev/toolkits/elorus) - Elorus is an online invoicing and time-tracking software for freelancers and small businesses. Easily manage finances, bill clients, and track work in one place. - [Eodhd apis](https://composio.dev/toolkits/eodhd_apis) - Eodhd apis delivers comprehensive financial data, including live and historical stock prices, via robust APIs. Easily access reliable, up-to-date market insights to power your apps, dashboards, and analytics. - [Fidel api](https://composio.dev/toolkits/fidel_api) - Fidel api is a secure platform for linking payment cards to web and mobile apps. It enables real-time card transaction monitoring and event-based automation for businesses. - [Finage](https://composio.dev/toolkits/finage) - Finage is a secure API platform delivering real-time and historical financial data for stocks, forex, crypto, indices, and commodities. It empowers developers and businesses to access, analyze, and act on market data instantly. - [Finmei](https://composio.dev/toolkits/finmei) - Finmei is an invoicing tool that simplifies billing, invoice management, and expense tracking. Ideal for automating and organizing your business finances in one place. - [Fixer](https://composio.dev/toolkits/fixer) - Fixer is a currency data API offering real-time and historical exchange rates for 170 currencies. Instantly access accurate, up-to-date forex data for your applications and workflows. - [Fixer io](https://composio.dev/toolkits/fixer_io) - Fixer.io is a lightweight API for real-time and historical foreign exchange rates. It makes global currency conversion fast, accurate, and hassle-free. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Splitwise MCP? With a standalone Splitwise MCP server, the agents and LLMs can only access a fixed set of Splitwise tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Splitwise and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Vercel AI SDK v6? Yes, you can. Vercel AI SDK v6 fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Splitwise tools. ### Can I manage the permissions and scopes for Splitwise while using Tool Router? Yes, absolutely. You can configure which Splitwise scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Splitwise data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)