Telnyx
Telnyx is a communications platform offering voice, messaging, and data services through a global private network.
Verdict
Common use cases
- Provision IoT networks from sprint planning chat
- Register webhook endpoints for SMS delivery events
- Wire notification profiles to route call alerts
- Audit and clean up unused telecom resources
- Script network teardown after QA cycles
Integration
- Vendor
- Telnyx
- Category
- other
- Auth
- API_KEY
- Tools
- 28
- Composio slug
telnyx
Tools
- Create Network
Tool to create a new network. use when you need to provision a fresh network resource before connecting devices.
- 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.
- Create Notification Profile
Tool to create a notification profile. use when you need to register a new profile to group notification channels and define notification settings.
- Create Notification Setting
Tool to add a notification setting. use after creating the event condition, profile, and channel.
- Delete Networkdestructive
Tool to delete a network by id. use when you have obtained the network's identifier and need to remove it permanently.
- Delete Notification Channeldestructive
Tool to delete a notification channel by id. use when you have the channel's identifier and need to remove it permanently.
- Delete Notification Profiledestructive
Tool to delete a notification profile by id. use when you have the profile's identifier and need to remove it permanently.
- Delete Notification Settingdestructive
Tool to delete a notification setting by id. use when you need to permanently remove an existing notification setting before reconfiguration.
- Get User Balance
Tool to retrieve the current user account balance and credit details. use after authenticating your account to check available balance.
- 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.
- List Connections
Tool to retrieve all connections in your account. use when you need to list connections with pagination, filtering, and sorting.
- 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".
- List Messaging Profiles
Tool to list messaging profiles. use when you need to retrieve messaging profiles with optional pagination.
- List Messaging URL Domains
Tool to list configured messaging url domains. use when you need to retrieve messaging url domains for a profile.
- 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.
- List Network Interfaces
Tool to list all network interfaces for a specified network. use after retrieving a network's id to enumerate its interfaces.
- List Networks
Tool to list all networks in your account. use when you need to retrieve networks with optional pagination and filtering.
- 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.
- 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.
- List Notification Events
Tool to list all notification events. use when you need to retrieve and paginate available notification events.
- List Notification Profiles
Tool to list all notification profiles. use when you need to retrieve and paginate your notification profiles with optional pagination.
- 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.
- List SSO Authentication Providers
Tool to retrieve all configured sso authentication providers. use after authenticating to enumerate your organization's sso providers.
- 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.
- 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.
- 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.
- 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.
- 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.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations tab. 2. Click 'Add Integration' and select Telnyx from the list. 3. Log in to your Telnyx account, go to the API Keys section under your profile, and generate a new key with permissions for Networks and Notifications. 4. Copy the key and paste it into the Switchy connection dialog, then click 'Connect'. 5. Switchy will verify the key and confirm the connection — you'll see a green checkmark when it succeeds. 6. Open any Space, type '@Telnyx create a notification channel for webhook callbacks' and send the message. 7. The MCP will respond with the channel ID and confirmation — if you see that, the integration is working. 8. To test deletion, ask '@Telnyx delete notification channel [ID]' using the ID from step 7.
What teammates see: by default, memories from Telnyx are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Provision Dev Network
@Telnyx create a new network named 'staging-iot-fleet' for our QA environment. Use default settings and return the network ID.Open in a Space →
Register Webhook Channel
@Telnyx create a notification channel of type webhook pointing to https://api.example.com/telnyx-events. Label it 'sms-delivery-receipts'.Open in a Space →
Build Notification Profile
@Telnyx create a notification profile called 'production-alerts' and list the channels it should include.Open in a Space →
Audit Active Networks
@Telnyx list all active networks in our account and show their IDs, names, and creation dates.Open in a Space →
Teardown Test Resources
@Telnyx delete the network with ID [network-id] and remove any associated notification settings.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@telnyx list all active notification channels and show which profiles they're attached to
Here's what I found in your Telnyx account: **Active Notification Channels (4 total)** - **webhook-prod** (webhook) → attached to "Production Alerts" profile - **sms-oncall** (SMS, +1-555-0199) → attached to "On-Call Notifications" - **email-ops** (email, ops@company.com) → attached to "Production Alerts" and "Billing Notices" - **webhook-dev** (webhook) → not attached to any profile The webhook-dev channel isn't currently receiving notifications since it's unattached. Would you like me to associate it with a profile or remove it?
This read-heavy example shows how the MCP surfaces relationships between Telnyx notification primitives. Requires API key with read scope for notification resources. Useful for auditing alert routing before making changes, though the MCP won't show historical delivery logs.
@telnyx create a new SMS notification channel using +1-555-0142 and attach it to the "Incident Response" profile
I've created the SMS notification channel and linked it: **New Channel Created** - Channel ID: `ntc_abc123xyz` - Type: SMS - Destination: +1-555-0142 - Status: Active **Attached to Profile** - Profile: "Incident Response" (ID: `ntp_def456uvw`) - Existing channels in this profile: 2 (webhook-incidents, email-oncall) The channel is live. Any notification settings tied to "Incident Response" will now send SMS to this number. Test it by triggering a low-priority event first to confirm delivery.
This write example demonstrates the MCP's ability to provision and wire notification infrastructure in one prompt. Side-effect: the phone number will immediately start receiving alerts if the profile has active notification settings. Confirm the number is correct before running—Telnyx bills per SMS sent.
@telnyx review all my networks and recommend which ones can be safely deleted based on zero device connections in the last 90 days
I checked your 7 Telnyx networks and found 3 candidates for deletion: **Safe to Delete (no devices, 90+ days idle)** 1. **staging-test-vpc** (ID: `net_123abc`) — created 140 days ago, 0 devices ever connected 2. **demo-environment** (ID: `net_456def`) — created 210 days ago, last device disconnected 95 days ago 3. **legacy-pilot** (ID: `net_789ghi`) — created 380 days ago, 0 devices in last 120 days **Keep (active or recent activity)** - production-primary, dev-sandbox, qa-cluster, partner-integration Deleting these 3 would reduce monthly network overhead. Want me to remove them, or should we archive their configs first?
This synthesis example pairs the MCP's network-listing tool with the AI's reasoning to surface cleanup opportunities. The MCP reads network metadata but doesn't track billing impact—confirm cost savings separately. Deletion is permanent and can't be undone, so verify no hidden dependencies (firewall rules, DNS records) before proceeding.
Use-case deep-dives
When Telnyx beats PagerDuty for small dev teams
A 6-person engineering team runs weekly on-call rotations and wants SMS alerts for production incidents without paying PagerDuty's per-seat pricing. Telnyx wins here if you already have alerting logic in your monitoring stack and just need the SMS delivery layer. You create one notification profile per rotation week, attach an SMS channel with the on-call engineer's number, and wire your existing alert webhooks to Telnyx's notification settings. The 28-tool MCP gives you full CRUD on channels and profiles, so swapping the on-call number is a single API call in your rotation script. The trade-off: if you need escalation policies or incident acknowledgment workflows, you're building that yourself. If your team just needs reliable SMS delivery and you're comfortable scripting the rotation logic, Telnyx is the cheaper, simpler call.
Telnyx for support teams with custom IVR needs
A 12-person customer success team wants to offer voice callbacks when wait times exceed 5 minutes, and their existing helpdesk (Zendesk, Intercom) doesn't support outbound calling. Telnyx is the right fit if you're willing to build the queue logic and callback scheduler yourself. The MCP's network and notification tools let you provision phone numbers, create voice channels, and trigger outbound calls when a callback is due. You'll script the integration between your helpdesk's API and Telnyx's notification settings to fire the call. This works well for teams under 20 agents where custom callback rules justify the engineering time. Beyond that scale, or if you need call recording and agent analytics out of the box, a full contact-center platform like Twilio Flex is the better investment. For lean teams with specific callback workflows, Telnyx delivers the voice layer without the bloat.
When Telnyx simplifies cross-region status notifications
A 10-person SaaS ops team runs services in 4 AWS regions and wants a single webhook endpoint per region to receive health-check failures, then route alerts to Slack, email, or SMS based on severity. Telnyx is a clean choice here because you can create one notification profile per region, attach multiple channels (webhook for Slack, SMS for critical alerts, email for summaries), and define notification settings that map health-check events to the right channel. The MCP's 28 tools give you programmatic control to add regions or swap channels as your infrastructure grows. The boundary: if your health-check logic is already in Datadog or New Relic, their native alerting is faster to set up. But if you're stitching together custom monitors or want a vendor-neutral notification layer that doesn't lock you into one observability platform, Telnyx keeps your alerting config portable and scriptable.
Frequently asked
What does the Telnyx MCP do in Switchy?
The Telnyx MCP lets your team manage telecom infrastructure — networks, notification channels, and alert profiles — directly from Switchy's AI workspace. You can provision networks, set up SMS/voice/webhook notification channels, and configure event-driven alerts without switching to Telnyx's dashboard. It's built for teams running communication workflows who want AI assistance with their telecom stack.
Do I need admin access to connect Telnyx?
You need a Telnyx API key with permissions to create and delete networks, notification channels, profiles, and settings. Telnyx uses API key auth, not OAuth, so whoever connects it must have access to generate keys in the Telnyx portal. If your team restricts API key creation to admins, you'll need one of them to set it up.
Can the Telnyx MCP send SMS or make phone calls?
No. This MCP manages the infrastructure layer — networks, notification channels, and alert profiles — not message or call execution. If you need to send an SMS or place a call, you'll use Telnyx's messaging or voice APIs directly, or connect a different tool. Think of this MCP as the setup layer, not the runtime layer.
Why use this instead of the Telnyx dashboard?
The MCP is faster for repetitive provisioning tasks and lets you script network or notification setup inside Switchy's AI workflows. If you're spinning up test environments, cloning notification configs, or auditing channel settings, the MCP saves you from clicking through Telnyx's UI. For one-off changes or visual troubleshooting, the dashboard is still easier.
Who on the team should connect Telnyx?
Whoever manages your telecom infrastructure or has access to Telnyx API keys. This is typically a backend engineer, DevOps lead, or technical product manager. Once connected, anyone in your Switchy workspace can ask the AI to create networks or notification channels, but the API key's permissions control what actually happens.