# How to integrate Helpdesk MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Helpdesk MCP with Vercel AI SDK v6", "toolkit": "Helpdesk", "toolkit_slug": "helpdesk", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/helpdesk/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/helpdesk/framework/ai-sdk.md", "updated_at": "2026-05-12T10:14:46.078Z" } ``` ## Introduction This guide walks you through connecting Helpdesk to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Helpdesk agent that can list all agents available for support, show all active canned responses for tickets, retrieve contact details for a specific customer through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Helpdesk account through Composio's Helpdesk MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Helpdesk with - [OpenAI Agents SDK](https://composio.dev/toolkits/helpdesk/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/helpdesk/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/helpdesk/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/helpdesk/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/helpdesk/framework/codex) - [OpenClaw](https://composio.dev/toolkits/helpdesk/framework/openclaw) - [Hermes](https://composio.dev/toolkits/helpdesk/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/helpdesk/framework/cli) - [Google ADK](https://composio.dev/toolkits/helpdesk/framework/google-adk) - [LangChain](https://composio.dev/toolkits/helpdesk/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/helpdesk/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/helpdesk/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/helpdesk/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Helpdesk integration - Using Composio's Tool Router to dynamically load and access Helpdesk 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 Helpdesk MCP server, and what's possible with it? The Helpdesk MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Helpdesk account. It provides structured and secure access to your ticketing system, so your agent can perform actions like listing support agents, managing contacts, retrieving canned responses, and reviewing automation rules on your behalf. - Agent and team management: Instantly list all support agents and teams in your Helpdesk account, making it easy to organize and delegate customer inquiries. - Contact and subscription retrieval: Pull up detailed contact lists and subscription information so your agent always has up-to-date customer and account data at hand. - Canned response access: Let your agent fetch and suggest predefined reply templates, ensuring fast and consistent communication with customers. - Rules and automation overview: Review all configured automation rules in your helpdesk, helping your agent stay aligned with your business processes and ticketing workflows. - Account configuration insights: Retrieve lists of custom fields, reply addresses, licenses, and email domains to support personalized automation and account management tasks. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `HELPDESK_LIST_AGENTS` | List Agents | Retrieves all support agents (team members) in the HelpDesk account. Use this action to get a complete list of agents with their details including: - Agent profiles (name, email, avatar, job title) - Role assignments (owner, normal, viewer) - Team memberships - Status (active or invited) - Auto-assignment settings - Email signatures This action requires no parameters and returns all agents in the account. Useful for finding agent IDs, checking team composition, or verifying permissions. | | `HELPDESK_LIST_CANNED_RESPONSES` | List Canned Responses | Tool to list canned responses. Use when you need to retrieve all predefined reply templates for tickets. | | `HELPDESK_LIST_CUSTOM_FIELDS` | List Custom Fields | Tool to list all custom fields defined in the account. Use when you need to view or manage custom fields. Only callable after authentication. | | `HELPDESK_LIST_EMAIL_DOMAINS` | List Email Domains | Lists all email domains configured for the HelpDesk account. Returns a comprehensive list of all email domains set up in the HelpDesk account, including domain names, verification status, DNS records, and configuration flags. Email domains allow you to send and receive tickets via custom email addresses. Use this action to: - Get domain IDs and names for use in other API operations - Check domain verification and setup status - View DNS configuration requirements - Audit which domains are actively being used for inbox No parameters required - returns all email domains accessible to the authenticated account. | | `HELPDESK_LIST_LICENSES` | List Licenses | Retrieves all licenses (account configurations) for the authenticated HelpDesk account. A license represents a customer account and contains subscription information, global settings, default team/template assignments, and detected languages. Most accounts have one license. Use this action to: - Check account configuration and settings - Get account ID and metadata - View default team and template assignments - Inspect company settings and feature flags No parameters required - returns all licenses for the authenticated account. | | `HELPDESK_LIST_REPLY_ADDRESSES` | List Reply Addresses | Lists all reply addresses configured in the HelpDesk account. Reply addresses are email addresses used to receive and respond to support tickets. Each reply address must be associated with a verified email domain and can be used as the "From" address when sending ticket responses to customers. Use this action to: - Get all available reply addresses and their verification status - Retrieve reply address IDs for use in other operations (e.g., creating mailboxes) - Check which email domains are being used for reply addresses - Audit reply address configuration across the account No parameters required - returns all reply addresses accessible to the authenticated account. | | `HELPDESK_LIST_RULES` | List Rules | Tool to retrieve a list of rules configured in the account. Use after authentication when you need an overview of all automation rules. | | `HELPDESK_LIST_SUBSCRIPTIONS` | List Subscriptions | Lists all billing subscriptions for the HelpDesk account, including active, expired, canceled, and future subscriptions. Subscriptions represent the currently selected plan (team or enterprise) and number of paid agent slots. Use this tool to retrieve subscription details including plan codes, pricing, billing cycles, trial periods, and subscription states. Both filter parameters are optional - omit them to retrieve all subscriptions. | | `HELPDESK_LIST_TEAMS` | List Teams | Lists all teams in the HelpDesk account. Returns a comprehensive list of all teams configured in the HelpDesk account, including team IDs, names, settings, reply addresses, and integration configurations. Teams are organizational units that group agents and manage ticket routing. Use this action to: - Get team IDs for use in other API operations - Retrieve team names and configurations - Audit team settings and reply addresses - View team integration configurations No parameters required - returns all teams accessible to the authenticated account. | | `HELPDESK_LIST_TICKETS` | List Tickets | List all tickets from a specified silo with cursor-based pagination support. This tool retrieves tickets from the helpdesk system with flexible sorting and pagination. Use this when you need to retrieve tickets for monitoring, reporting, or processing. Key features: - Retrieves tickets from specified silo (tickets, archive, trash, or spam) - Supports cursor-based pagination for efficient navigation through large datasets - Configurable page size (1-100 tickets per page) - Multiple sort options (createdAt, updatedAt, lastMessageAt) in ascending or descending order Common use cases: - Get all open tickets: Use default parameters with silo='tickets' - Browse archived tickets: Set silo='archive' - Paginate through results: Use next_value and next_id from previous response | | `HELPDESK_LIST_TRUSTED_EMAILS` | List Trusted Emails | Tool to retrieve a list of trusted email addresses or domains. Use when managing your spam whitelist after authenticating. | | `HELPDESK_LIST_VIEWS` | List Views | Tool to list agent views. Use when you need to retrieve saved ticket views after authentication. | | `HELPDESK_LIST_WEBHOOKS` | List Webhooks | Lists all configured webhooks for the HelpDesk account. Webhooks allow you to receive real-time notifications about ticket events (creation, updates, status changes, assignments, etc.) sent as HTTP POST requests to your specified URLs. Use this action to view all active webhook configurations. | | `HELPDESK_VIEW_AGENT` | View Agent | Retrieves comprehensive details for a specific agent in the HelpDesk system. Returns complete agent information including profile details, role assignments, team memberships, status, settings, and signature configuration. Use this action when you need detailed information about a specific agent after obtaining their ID from the list_agents action. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Helpdesk MCP server is an implementation of the Model Context Protocol that connects your AI agent to Helpdesk. It provides structured and secure access so your agent can perform Helpdesk 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 Helpdesk 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 Helpdesk-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: ["helpdesk"], }); 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 Helpdesk 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 helpdesk, 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 Helpdesk 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: ["helpdesk"], }); 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 helpdesk, 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 Helpdesk 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 Helpdesk MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/helpdesk/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/helpdesk/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/helpdesk/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/helpdesk/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/helpdesk/framework/codex) - [OpenClaw](https://composio.dev/toolkits/helpdesk/framework/openclaw) - [Hermes](https://composio.dev/toolkits/helpdesk/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/helpdesk/framework/cli) - [Google ADK](https://composio.dev/toolkits/helpdesk/framework/google-adk) - [LangChain](https://composio.dev/toolkits/helpdesk/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/helpdesk/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/helpdesk/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/helpdesk/framework/crew-ai) ## Related Toolkits - [Aeroleads](https://composio.dev/toolkits/aeroleads) - Aeroleads is a B2B lead generation platform for finding business emails and phone numbers. Grow your sales pipeline faster with powerful prospecting tools. - [Autobound](https://composio.dev/toolkits/autobound) - Autobound is an AI-powered sales engagement platform that crafts hyper-personalized outreach and insights. It helps sales teams boost response rates and close more deals through tailored content and recommendations. - [Better proposals](https://composio.dev/toolkits/better_proposals) - Better Proposals is a web-based tool for crafting and sending professional proposals. It helps teams impress clients and close deals faster with slick, easy-to-use templates. - [Bidsketch](https://composio.dev/toolkits/bidsketch) - Bidsketch is a proposal software that helps businesses create professional proposals quickly and efficiently. It streamlines the proposal process, saving time while boosting client win rates. - [Bolna](https://composio.dev/toolkits/bolna) - Bolna is an AI platform for building conversational voice agents. It helps businesses automate support and streamline interactions through natural, voice-powered conversations. - [Botsonic](https://composio.dev/toolkits/botsonic) - Botsonic is a no-code AI chatbot builder for easily creating and deploying chatbots to your website. It empowers businesses to offer conversational experiences without writing code. - [Botstar](https://composio.dev/toolkits/botstar) - BotStar is a comprehensive chatbot platform for designing, developing, and training chatbots visually on Messenger and websites. It helps businesses automate conversations and customer interactions without coding. - [Callerapi](https://composio.dev/toolkits/callerapi) - CallerAPI is a white-label caller identification platform for branded caller ID and fraud prevention. It helps businesses boost customer trust while stopping spam, fraud, and robocalls. - [Callingly](https://composio.dev/toolkits/callingly) - Callingly is a lead response management platform that automates immediate call and text follow-ups with new leads. It helps sales teams boost response speed and close more deals by connecting seamlessly with CRMs and lead sources. - [Callpage](https://composio.dev/toolkits/callpage) - Callpage is a lead capture platform that lets businesses instantly connect with website visitors via callback. It boosts lead generation and increases your sales conversion rates. - [Clearout](https://composio.dev/toolkits/clearout) - Clearout is an AI-powered service for verifying, finding, and enriching email addresses. It boosts deliverability and helps you discover high-quality leads effortlessly. - [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. - [Convolo ai](https://composio.dev/toolkits/convolo_ai) - Convolo ai is an AI-powered communications platform for sales teams. It accelerates lead response and improves conversion rates by automating calls and integrating workflows. - [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment. - [Docsbot ai](https://composio.dev/toolkits/docsbot_ai) - Docsbot ai is a platform that lets you build custom AI chatbots trained on your documentation. It automates customer support and content generation, saving time and improving response quality. - [Emelia](https://composio.dev/toolkits/emelia) - Emelia is an all-in-one B2B prospecting platform for cold-email, LinkedIn outreach, and prospect research. It streamlines outbound campaigns so you can find, engage, and warm up leads faster. - [Findymail](https://composio.dev/toolkits/findymail) - Findymail is a B2B data provider offering verified email and phone contacts for sales prospecting. Enhance outreach with automated exports, email verification, and CRM enrichment. - [Freshdesk](https://composio.dev/toolkits/freshdesk) - Freshdesk is customer support software with ticketing and automation tools. It helps teams streamline helpdesk operations for faster, better customer support. - [Fullenrich](https://composio.dev/toolkits/fullenrich) - FullEnrich is a B2B contact enrichment platform that aggregates emails and phone numbers from 15+ data vendors. Instantly find and verify lead contact data to boost your outreach. - [Gatherup](https://composio.dev/toolkits/gatherup) - GatherUp is a customer feedback and online review management platform. It helps businesses boost their reputation by streamlining how they collect and manage customer feedback. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Helpdesk MCP? With a standalone Helpdesk MCP server, the agents and LLMs can only access a fixed set of Helpdesk tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Helpdesk 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 Helpdesk tools. ### Can I manage the permissions and scopes for Helpdesk while using Tool Router? Yes, absolutely. You can configure which Helpdesk 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 Helpdesk data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)