# How to integrate Helpdesk MCP with LlamaIndex ```json { "title": "How to integrate Helpdesk MCP with LlamaIndex", "toolkit": "Helpdesk", "toolkit_slug": "helpdesk", "framework": "LlamaIndex", "framework_slug": "llama-index", "url": "https://composio.dev/toolkits/helpdesk/framework/llama-index", "markdown_url": "https://composio.dev/toolkits/helpdesk/framework/llama-index.md", "updated_at": "2026-05-12T10:14:46.078Z" } ``` ## Introduction This guide walks you through connecting Helpdesk to LlamaIndex 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 LlamaIndex 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) - [Vercel AI SDK](https://composio.dev/toolkits/helpdesk/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/helpdesk/framework/mastra-ai) - [CrewAI](https://composio.dev/toolkits/helpdesk/framework/crew-ai) ## TL;DR Here's what you'll learn: - Set your OpenAI and Composio API keys - Install LlamaIndex and Composio packages - Create a Composio Tool Router session for Helpdesk - Connect LlamaIndex to the Helpdesk MCP server - Build a Helpdesk-powered agent using LlamaIndex - Interact with Helpdesk through natural language ## What is LlamaIndex? LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools. Key features include: - ReAct Agent: Reasoning and acting pattern for tool-using agents - MCP Tools: Native support for Model Context Protocol - Context Management: Maintain conversation context across interactions - Async Support: Built for async/await patterns ## 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: - Python 3.8/Node 16 or higher installed - A Composio account with the API key - An OpenAI API key - A Helpdesk account and project - Basic familiarity with async Python/Typescript ### 1. Getting API Keys for OpenAI, Composio, and Helpdesk No description provided. ### 2. Installing dependencies No description provided. ```python pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv ``` ```typescript npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv ``` ### 3. Set environment variables Create a .env file in your project root: These credentials will be used to: - Authenticate with OpenAI's GPT-5 model - Connect to Composio's Tool Router - Identify your Composio user session for Helpdesk access ```bash OPENAI_API_KEY=your-openai-api-key COMPOSIO_API_KEY=your-composio-api-key COMPOSIO_USER_ID=your-user-id ``` ### 4. Import modules No description provided. ```python import asyncio import os import dotenv from composio import Composio from composio_llamaindex import LlamaIndexProvider from llama_index.core.agent.workflow import ReActAgent from llama_index.core.workflow import Context from llama_index.llms.openai import OpenAI from llama_index.tools.mcp import BasicMCPClient, McpToolSpec dotenv.load_dotenv() ``` ```typescript import "dotenv/config"; import readline from "node:readline/promises"; import { stdin as input, stdout as output } from "node:process"; import { Composio } from "@composio/core"; import { mcp } from "@llamaindex/tools"; import { agent as createAgent } from "@llamaindex/workflow"; import { openai } from "@llamaindex/openai"; dotenv.config(); ``` ### 5. Load environment variables and initialize Composio No description provided. ```python OPENAI_API_KEY = os.getenv("OPENAI_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not OPENAI_API_KEY: raise ValueError("OPENAI_API_KEY is not set in the environment") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment") ``` ```typescript const OPENAI_API_KEY = process.env.OPENAI_API_KEY; const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY; const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID; if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set"); if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set"); ``` ### 6. Create a Tool Router session and build the agent function What's happening here: - We create a Composio client using your API key and configure it with the LlamaIndex provider - We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, helpdesk) - The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools - LlamaIndex will connect to this endpoint to dynamically discover and use the available Helpdesk tools. - The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent. ```python async def build_agent() -> ReActAgent: composio_client = Composio( api_key=COMPOSIO_API_KEY, provider=LlamaIndexProvider(), ) session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["helpdesk"], ) mcp_url = session.mcp.url print(f"Composio MCP URL: {mcp_url}") mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY}) mcp_tool_spec = McpToolSpec(client=mcp_client) tools = await mcp_tool_spec.to_tool_list_async() llm = OpenAI(model="gpt-5") description = "An agent that uses Composio Tool Router MCP tools to perform Helpdesk actions." system_prompt = """ You are a helpful assistant connected to Composio Tool Router. Use the available tools to answer user queries and perform Helpdesk actions. """ return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True) ``` ```typescript async function buildAgent() { console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`); console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`); const composio = new Composio({ apiKey: COMPOSIO_API_KEY, provider: new LlamaindexProvider(), }); const session = await composio.create( COMPOSIO_USER_ID!, { toolkits: ["helpdesk"], }, ); const mcpUrl = session.mcp.url; console.log(`Composio Tool Router MCP URL: ${mcpUrl}`); const server = mcp({ url: mcpUrl, clientName: "composio_tool_router_with_llamaindex", requestInit: { headers: { "x-api-key": COMPOSIO_API_KEY!, }, }, // verbose: true, }); const tools = await server.tools(); const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" }); const agent = createAgent({ name: "composio_tool_router_with_llamaindex", description : "An agent that uses Composio Tool Router MCP tools to perform actions.", systemPrompt: "You are a helpful assistant connected to Composio Tool Router."+ "Use the available tools to answer user queries and perform Helpdesk actions." , llm, tools, }); return agent; } ``` ### 7. Create an interactive chat loop No description provided. ```python async def chat_loop(agent: ReActAgent) -> None: ctx = Context(agent) print("Type 'quit', 'exit', or Ctrl+C to stop.") while True: try: user_input = input("\nYou: ").strip() except (KeyboardInterrupt, EOFError): print("\nBye!") break if not user_input or user_input.lower() in {"quit", "exit"}: print("Bye!") break try: print("Agent: ", end="", flush=True) handler = agent.run(user_input, ctx=ctx) async for event in handler.stream_events(): # Stream token-by-token from LLM responses if hasattr(event, "delta") and event.delta: print(event.delta, end="", flush=True) # Show tool calls as they happen elif hasattr(event, "tool_name"): print(f"\n[Using tool: {event.tool_name}]", flush=True) # Get final response response = await handler print() # Newline after streaming except KeyboardInterrupt: print("\n[Interrupted]") continue except Exception as e: print(f"\nError: {e}") ``` ```typescript async function chatLoop(agent: ReturnType) { const rl = readline.createInterface({ input, output }); console.log("Type 'quit' or 'exit' to stop."); while (true) { let userInput: string; try { userInput = (await rl.question("\nYou: ")).trim(); } catch { console.log("\nAgent: Bye!"); break; } if (!userInput) { continue; } const lower = userInput.toLowerCase(); if (lower === "quit" || lower === "exit") { console.log("Agent: Bye!"); break; } try { process.stdout.write("Agent: "); const stream = agent.runStream(userInput); let finalResult: any = null; for await (const event of stream) { // The event.data contains the streamed content const data: any = event.data; // Check for streaming delta content if (data?.delta) { process.stdout.write(data.delta); } // Store final result for fallback if (data?.result || data?.message) { finalResult = data; } } // If no streaming happened, show the final result if (finalResult) { const answer = finalResult.result ?? finalResult.message?.content ?? finalResult.message ?? ""; if (answer && typeof answer === "string" && !answer.includes("[object")) { process.stdout.write(answer); } } console.log(); // New line after streaming completes } catch (err: any) { console.error("\nAgent error:", err?.message ?? err); } } rl.close(); } ``` ### 8. Define the main entry point What's happening here: - We're orchestrating the entire application flow - The agent gets built with proper error handling - Then we kick off the interactive chat loop so you can start talking to Helpdesk ```python async def main() -> None: agent = await build_agent() await chat_loop(agent) if __name__ == "__main__": # Handle Ctrl+C gracefully signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0))) try: asyncio.run(main()) except KeyboardInterrupt: print("\nBye!") ``` ```typescript async function main() { try { const agent = await buildAgent(); await chatLoop(agent); } catch (err) { console.error("Failed to start agent:", err); process.exit(1); } } main(); ``` ### 9. Run the agent When prompted, authenticate and authorise your agent with Helpdesk, then start asking questions. ```bash python llamaindex_agent.py ``` ```typescript npx ts-node llamaindex-agent.ts ``` ## Complete Code ```python import asyncio import os import signal import dotenv from composio import Composio from composio_llamaindex import LlamaIndexProvider from llama_index.core.agent.workflow import ReActAgent from llama_index.core.workflow import Context from llama_index.llms.openai import OpenAI from llama_index.tools.mcp import BasicMCPClient, McpToolSpec dotenv.load_dotenv() OPENAI_API_KEY = os.getenv("OPENAI_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not OPENAI_API_KEY: raise ValueError("OPENAI_API_KEY is not set") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set") async def build_agent() -> ReActAgent: composio_client = Composio( api_key=COMPOSIO_API_KEY, provider=LlamaIndexProvider(), ) session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["helpdesk"], ) mcp_url = session.mcp.url print(f"Composio MCP URL: {mcp_url}") mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY}) mcp_tool_spec = McpToolSpec(client=mcp_client) tools = await mcp_tool_spec.to_tool_list_async() llm = OpenAI(model="gpt-5") description = "An agent that uses Composio Tool Router MCP tools to perform Helpdesk actions." system_prompt = """ You are a helpful assistant connected to Composio Tool Router. Use the available tools to answer user queries and perform Helpdesk actions. """ return ReActAgent( tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True, ); async def chat_loop(agent: ReActAgent) -> None: ctx = Context(agent) print("Type 'quit', 'exit', or Ctrl+C to stop.") while True: try: user_input = input("\nYou: ").strip() except (KeyboardInterrupt, EOFError): print("\nBye!") break if not user_input or user_input.lower() in {"quit", "exit"}: print("Bye!") break try: print("Agent: ", end="", flush=True) handler = agent.run(user_input, ctx=ctx) async for event in handler.stream_events(): # Stream token-by-token from LLM responses if hasattr(event, "delta") and event.delta: print(event.delta, end="", flush=True) # Show tool calls as they happen elif hasattr(event, "tool_name"): print(f"\n[Using tool: {event.tool_name}]", flush=True) # Get final response response = await handler print() # Newline after streaming except KeyboardInterrupt: print("\n[Interrupted]") continue except Exception as e: print(f"\nError: {e}") async def main() -> None: agent = await build_agent() await chat_loop(agent) if __name__ == "__main__": # Handle Ctrl+C gracefully signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0))) try: asyncio.run(main()) except KeyboardInterrupt: print("\nBye!") ``` ```typescript import "dotenv/config"; import readline from "node:readline/promises"; import { stdin as input, stdout as output } from "node:process"; import { Composio } from "@composio/core"; import { LlamaindexProvider } from "@composio/llamaindex"; import { mcp } from "@llamaindex/tools"; import { agent as createAgent } from "@llamaindex/workflow"; import { openai } from "@llamaindex/openai"; dotenv.config(); const OPENAI_API_KEY = process.env.OPENAI_API_KEY; const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY; const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID; if (!OPENAI_API_KEY) { throw new Error("OPENAI_API_KEY is not set in the environment"); } if (!COMPOSIO_API_KEY) { throw new Error("COMPOSIO_API_KEY is not set in the environment"); } if (!COMPOSIO_USER_ID) { throw new Error("COMPOSIO_USER_ID is not set in the environment"); } async function buildAgent() { console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`); console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`); const composio = new Composio({ apiKey: COMPOSIO_API_KEY, provider: new LlamaindexProvider(), }); const session = await composio.create( COMPOSIO_USER_ID!, { toolkits: ["helpdesk"], }, ); const mcpUrl = session.mcp.url; console.log(`Composio Tool Router MCP URL: ${mcpUrl}`); const server = mcp({ url: mcpUrl, clientName: "composio_tool_router_with_llamaindex", requestInit: { headers: { "x-api-key": COMPOSIO_API_KEY!, }, }, // verbose: true, }); const tools = await server.tools(); const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" }); const agent = createAgent({ name: "composio_tool_router_with_llamaindex", description: "An agent that uses Composio Tool Router MCP tools to perform actions.", systemPrompt: "You are a helpful assistant connected to Composio Tool Router."+ "Use the available tools to answer user queries and perform Helpdesk actions." , llm, tools, }); return agent; } async function chatLoop(agent: ReturnType) { const rl = readline.createInterface({ input, output }); console.log("Type 'quit' or 'exit' to stop."); while (true) { let userInput: string; try { userInput = (await rl.question("\nYou: ")).trim(); } catch { console.log("\nAgent: Bye!"); break; } if (!userInput) { continue; } const lower = userInput.toLowerCase(); if (lower === "quit" || lower === "exit") { console.log("Agent: Bye!"); break; } try { process.stdout.write("Agent: "); const stream = agent.runStream(userInput); let finalResult: any = null; for await (const event of stream) { // The event.data contains the streamed content const data: any = event.data; // Check for streaming delta content if (data?.delta) { process.stdout.write(data.delta); } // Store final result for fallback if (data?.result || data?.message) { finalResult = data; } } // If no streaming happened, show the final result if (finalResult) { const answer = finalResult.result ?? finalResult.message?.content ?? finalResult.message ?? ""; if (answer && typeof answer === "string" && !answer.includes("[object")) { process.stdout.write(answer); } } console.log(); // New line after streaming completes } catch (err: any) { console.error("\nAgent error:", err?.message ?? err); } } rl.close(); } async function main() { try { const agent = await buildAgent(); await chatLoop(agent); } catch (err: any) { console.error("Failed to start agent:", err?.message ?? err); process.exit(1); } } main(); ``` ## Conclusion You've successfully connected Helpdesk to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways: - Tool Router dynamically exposes Helpdesk tools through an MCP endpoint - LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations - The agent becomes more capable without increasing prompt size - Async Python provides clean, efficient execution of agent workflows You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter. ## 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) - [Vercel AI SDK](https://composio.dev/toolkits/helpdesk/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/helpdesk/framework/mastra-ai) - [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 LlamaIndex? Yes, you can. LlamaIndex 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)