# How to integrate Telnyx MCP with LlamaIndex

```json
{
  "title": "How to integrate Telnyx MCP with LlamaIndex",
  "toolkit": "Telnyx",
  "toolkit_slug": "telnyx",
  "framework": "LlamaIndex",
  "framework_slug": "llama-index",
  "url": "https://composio.dev/toolkits/telnyx/framework/llama-index",
  "markdown_url": "https://composio.dev/toolkits/telnyx/framework/llama-index.md",
  "updated_at": "2026-05-12T10:28:04.717Z"
}
```

## Introduction

This guide walks you through connecting Telnyx to LlamaIndex 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 LlamaIndex 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)
- [Vercel AI SDK](https://composio.dev/toolkits/telnyx/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/telnyx/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/telnyx/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 Telnyx
- Connect LlamaIndex to the Telnyx MCP server
- Build a Telnyx-powered agent using LlamaIndex
- Interact with Telnyx 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 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:
- Python 3.8/Node 16 or higher installed
- A Composio account with the API key
- An OpenAI API key
- A Telnyx account and project
- Basic familiarity with async Python/Typescript

### 1. Getting API Keys for OpenAI, Composio, and Telnyx

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 Telnyx 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, telnyx)
- 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 Telnyx 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=["telnyx"],
    )

    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 Telnyx actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Telnyx 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: ["telnyx"],
    },
  );

  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 Telnyx 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<typeof createAgent>) {
  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 Telnyx
```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 Telnyx, 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=["telnyx"],
    )

    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 Telnyx actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Telnyx 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: ["telnyx"],
    },
  );

  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 Telnyx actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  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 Telnyx to LlamaIndex through Composio's Tool Router MCP layer.
Key takeaways:
- Tool Router dynamically exposes Telnyx 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 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)
- [Vercel AI SDK](https://composio.dev/toolkits/telnyx/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/telnyx/framework/mastra-ai)
- [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 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 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)