# How to integrate Zoho desk MCP with Vercel AI SDK v6

```json
{
  "title": "How to integrate Zoho desk MCP with Vercel AI SDK v6",
  "toolkit": "Zoho desk",
  "toolkit_slug": "zoho_desk",
  "framework": "Vercel AI SDK",
  "framework_slug": "ai-sdk",
  "url": "https://composio.dev/toolkits/zoho_desk/framework/ai-sdk",
  "markdown_url": "https://composio.dev/toolkits/zoho_desk/framework/ai-sdk.md",
  "updated_at": "2026-10-12T13:32:28.984Z"
}
```

## Introduction

This guide walks you through connecting Zoho desk to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Zoho desk agent that can list high-priority open support tickets, summarize recent customer interactions today, create new ticket for incoming email through natural language commands.
This guide will help you understand how to give your Vercel AI SDK agent real control over a Zoho desk account through Composio's Zoho desk MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Zoho desk with

- [Claude Code](https://composio.dev/toolkits/zoho_desk/framework/claude-code)
- [Cursor](https://composio.dev/toolkits/zoho_desk/framework/cursor)
- [ChatGPT](https://composio.dev/toolkits/zoho_desk/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/zoho_desk/framework/claude-cowork)
- [Antigravity](https://composio.dev/toolkits/zoho_desk/framework/antigravity)
- [OpenAI Agents SDK](https://composio.dev/toolkits/zoho_desk/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/zoho_desk/framework/claude-agents-sdk)
- [Codex](https://composio.dev/toolkits/zoho_desk/framework/codex)
- [Grok Build](https://composio.dev/toolkits/zoho_desk/framework/grok-build)
- [VS Code](https://composio.dev/toolkits/zoho_desk/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/zoho_desk/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/zoho_desk/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/zoho_desk/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/zoho_desk/framework/atomic-agent)
- [Google ADK](https://composio.dev/toolkits/zoho_desk/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/zoho_desk/framework/langchain)
- [Mastra AI](https://composio.dev/toolkits/zoho_desk/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/zoho_desk/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/zoho_desk/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/zoho_desk/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/zoho_desk/framework/autogen)

## TL;DR

Here's what you'll learn:
- How to set up and configure a Vercel AI SDK agent with Zoho desk integration
- Using Composio's Tool Router to dynamically load and access Zoho desk 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 Zoho desk MCP server, and what's possible with it?

The Zoho desk MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Zoho Desk account. It provides structured and secure access to your helpdesk workspace, so your agent can perform actions like tracking support tickets, managing customer conversations, automating ticket workflows, and generating support insights on your behalf.
- Ticket tracking and management: Let your agent create, update, and monitor support tickets, ensuring customer inquiries are handled efficiently.
- Automated workflow execution: Empower your agent to automate repetitive support processes, such as assigning tickets or escalating issues based on rules.
- Customer communication handling: Enable your agent to fetch and organize customer conversations, keeping your team informed and responsive.
- Insightful analytics and reporting: Have your agent generate detailed reports and metrics on ticket trends, response times, and agent performance for better decision-making.
- Collaboration with support teams: Allow your agent to coordinate with team members by tagging, commenting, or sharing ticket information securely within Zoho Desk.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `ZOHO_DESK_CREATE_CONTACT` | Create Contact | Tool to create a new contact in Zoho Desk with name, email, and other details. Use this action when you need to add a new contact to the system, such as when onboarding a new customer or registering a support requester. Returns the created contact with id and webUrl for downstream operations. |
| `ZOHO_DESK_CREATE_TICKET` | Create Ticket | Tool to create a new Zoho Desk ticket with subject, description, department, and requester details. Use when you need to create a support ticket in Zoho Desk. Returns the created ticket with id and webUrl for downstream chaining. |
| `ZOHO_DESK_DOWNLOAD_TICKET_ATTACHMENT` | Download Ticket Attachment | Download a file attachment from a Zoho Desk ticket by attachment ID. Use this action when you need to retrieve a specific file that was previously attached to a ticket. Requires both the ticket ID and the attachment ID to identify the file to download. |
| `ZOHO_DESK_GET_AGENT` | Get Agent | Tool to fetch details of a Zoho Desk agent. Use when you have an agent ID and need its full data, optionally including related resources. |
| `ZOHO_DESK_GET_AGENTS_COUNT` | Get Agents Count | Tool to get the total count of agents in Zoho Desk. Use when you need the number of agents optionally filtered by status, confirmation, or light agents. |
| `ZOHO_DESK_GET_CONTACT` | Get Contact | Tool to fetch details of a Zoho Desk contact. Use when you have a contact ID and need its full data, optionally including accounts or owner details. |
| `ZOHO_DESK_GET_CONTACTS_BY_IDS` | Get Contacts By IDs | Tool to fetch multiple contacts by their IDs using Zoho Desk's contactsByIds endpoint. |
| `ZOHO_DESK_GET_DEPARTMENT` | Get Department | Tool to fetch details of a Zoho Desk department by ID. |
| `ZOHO_DESK_GET_DEPARTMENT_LOGO` | Get Department Logo | Tool to get/download a department's logo from Zoho Desk. |
| `ZOHO_DESK_GET_DEPARTMENTS_COUNT` | Get Departments Count | Tool to get the total count of departments in Zoho Desk. Use when you need the number of departments, optionally filtered by enabled status. |
| `ZOHO_DESK_GET_TICKET` | Get Ticket | Get Ticket |
| `ZOHO_DESK_GET_TICKET_LATEST_THREAD` | Get Ticket Latest Thread | Tool to fetch the most recent thread of a ticket. Use when you need the latest conversation on a ticket. |
| `ZOHO_DESK_GET_TICKET_RESOLUTION` | Get Ticket Resolution | Get Ticket Resolution |
| `ZOHO_DESK_GET_TICKET_THREAD` | Get Ticket Thread | Tool to fetch a specific thread within a Zoho Desk ticket. Use when you need detailed thread information by ticket and thread IDs. |
| `ZOHO_DESK_LIST_AGENTS` | List Agents | Tool to list all agents in the Zoho Desk organization with optional filtering and pagination. Use when you need to retrieve multiple agents, optionally filtered by status or confirmation state. |
| `ZOHO_DESK_LIST_CONTACT_ACCOUNTS` | List Contact Accounts | Tool to list accounts associated with a Zoho Desk contact. Use when you need to retrieve the accounts linked to a specific contact. |
| `ZOHO_DESK_LIST_CONTACTS` | List Contacts | Tool to list contacts with filters and pagination. Use when you need to fetch contacts from Zoho Desk with optional filtering, sorting, or field selection. |
| `ZOHO_DESK_LIST_DEPARTMENTS` | List Departments | Tool to list all departments in the current Zoho Desk organization. |
| `ZOHO_DESK_LIST_ORGANIZATIONS` | List Organizations | Tool to list all organizations the current user belongs to. Use when you need to retrieve organization metadata like portal URLs, names, and editions. |
| `ZOHO_DESK_LIST_ROLES` | List Roles | List Roles |
| `ZOHO_DESK_LIST_ROLES_BY_IDS` | List Roles By IDs | List Roles By IDs |
| `ZOHO_DESK_LIST_TEAMS_IN_DEPARTMENT` | List Teams in Department | Tool to list teams in the specified Zoho Desk department. |
| `ZOHO_DESK_LIST_TICKET_CONVERSATIONS` | List Ticket Conversations | List Ticket Conversations |
| `ZOHO_DESK_LIST_TICKET_HISTORY` | List Ticket History | List audit and activity history for a ticket. History records describe ticket changes and actions. Use the conversation or thread actions instead when you need message and comment content. |
| `ZOHO_DESK_LIST_TICKETS` | List Tickets | List Tickets |
| `ZOHO_DESK_LIST_TICKET_THREADS` | List Ticket Threads | List message threads recorded on a Zoho Desk ticket. This returns threads only. Use the conversations action when comments and threads should be returned together. |
| `ZOHO_DESK_LIST_VIEWS` | List Views | List all ticket views in the Zoho Desk organization with pagination support. Views are saved filters that help organize and display tickets based on specific criteria. Use this action when you need to retrieve available views for filtering tickets, such as before calling the list tickets endpoint with a specific viewId. |
| `ZOHO_DESK_SEARCH` | Search | Search across Zoho Desk modules including tickets, accounts, contacts, and tasks using keywords or phrases. Use this action when you need to find records across multiple modules or within a specific module based on search criteria. Returns matching results with pagination support. |
| `ZOHO_DESK_UPDATE_ACCOUNT` | Update Account | Tool to update an existing Zoho Desk account's information such as name, email, phone, website, or description. Use this action when you need to modify account details after the account has been created. Only the fields you provide will be updated; other fields remain unchanged. |
| `ZOHO_DESK_UPDATE_MANY_TASKS` | Update Many Tasks | Update multiple tasks in a single call using Zoho Desk API. Endpoint: POST /api/v1/tasks/updateMany |
| `ZOHO_DESK_UPDATE_TICKET` | Update Ticket | Updates an existing Zoho Desk ticket by modifying one or more fields such as status, priority, assignee, description, or other ticket properties. Use this action when you need to modify an existing support ticket in Zoho Desk, such as changing its status, reassigning it to a different agent, updating priority, or adding information. Returns the updated ticket object with all current field values including the modified fields. |
| `ZOHO_DESK_UPLOAD_DEPARTMENT_LOGO` | Upload Department Logo | Tool to upload/update a department logo in Zoho Desk. |
| `ZOHO_DESK_UPLOAD_TICKET_ATTACHMENT` | Upload Ticket Attachment | Uploads a file attachment to a specific Zoho Desk ticket. The uploaded file becomes accessible as an attachment within the ticket for support agents and customers to reference. Use this action when you need to attach documentation, screenshots, logs, or any supporting files to an existing ticket. Maximum file size is 20 MB per attachment. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Zoho desk MCP server is an implementation of the Model Context Protocol that connects your AI agent to Zoho desk. It provides structured and secure access so your agent can perform Zoho desk 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 Zoho desk 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 Zoho desk-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: ["zoho_desk"],
  });

  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 Zoho desk 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 zoho_desk, 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 Zoho desk 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: ["zoho_desk"],
  });

  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 zoho_desk, 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 Zoho desk 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 Zoho desk MCP Agent with another framework

- [Claude Code](https://composio.dev/toolkits/zoho_desk/framework/claude-code)
- [Cursor](https://composio.dev/toolkits/zoho_desk/framework/cursor)
- [ChatGPT](https://composio.dev/toolkits/zoho_desk/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/zoho_desk/framework/claude-cowork)
- [Antigravity](https://composio.dev/toolkits/zoho_desk/framework/antigravity)
- [OpenAI Agents SDK](https://composio.dev/toolkits/zoho_desk/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/zoho_desk/framework/claude-agents-sdk)
- [Codex](https://composio.dev/toolkits/zoho_desk/framework/codex)
- [Grok Build](https://composio.dev/toolkits/zoho_desk/framework/grok-build)
- [VS Code](https://composio.dev/toolkits/zoho_desk/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/zoho_desk/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/zoho_desk/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/zoho_desk/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/zoho_desk/framework/atomic-agent)
- [Google ADK](https://composio.dev/toolkits/zoho_desk/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/zoho_desk/framework/langchain)
- [Mastra AI](https://composio.dev/toolkits/zoho_desk/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/zoho_desk/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/zoho_desk/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/zoho_desk/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/zoho_desk/framework/autogen)

## 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.
- [Botdog](https://composio.dev/toolkits/botdog) - Botdog is a LinkedIn outreach platform for managing campaigns, leads, messages, analytics, and sending accounts. It helps sales teams run outbound workflows and track performance from one place.
- [BotPenguin](https://composio.dev/toolkits/botpenguin) - BotPenguin is an AI chatbot platform for customer messaging, contacts, and conversations. It helps teams manage bot-led support and lead engagement across channels.
- [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.
- [Charla](https://composio.dev/toolkits/charla) - Charla is a live chat and AI customer-support platform for property teams. It helps manage guest conversations, property contacts, and support knowledge.
- [Chatforma](https://composio.dev/toolkits/chatforma) - Chatforma is a chatbot automation platform for building and managing bots. It helps teams run dialogs, segments, broadcasts, forms, and user updates from one place.
- [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.
- [Crisp](https://composio.dev/toolkits/crisp) - Crisp is a customer messaging platform for live chat, contacts, helpdesk, and campaigns. It helps support teams manage customer conversations from one shared workspace.
- [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.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Zoho desk MCP?

With a standalone Zoho desk MCP server, the agents and LLMs can only access a fixed set of Zoho desk tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Zoho desk 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 Zoho desk tools.

### Can I manage the permissions and scopes for Zoho desk while using Tool Router?

Yes, absolutely. You can configure which Zoho desk 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 Zoho desk data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
