Skip to main content
Glama
Sign In

Telnyx

by com.telnyx.api
OverviewDiscussionsAdmin

Server Details

The Telnyx MCP server is an official implementation of the Model Context Protocol that enables AI clients (like Claude Desktop, Cursor, and OpenAI Agents) to interact with Telnyx's telephony, messaging, and AI assistant APIs. It provides comprehensive capabilities including making and managing phone calls, sending SMS/MMS messages, purchasing and configuring phone numbers, creating AI assistants with custom instructions, managing cloud storage buckets, scraping and embedding website content, and handling integration secrets. The server exists as both a local implementation and a remotely hosted version, allowing developers to integrate real-world communication infrastructure directly into AI applications.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation5/5

The set splits cleanly into a three-step API workflow (list → get schema → invoke) and three app openers, each targeting a distinct app domain. Descriptions explicitly encode ordering ('use this first', 'after discovery', 'only after inspecting'), leaving little room for misselection. No two tools plausibly compete for the same request.

Naming Consistency4/5

Two internally consistent families: verb_api_noun for the API gateway (list_api_endpoints, get_api_endpoint_schema, invoke_api_endpoint) and open_<app> for the app launchers. The only wobble is 'api_endpoint' vs 'endpoint' in the get/invoke pair, which is cosmetic rather than confusing.

Tool Count5/5

Six tools is well-scoped: three minimal primitives expose the whole Telnyx API surface via progressive disclosure, plus three purpose-specific app launchers. Every tool earns its place with no redundant wrappers.

Completeness4/5

The list/inspect/invoke trio gives effectively full read/write coverage of the Telnyx API, so no dead ends for core operations. The app layer is only partially populated (number intelligence, usage/cost, voice) — other app surfaces are absent, though the generic API tools provide a workaround.

Available Tools

6 tools
get_api_endpoint_schemaA
Read-onlyIdempotent
Inspect

Use this after discovery to inspect a selected Telnyx API operation before invocation. Returns its name, description, and input schema.

Inputs: endpoint (required). Returns: name, description, inputSchema

invoke_api_endpointA
Destructive
Inspect

Use this only after inspecting an endpoint schema to invoke a Telnyx API operation. It may create, update, or delete data and returns the API result.

Inputs: args (required), endpoint_name (required). Returns: result, isError, endpointName

list_api_endpointsA
Read-onlyIdempotent
Inspect

Use this first to discover or search Telnyx API operations by name, resource, operation, or tag. Returns matching endpoint metadata.

Inputs: search_query. Returns: tools

open_number_intelligenceA
Read-onlyIdempotent
Inspect

Use this to open the Telnyx Number Intelligence MCP App for phone number lookup, validation, and enrichment. Returns the app resource URI.

Inputs: action. Returns: name, resourceUri

open_usage_cost_explorerA
Read-onlyIdempotent
Inspect

Use this to open the Telnyx Usage & Cost Explorer MCP App for usage and cost analysis. Returns the app resource URI.

Inputs: action. Returns: name, resourceUri

open_voice_monitorA
Read-onlyIdempotent
Inspect

Use this to open the Telnyx Voice Monitor MCP App for observing and troubleshooting voice traffic. Returns the app resource URI.

Inputs: action. Returns: name, resourceUri

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • TELNYX MCP Server

      tomaitagaki
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for TELNYX integration, enabling AI assistants to send SMS messages, make voice calls, and handle incoming communications via webhooks.
      MIT

    • Voyp MCP Server

      paulotaylor
      A
      license
      B
      quality
      C
      maintenance
      The Voyp MCP Server enables AI systems to integrate with VOYP's calling capabilities, allowing for secure telephony actions such as making calls, scheduling appointments, and tracking call statuses through the Model Context Protocol.
      7
      53 npm
      10
      MIT

    • Karya

      Dashy-E
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI agents hands to make phone calls, send messages, and handle CRM/task workflows. It runs with a simulated provider for zero-cost testing and can switch to real providers like Twilio and ElevenLabs.
      MIT
    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources