Telnyx MCP Server

Official

Official proxy connecting your IDE to Telnyx's remote MCP server

How to install ↓ Compare GitHub source repository ↗

Category: Other #119 of 230
Stars: ★ 220 Popular
Transport: stdio (local process) · Streamable HTTP
Runtime: Node.js · Hosted (no local runtime)
Credentials: API key / credential required
License: MIT
Last commit: 6 days ago

54FMRS · D

Telnyx MCP is Telnyx's officially maintained bridge from IDE-based AI assistants to its remote telecom API MCP server, aimed at letting agents call Telnyx services without relying on pre-training or fragile documentation retrieval; the main risks concern API key security and account-level permissions, and the source material does not list specific tool names.

Strongest · Maintenance 14/20 Weakest · Reliability 7/20

Reliability

7/20

Security and permissions

8/20

Maintenance

14/20

Documentation

13/20

Setup experience

12/20

Why each score

Reliability 7/20: The manifest only lists package metadata (npm package @telnyx/mcp, stdio transport, one required secret env var) with no enumerated tool list, no test suite, and no CI workflow evidence in the reviewed material, so declared tools cannot be checked against real behavior. The server is described as a thin proxy to a remote Telnyx-hosted MCP endpoint, meaning most actual logic executes server-side and is unverifiable from this repo. No error-handling or failure-mode documentation is shown. Per the static calibration cap, this dimension is scored well below the ceiling.
Security and permissions 8/20: Credential handling follows a reasonable pattern (TELNYX_API_KEY passed via env var, explicitly marked isSecret/isRequired, no token committed in examples). However, the server proxies full API access to a telecom account that, per the README's own Agent Toolkit examples, includes paid/irreversible actions (buy_phone_number, send_sms, account funding via MPP/x402, porting). Neither the manifest nor the README discloses any scoping, tool allowlisting, or confirmation gating for such actions when exposed through the MCP proxy — this is an undisclosed risk area rather than a confirmed default-execute-without-confirmation behavior, so it is treated as a deduction rather than a red line. No statement is made about what request data is logged or retained by Telnyx's remote infrastructure.
Maintenance 14/20: The repository is active (not archived), carries an MIT license, and names four maintainers from a dedicated 'AI-FDE team' with a CODEOWNERS file and a SECURITY.md channel for vulnerability reports — clear ownership and a defined security-response path. 30 open issues against 201 stars suggest real usage alongside an unresolved backlog. No release/versioning history, changelog, or dependency-update cadence is visible in the reviewed material, so sustained update discipline cannot be confirmed.
Documentation 13/20: The root README is layered and covers multiple install paths (Claude Code plugin, Gemini CLI extension, Cursor config, direct npx invocation) with copyable config snippets, and links out to /tools/mcp, /skills, and /guides for deeper material. However, none of that deeper documentation is included in the reviewed evidence, and the README itself does not enumerate the MCP server's actual tool list, parameters, rate limits, or the cost implications of telecom actions (buying numbers, sending messages) implied by the toolkit examples. Troubleshooting guidance specific to the MCP proxy is absent.
Setup experience 12/20: Setup is presented in few steps with concrete examples: npx invocation with an --api-key flag, or a hosted HTTP endpoint snippet for Cursor's mcp.json, and the manifest's required TELNYX_API_KEY is properly flagged as a secret. This suggests a low-friction path in mainstream clients. However, there is a minor inconsistency between the manifest (declares stdio transport with an environmentVariables-based API key) and the README's CLI-flag example plus the separate hosted-HTTP example, leaving it unclear which is authoritative for io.github.team-telnyx/telnyx-mcp. No installation is exercised or verified in this static review, and per the calibration cap, the absence of CI/test evidence prevents a higher score.

Static review · not runListed 2026-08-26

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

Developers already on the Telnyx platform who want to operate Telnyx resources from inside their IDE
Teams building voice agents, SMS automation, or other telecom-integrated AI applications

Not for

Users without a Telnyx account or API key
Teams that need a fully enumerated tool list up front to assess integration scope — the source material does not name individual tools

Required permissions

Requires a Telnyx API key (TELNYX_API_KEY), flagged as a secret in the server manifest
That key can authorize account-level telecom operations (e.g., sending messages, purchasing numbers) and should be handled carefully

Risks and side effects

A leaked API key could be used to incur real charges or misuse telecom resources (e.g., bulk SMS) on the Telnyx account
The remote MCP server (api.telnyx.com) is a hosted service; its availability and behavior depend on Telnyx's infrastructure rather than local control
The source material explicitly states the repository is a work in progress under active development, so interfaces may change

Setup

Before you start

Runtime：Node.js · Hosted (no local runtime)

TELNYX_API_KEY requiredsecret Telnyx API key for authentication; get it from your Telnyx account dashboard.

Option 1 (local stdio proxy): configure your MCP client to run npx -y @telnyx/mcp --api-key=YOUR_TELNYX_API_KEY, or set the TELNYX_API_KEY environment variable when running the npm package. Option 2 (direct remote connection): add an http-type MCP server entry pointing to https://api.telnyx.com/v2/mcp in your client's MCP config (e.g., Cursor's .cursor/mcp.json).

.cursor/mcp.json

{
  "mcpServers": {
    "telnyx": {
      "command": "npx",
      "args": [
        "-y",
        "@telnyx/mcp",
        "--api-key=YOUR_TELNYX_API_KEY"
      ]
    }
  }
}

Shown for Cursor. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

{
  "servers": {
    "telnyx": {
      "command": "npx",
      "args": [
        "-y",
        "@telnyx/mcp",
        "--api-key=YOUR_TELNYX_API_KEY"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add telnyx -- npx -y @telnyx/mcp --api-key=YOUR_TELNYX_API_KEY

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Run `npx -y @telnyx/mcp --api-key=YOUR_TELNYX_API_KEY` and connect from your client; the Telnyx tools (e.g. messaging/number management) should appear in the client's tool list.

Troubleshooting

Verify TELNYX_API_KEY is set correctly or passed via the --api-key flag
For Cursor's http connection, confirm the url field in .cursor/mcp.json is set to https://api.telnyx.com/v2/mcp
Ensure Node.js/npx is available to run the local stdio proxy package
For account or billing-related failures, check Telnyx account status and API key permission scope

Things to try

Once connected, you can ask your AI assistant things like:

Search for available phone numbers in the US and buy one
Send an SMS to +15551234567 saying hello
Check my Telnyx account balance
Set up a new messaging profile for my number

Use cases

Letting a coding assistant call Telnyx's SMS, voice, and number-management APIs directly

Managing Telnyx account resources (e.g., buying numbers, configuring messaging profiles) during development

Wiring AI-powered telecom tooling into voice agent, IoT, or WebRTC projects

Supported clients

Cursor

Claude CodePartial support

Gemini CLIPartial support

Listed from the project's documentation, not tested by this site.

Overview

Telnyx MCP is an officially maintained proxy that connects IDEs and coding assistants (Cursor, Claude Code, Gemini CLI, etc.) to Telnyx's remote MCP server at https://api.telnyx.com/v2/mcp, exposing AI-powered telecom tools. The repo ships the @telnyx/mcp npm package, which runs locally over stdio and proxies to the remote service, as well as documentation for connecting a client directly to the hosted HTTP endpoint. The source material does not enumerate specific tool names or a fixed tool count — it describes the server generically as providing 'AI-powered telecom tools' spanning Telnyx's messaging, voice, numbers, AI assistant, and WebRTC product areas. Authentication requires a Telnyx API key.

Similar servers

Hevy MCP 77 · B

Manage your Hevy workout data from AI assistants via MCP.

★ 509 · Tools 26 Compare with this →

Firecrawl MCP Server 75 · B

Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents

★ 7.6k · Tools 11 Compare with this →

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 653 · Tools 11 Compare with this →

Compartment 75 · B

Encrypted, fully offline long-term memory for AI agents

★ 579 · Tools 14 Compare with this →

Compare with other MCP servers

Source revision 4d2ace03d087 Data synced 2026-10-11 Read the FMRS scoring method