# How to integrate Dialmycalls MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Dialmycalls MCP with Vercel AI SDK v6", "toolkit": "Dialmycalls", "toolkit_slug": "dialmycalls", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/dialmycalls/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/dialmycalls/framework/ai-sdk.md", "updated_at": "2026-05-12T10:08:36.828Z" } ``` ## Introduction This guide walks you through connecting Dialmycalls to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Dialmycalls agent that can add a new contact named lisa chen, create a group for emergency alerts, delete the caller id ending in 4321 through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Dialmycalls account through Composio's Dialmycalls MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Dialmycalls with - [OpenAI Agents SDK](https://composio.dev/toolkits/dialmycalls/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/dialmycalls/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/dialmycalls/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/dialmycalls/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/dialmycalls/framework/codex) - [OpenClaw](https://composio.dev/toolkits/dialmycalls/framework/openclaw) - [Hermes](https://composio.dev/toolkits/dialmycalls/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/dialmycalls/framework/cli) - [Google ADK](https://composio.dev/toolkits/dialmycalls/framework/google-adk) - [LangChain](https://composio.dev/toolkits/dialmycalls/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/dialmycalls/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/dialmycalls/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/dialmycalls/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Dialmycalls integration - Using Composio's Tool Router to dynamically load and access Dialmycalls 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 Dialmycalls MCP server, and what's possible with it? The Dialmycalls MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Dialmycalls account. It provides structured and secure access to your mass notification system, allowing your agent to manage contacts, groups, and broadcast voice or text messages—all on your behalf. - Contact and group management: Effortlessly add, update, or remove individual contacts and organize recipients into groups for targeted messaging. - Account and sub-account administration: View your main account details, manage access (sub) accounts, and streamline team communication permissions. - Broadcast preparation: Set up caller IDs, upload or delete recordings, and get everything ready for your next mass notification campaign. - Data cleanup and maintenance: Easily delete old contacts, groups, caller IDs, or recordings to keep your Dialmycalls account organized and up to date. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `DIALMYCALLS_ADD_ACCESS_ACCOUNT` | Add Access Account | Tool to add a new access (sub) account. Use when you need to delegate dialing capabilities to another user after setting up your master account. | | `DIALMYCALLS_ADD_CONTACT` | Add Contact | Tool to add a contact to your contact list. Use when you need to store a new contact's phone (and optional name, email, or group) before sending messages. | | `DIALMYCALLS_ADD_GROUP` | Add Group | Tool to add a new contact group. Use after deciding the group name to organize recipients into groups. | | `DIALMYCALLS_DELETE_ACCESS_ACCOUNT` | Delete Access Account | Tool to delete an access (sub) account by ID. Use when removing a sub account after deprovisioning. | | `DIALMYCALLS_DELETE_CALLER_ID` | Delete Caller ID | Tool to delete a caller ID. Use when you need to permanently remove an existing caller ID no longer in use. | | `DIALMYCALLS_DELETE_CONTACT` | Delete Contact | Tool to delete a contact by ID. Use when you need to permanently remove a contact from your list. | | `DIALMYCALLS_DELETE_GROUP` | Delete Group | Tool to delete a contact group by ID. Use when you need to remove an existing contact group after confirming its ID. | | `DIALMYCALLS_DELETE_RECORDING` | Delete Recording | Tool to delete a recording by ID. Use when you need to permanently remove a custom recording after confirming its recording ID. | | `DIALMYCALLS_GET_ACCESS_ACCOUNT` | Get Access Account | Tool to retrieve an access (sub) account by ID. Use when you need to inspect the details of a specific sub-account. | | `DIALMYCALLS_GET_ACCOUNT` | Get Account | Tool to retrieve your main account details. Use when you need to confirm account ID, remaining credits, and status. | | `DIALMYCALLS_GET_CALLER_ID` | Get Caller ID | Tool to retrieve a caller ID by ID. Use when you need its details such as phone number and verification status. | | `DIALMYCALLS_GET_CONTACT` | Get Contact | Tool to retrieve a contact by its unique ID. Use when you need to fetch details of a specific contact from your account. | | `DIALMYCALLS_GET_GROUP` | Get Group | Tool to retrieve a contact group by ID. Use when you need to fetch group details after creating or updating a group. | | `DIALMYCALLS_GET_RECORDING` | Get Recording | Tool to retrieve a recording by ID. Use when you need details and file URL of an existing recording. | | `DIALMYCALLS_LIST_ACCESS_ACCOUNTS` | List Access Accounts | Tool to list all access (sub) accounts. Use when you need to retrieve paginated sub-account information for administration or reporting. | | `DIALMYCALLS_LIST_CALLER_I_DS` | List Caller IDs | Tool to list all caller IDs on the account. Use when you need to enumerate existing caller IDs before performing other operations. | | `DIALMYCALLS_LIST_CALLS` | List Calls | Tool to list all call broadcasts on the account. Use when you need to retrieve or manage call records with optional filters like name, type, status, dates, pagination, and sorting. | | `DIALMYCALLS_LIST_CONTACTS` | List Contacts | Tool to list all contacts in your contact list. Use when fetching paginated or filtered contact data for review (e.g., after adding or updating contacts). | | `DIALMYCALLS_LIST_DO_NOT_CONTACTS` | List Do Not Contacts | Tool to list all Do Not Contact entries. Use when you need to review or manage blocked phone numbers or emails in your account. Supports pagination and filtering by type and search. | | `DIALMYCALLS_LIST_GROUPS` | List Groups | Tool to list all contact groups. Use when you need an overview of existing groups before sending messages. | | `DIALMYCALLS_LIST_RECORDINGS` | List Recordings | Tool to list all recordings. Use when you need to retrieve your account's recordings for auditing or bulk management. | | `DIALMYCALLS_LIST_TEXTS` | List Text Broadcasts | Tool to list all outgoing text broadcasts. Use when you need to review past text broadcasts with filters for date, status, and pagination. | | `DIALMYCALLS_LIST_VANITY_NUMBERS` | List Vanity Numbers | Tool to list all vanity numbers. Use when you need to retrieve available vanity phone numbers with pagination support. | | `DIALMYCALLS_UPDATE_ACCESS_ACCOUNT` | Update Access Account | Tool to update an existing access (sub) account by ID. Use when you need to change details like email, phone, name, password, or activation status after account creation. | | `DIALMYCALLS_UPDATE_CALLER_ID` | Update Caller ID | Tool to update an existing caller ID by ID. Use when you need to change its phone number or display name. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Dialmycalls MCP server is an implementation of the Model Context Protocol that connects your AI agent to Dialmycalls. It provides structured and secure access so your agent can perform Dialmycalls 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 Dialmycalls 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 Dialmycalls-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: ["dialmycalls"], }); 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 Dialmycalls 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 dialmycalls, 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 Dialmycalls 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: ["dialmycalls"], }); 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 dialmycalls, 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 Dialmycalls 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 Dialmycalls MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/dialmycalls/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/dialmycalls/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/dialmycalls/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/dialmycalls/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/dialmycalls/framework/codex) - [OpenClaw](https://composio.dev/toolkits/dialmycalls/framework/openclaw) - [Hermes](https://composio.dev/toolkits/dialmycalls/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/dialmycalls/framework/cli) - [Google ADK](https://composio.dev/toolkits/dialmycalls/framework/google-adk) - [LangChain](https://composio.dev/toolkits/dialmycalls/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/dialmycalls/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/dialmycalls/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/dialmycalls/framework/crew-ai) ## Related Toolkits - [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable. - [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management. - [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place. - [Gong](https://composio.dev/toolkits/gong) - Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action. - [Microsoft teams](https://composio.dev/toolkits/microsoft_teams) - Microsoft Teams is a collaboration platform that combines chat, meetings, and file sharing within Microsoft 365. It keeps distributed teams connected and productive through seamless virtual communication. - [Slackbot](https://composio.dev/toolkits/slackbot) - Slackbot is a conversational automation tool for Slack that handles reminders, notifications, and automated responses. It boosts team productivity by streamlining onboarding, answering FAQs, and managing timely alerts—all right inside Slack. - [2chat](https://composio.dev/toolkits/_2chat) - 2chat is an API platform for WhatsApp and multichannel text messaging. It streamlines chat automation, group management, and real-time messaging for developers. - [Agent mail](https://composio.dev/toolkits/agent_mail) - Agent mail provides AI agents with dedicated email inboxes for sending, receiving, and managing emails. It empowers agents to communicate autonomously with people, services, and other agents—no human intervention needed. - [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place. - [Chatwork](https://composio.dev/toolkits/chatwork) - Chatwork is a team communication platform with group chats, file sharing, and task management. It helps businesses boost collaboration and streamline productivity. - [Clickmeeting](https://composio.dev/toolkits/clickmeeting) - ClickMeeting is a cloud-based platform for running online meetings and webinars. It helps businesses and individuals host, manage, and engage virtual audiences with ease. - [Confluence](https://composio.dev/toolkits/confluence) - Confluence is Atlassian's team collaboration and knowledge management platform. It helps your team organize, share, and update documents and project content in one secure workspace. - [Dailybot](https://composio.dev/toolkits/dailybot) - DailyBot streamlines team collaboration with chat-based standups, reminders, and polls. It keeps work flowing smoothly in your favorite messaging platforms. - [Dialpad](https://composio.dev/toolkits/dialpad) - Dialpad is a cloud-based business phone and contact center system for teams. It unifies voice, video, messaging, and meetings across your devices. - [Discord](https://composio.dev/toolkits/discord) - Discord is a real-time messaging and VoIP platform for communities and teams. It lets users chat, share media, and collaborate across public and private channels. - [Discordbot](https://composio.dev/toolkits/discordbot) - Discordbot is an automation tool for Discord servers that handles moderation, messaging, and user engagement. It helps communities run smoothly by automating routine and complex tasks. - [Echtpost](https://composio.dev/toolkits/echtpost) - Echtpost is a secure digital communication platform for encrypted document and message exchange. It ensures confidential data stays private and protected during transmission. - [Egnyte](https://composio.dev/toolkits/egnyte) - Egnyte is a cloud-based platform for secure file sharing, storage, and governance. It helps teams collaborate efficiently while maintaining data compliance and security. - [Google Meet](https://composio.dev/toolkits/googlemeet) - Google Meet is a secure video conferencing platform for virtual meetings, chat, and screen sharing. It helps teams connect, collaborate, and communicate seamlessly from anywhere. - [Heartbeat](https://composio.dev/toolkits/heartbeat) - Heartbeat is a plug-and-play platform for building and managing online communities. It helps you organize users, channels, events, and discussions in one place. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Dialmycalls MCP? With a standalone Dialmycalls MCP server, the agents and LLMs can only access a fixed set of Dialmycalls tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Dialmycalls 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 Dialmycalls tools. ### Can I manage the permissions and scopes for Dialmycalls while using Tool Router? Yes, absolutely. You can configure which Dialmycalls 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 Dialmycalls data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)