# How to integrate Telnyx MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Telnyx MCP with Vercel AI SDK v6", "toolkit": "Telnyx", "toolkit_slug": "telnyx", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/telnyx/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/telnyx/framework/ai-sdk.md", "updated_at": "2026-05-12T10:28:04.717Z" } ``` ## Introduction This guide walks you through connecting Telnyx to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Telnyx agent that can check current telnyx account balance, list recent audit logs for last week, create new sms notification channel through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Telnyx account through Composio's Telnyx MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Telnyx with - [OpenAI Agents SDK](https://composio.dev/toolkits/telnyx/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/telnyx/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/telnyx/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/telnyx/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/telnyx/framework/codex) - [OpenClaw](https://composio.dev/toolkits/telnyx/framework/openclaw) - [Hermes](https://composio.dev/toolkits/telnyx/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/telnyx/framework/cli) - [Google ADK](https://composio.dev/toolkits/telnyx/framework/google-adk) - [LangChain](https://composio.dev/toolkits/telnyx/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/telnyx/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/telnyx/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/telnyx/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Telnyx integration - Using Composio's Tool Router to dynamically load and access Telnyx 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 Telnyx MCP server, and what's possible with it? The Telnyx MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Telnyx account. It provides structured and secure access to your Telnyx communications platform, so your agent can manage networks, handle notification channels, monitor usage, and review account activities on your behalf. - Network provisioning and management: Easily create or delete network resources, allowing your agent to spin up new networks or remove unused ones as needed. - Notification channel automation: Set up, configure, or remove notification channels—including SMS, voice, email, or webhook endpoints—so your agent can handle event-driven communications flexibly. - Notification profile and settings control: Group and configure notification profiles and settings, enabling your agent to define how and when notifications are delivered for different events. - Real-time balance monitoring: Retrieve your current account balance and credit details, helping your agent keep tabs on usage and alert you before credits run low. - Comprehensive audit log access: Review detailed audit logs so your agent can surface recent changes, track resource modifications, and help maintain compliance or troubleshoot issues quickly. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `TELNYX_CREATE_NETWORK` | Create Network | Tool to create a new network. Use when you need to provision a fresh network resource before connecting devices. | | `TELNYX_CREATE_NOTIFICATION_CHANNEL` | Create Notification Channel | Tool to create a notification channel. Use when you need to register a channel (SMS, voice, email, or webhook) to receive notifications. E.g., create a webhook channel for event callbacks. | | `TELNYX_CREATE_NOTIFICATION_PROFILE` | Create Notification Profile | Tool to create a notification profile. Use when you need to register a new profile to group notification channels (SMS and voice) and define notification settings. Must be called before TELNYX_CREATE_NOTIFICATION_CHANNEL, as channel creation requires the notification_profile_id returned by this tool. | | `TELNYX_CREATE_NOTIFICATION_SETTING` | Create Notification Setting | Tool to add a notification setting. Use after creating the event condition, profile, and channel. All three UUID parameters must be fetched dynamically from their respective list/create endpoints; hardcoded IDs are not portable across accounts. | | `TELNYX_DELETE_NETWORK` | Delete Network | Tool to delete a network by ID. Use when you have obtained the network's identifier and need to remove it permanently. | | `TELNYX_DELETE_NOTIFICATION_CHANNEL` | Delete Notification Channel | Tool to delete a notification channel by ID. Use when you have the channel's identifier and need to remove it permanently. | | `TELNYX_DELETE_NOTIFICATION_PROFILE` | Delete Notification Profile | Tool to delete a notification profile by ID. Use when you have the profile's identifier and need to remove it permanently. | | `TELNYX_DELETE_NOTIFICATION_SETTING` | Delete Notification Setting | Tool to delete a notification setting by ID. Use when you need to permanently remove an existing notification setting before reconfiguration. | | `TELNYX_GET_BLACK_BOX_TEST_RESULTS` | Get Black Box Test Results | Tool to retrieve black box test results from Telnyx SETI Observability. Use when you need to check service health and test results, optionally filtering by product. | | `TELNYX_GET_USER_BALANCE` | Get User Balance | Tool to retrieve the current user account balance and credit details. Use after authenticating your account to check available balance. | | `TELNYX_LIST_AUDIT_LOGS` | List Audit Logs | Tool to retrieve a list of audit log entries for your account. Use when you need to review recent resource changes with optional pagination and date filters. | | `TELNYX_LIST_CONNECTIONS` | List Connections | Tool to retrieve all connections in your account. Use when you need to list connections with pagination, filtering, and sorting. | | `TELNYX_LIST_DYNAMIC_EMERGENCY_ENDPOINTS` | List Dynamic Emergency Endpoints | Tool to list dynamic emergency endpoints. Use when you need to retrieve dynamic emergency endpoint records, optionally filtered by status or country. Example: "List all activated endpoints in US". | | `TELNYX_LIST_GLOBAL_IP_HEALTH_CHECK_TYPES` | List Global IP Health Check Types | Tool to list all available global IP health check types. Use when you need to retrieve supported health check types for global IP configurations. | | `TELNYX_LIST_MESSAGING_PROFILES` | List Messaging Profiles | Tool to list messaging profiles. Use when you need to retrieve messaging profiles with optional pagination. | | `TELNYX_LIST_MESSAGING_URL_DOMAINS` | List Messaging URL Domains | Tool to list configured messaging URL domains. Use when you need to retrieve messaging URL domains for a profile. | | `TELNYX_LIST_MOBILE_NETWORK_OPERATORS` | List Mobile Network Operators | Tool to list available mobile network operators. Use when you need to discover operators optionally filtered by country code, operator name, or with pagination. | | `TELNYX_LIST_NETWORK_INTERFACES` | List Network Interfaces | Tool to list all network interfaces for a specified network. Use after retrieving a network's ID to enumerate its interfaces. | | `TELNYX_LIST_NETWORKS` | List Networks | Tool to list all networks in your account. Use when you need to retrieve networks with optional pagination and filtering. | | `TELNYX_LIST_NOTIFICATION_CHANNELS` | List Notification Channels | Tool to list all notification channels. Use when you need to retrieve and paginate existing notification channels, optionally filtering by channel type. | | `TELNYX_LIST_NOTIFICATION_EVENT_CONDITIONS` | List Notification Event Conditions | Tool to list all notification event conditions. Use when you need to retrieve and paginate notification event conditions, optionally filtering by associated record type. | | `TELNYX_LIST_NOTIFICATION_EVENTS` | List Notification Events | Tool to list all notification events with their IDs. Use to dynamically retrieve notification_event_condition_id values before configuring webhook subscriptions — IDs are account-specific and must not be hardcoded, as stale IDs silently prevent events (e.g., call routing, recording) from reaching the webhook. | | `TELNYX_LIST_NOTIFICATION_PROFILES` | List Notification Profiles | Tool to list all notification profiles. Use when you need to retrieve and paginate your notification profiles with optional pagination. | | `TELNYX_LIST_PHONE_NUMBERS` | List Phone Numbers | Tool to list phone numbers associated with your account. Use when you need to retrieve and filter your phone numbers with optional pagination and sorting. | | `TELNYX_LIST_SSO_AUTHENTICATION_PROVIDERS` | List SSO Authentication Providers | Tool to retrieve all configured SSO authentication providers. Use after authenticating to enumerate your organization's SSO providers. | | `TELNYX_RETRIEVE_NETWORK` | Retrieve Network | Tool to retrieve details of a specific network by ID. Use after obtaining the network's identifier to fetch its current attributes before update or delete operations. | | `TELNYX_RETRIEVE_NOTIFICATION_CHANNEL` | Retrieve Notification Channel | Tool to retrieve a notification channel by ID. Use after you have a channel ID and need its details, such as name, type, and status. | | `TELNYX_RETRIEVE_NOTIFICATION_PROFILE` | Retrieve Notification Profile | Tool to retrieve a notification profile by ID. Use after obtaining the profile ID when you need details about its webhook endpoints and subscribed events. | | `TELNYX_RETRIEVE_NOTIFICATION_SETTING` | Retrieve Notification Setting | Tool to retrieve a notification setting by ID. Use after obtaining the notification setting ID to fetch its details, such as status, parameters, and associated channel. | | `TELNYX_UPDATE_NETWORK` | Update Network | Tool to update details of an existing network. Use when you have a network's identifier and need to modify its name or tags. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Telnyx MCP server is an implementation of the Model Context Protocol that connects your AI agent to Telnyx. It provides structured and secure access so your agent can perform Telnyx 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 Telnyx 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 Telnyx-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: ["telnyx"], }); 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 Telnyx 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 telnyx, 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 Telnyx 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: ["telnyx"], }); 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 telnyx, 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 Telnyx 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 Telnyx MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/telnyx/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/telnyx/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/telnyx/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/telnyx/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/telnyx/framework/codex) - [OpenClaw](https://composio.dev/toolkits/telnyx/framework/openclaw) - [Hermes](https://composio.dev/toolkits/telnyx/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/telnyx/framework/cli) - [Google ADK](https://composio.dev/toolkits/telnyx/framework/google-adk) - [LangChain](https://composio.dev/toolkits/telnyx/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/telnyx/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/telnyx/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/telnyx/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. - [Dialmycalls](https://composio.dev/toolkits/dialmycalls) - Dialmycalls is a mass notification service for sending voice and text messages to contacts. It helps teams and organizations quickly broadcast urgent alerts and updates. - [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. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Telnyx MCP? With a standalone Telnyx MCP server, the agents and LLMs can only access a fixed set of Telnyx tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Telnyx 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 Telnyx tools. ### Can I manage the permissions and scopes for Telnyx while using Tool Router? Yes, absolutely. You can configure which Telnyx 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 Telnyx data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)