How to integrate Telnyx MCP with CrewAI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Telnyx Logo
CrewAI Logo
divider

Introduction

This guide walks you through connecting Telnyx to CrewAI 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, delete a notification profile by id through natural language commands.

This guide will help you understand how to give your CrewAI 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.

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Telnyx connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Telnyx
  • Build a conversational loop where your agent can execute Telnyx operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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 & Triggers

Tools
Create NetworkTool to create a new network.
Create Notification ChannelTool to create a notification channel.
Create Notification ProfileTool to create a notification profile.
Create Notification SettingTool to add a notification setting.
Delete NetworkTool to delete a network by id.
Delete Notification ChannelTool to delete a notification channel by id.
Delete Notification ProfileTool to delete a notification profile by id.
Delete Notification SettingTool to delete a notification setting by id.
Get User BalanceTool to retrieve the current user account balance and credit details.
List Audit LogsTool to retrieve a list of audit log entries for your account.
List ConnectionsTool to retrieve all connections in your account.
List Dynamic Emergency EndpointsTool to list dynamic emergency endpoints.
List Messaging ProfilesTool to list messaging profiles.
List Messaging URL DomainsTool to list configured messaging url domains.
List Mobile Network OperatorsTool to list available mobile network operators.
List Network InterfacesTool to list all network interfaces for a specified network.
List NetworksTool to list all networks in your account.
List Notification ChannelsTool to list all notification channels.
List Notification Event ConditionsTool to list all notification event conditions.
List Notification EventsTool to list all notification events.
List Notification ProfilesTool to list all notification profiles.
List Phone NumbersTool to list phone numbers associated with your account.
List SSO Authentication ProvidersTool to retrieve all configured sso authentication providers.
Retrieve NetworkTool to retrieve details of a specific network by id.
Retrieve Notification ChannelTool to retrieve a notification channel by id.
Retrieve Notification ProfileTool to retrieve a notification profile by id.
Retrieve Notification SettingTool to retrieve a notification setting by id.
Update NetworkTool to update details of an existing network.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Telnyx connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

bash
pip install composio crewai crewai-tools python-dotenv
What's happening:
  • composio connects your agent to Telnyx via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools includes MCP helpers
  • python-dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model

Import dependencies

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter  # optional import if you plan to adapt tools
from composio import Composio
from dotenv import load_dotenv
import os
from crewai.mcp import MCPServerHTTP

load_dotenv()
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Telnyx MCP URL

Create a Composio Tool Router session for Telnyx

python
composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
session = composio.create(
    user_id=os.getenv("USER_ID"),
    toolkits=["telnyx"],
)
url = session.mcp.url
What's happening:
  • You create a Telnyx only session through Composio
  • Composio returns an MCP HTTP URL that exposes Telnyx tools

Configure the LLM

python
llm = LLM(
    model="gpt-5-mini",
    api_key=os.getenv("OPENAI_API_KEY"),
)
What's happening:
  • CrewAI will call this LLM for planning and responses
  • You can swap in a different model if needed

Attach the MCP server and create the agent

python
toolkit_agent = Agent(
    role="Telnyx Assistant",
    goal="Help users interact with Telnyx through natural language commands",
    backstory=(
        "You are an expert assistant with access to Telnyx tools. "
        "You can perform various Telnyx operations on behalf of the user."
    ),
    mcps=[
        MCPServerHTTP(
            url=url,
            streamable=True,
            cache_tools_list=True,
            headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")},
        ),
    ],
    llm=llm,
    verbose=True,
    max_iter=10,
)
What's happening:
  • MCPServerHTTP connects the agent to the Telnyx MCP endpoint
  • cache_tools_list saves a tools catalog for faster subsequent runs
  • verbose helps you see what the agent is doing

Add a REPL loop with Task and Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to perform Telnyx operations.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Based on the conversation history:\n{conversation_context}\n\n"
            f"Current user request: {user_input}\n\n"
            f"Please help the user with their Telnyx related request."
        ),
        expected_output="A helpful response addressing the user's request",
        agent=toolkit_agent,
    )

    crew = Crew(
        agents=[toolkit_agent],
        tasks=[task],
        verbose=False,
    )

    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's happening:
  • You build a simple chat loop and keep a running context
  • Each user turn becomes a Task handled by the same agent
  • Crew executes the task and returns a response

Run the application

python
if __name__ == "__main__":
    main()
What's happening:
  • Standard Python entry point so you can run python crewai_telnyx_agent.py

Complete Code

Here's the complete code to get you started with Telnyx and CrewAI:

python
# file: crewai_telnyx_agent.py
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter  # optional
from composio import Composio
from dotenv import load_dotenv
import os
from crewai.mcp import MCPServerHTTP

load_dotenv()

def main():
    # Initialize Composio and create a Telnyx session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["telnyx"],
    )
    url = session.mcp.url

    # Configure LLM
    llm = LLM(
        model="gpt-5-mini",
        api_key=os.getenv("OPENAI_API_KEY"),
    )

    # Create Telnyx assistant agent
    toolkit_agent = Agent(
        role="Telnyx Assistant",
        goal="Help users interact with Telnyx through natural language commands",
        backstory=(
            "You are an expert assistant with access to Telnyx tools. "
            "You can perform various Telnyx operations on behalf of the user."
        ),
        mcps=[
            MCPServerHTTP(
                url=url,
                streamable=True,
                cache_tools_list=True,
                headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")},
            ),
        ],
        llm=llm,
        verbose=True,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Try asking the agent to perform Telnyx operations.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Based on the conversation history:\n{conversation_context}\n\n"
                f"Current user request: {user_input}\n\n"
                f"Please help the user with their Telnyx related request."
            ),
            expected_output="A helpful response addressing the user's request",
            agent=toolkit_agent,
        )

        crew = Crew(
            agents=[toolkit_agent],
            tasks=[task],
            verbose=False,
        )

        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

if __name__ == "__main__":
    main()

Conclusion

You now have a CrewAI agent connected to Telnyx through Composio's Tool Router. The agent can perform Telnyx operations through natural language commands. Next steps:
  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations

How to build Telnyx MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Telnyx MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Telnyx MCP with Claude Agent SDK

Google ADK

Google ADK

Use Telnyx MCP with Google ADK

LangChain

LangChain

Use Telnyx MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Telnyx MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Telnyx MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Telnyx MCP with LlamaIndex

FAQ

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 CrewAI?

Yes, you can. CrewAI 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.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free