Skip to main content
mcpSource-backedReview first Safety Privacy
Telnyx MCP Server logo

Telnyx MCP Server

The official Telnyx MCP server (@telnyx/mcp) that lets AI assistants use Telnyx's communications APIs through function calling — messaging (SMS/MMS), voice and call control, phone-number management, SIP connections, verification, and wireless. The npx package proxies to Telnyx's hosted MCP server over HTTPS and authenticates with a Telnyx API key.

by team-telnyx · submitted by davion-knight·added 2026-07-08·
HarnessClaude CodeCodexCursorClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/team-telnyx/ai/tree/main/tools/mcp, https://github.com/team-telnyx/ai, https://telnyx.com/
Brand
Telnyx MCP Server
Brand domain
telnyx.com
Brand asset source
brandfetch
Safety notes
The Telnyx API key grants access to your account's communications APIs, so tools can take real actions — sending SMS/MMS, placing or controlling calls, and managing phone numbers, SIP connections, and messaging profiles., Messaging and voice operations reach real recipients and incur usage charges, so use a limited or test key and review actions before running against a production account., Access is bounded by the API key's permissions, not by tool naming; scope the key to the minimum needed and treat it as a secret., The package proxies your requests to Telnyx's hosted MCP server over HTTPS and sends the API key to authenticate against the Telnyx API., Prefer a dedicated or restricted key for autonomous agents rather than a full-access production key.
Privacy notes
The server calls Telnyx APIs with your key; account, phone-number, messaging, and call data it returns is passed to the LLM/MCP client., Communications data can include phone numbers, message content, and call metadata, which are personal data, so avoid exposing production data to the model unnecessarily., Requests and the API key are sent to Telnyx's hosted MCP server; review Telnyx's data-handling terms before using real customer data., The API key lives in your MCP client config (argument or `TELNYX_API_KEY` env var) — keep that config out of version control and restrict access to it.
Author
team-telnyx
Submitted by
davion-knight
Claim status
unclaimed
Last verified
2026-07-08

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Safety notes

  • The Telnyx API key grants access to your account's communications APIs, so tools can take real actions — sending SMS/MMS, placing or controlling calls, and managing phone numbers, SIP connections, and messaging profiles.
  • Messaging and voice operations reach real recipients and incur usage charges, so use a limited or test key and review actions before running against a production account.
  • Access is bounded by the API key's permissions, not by tool naming; scope the key to the minimum needed and treat it as a secret.
  • The package proxies your requests to Telnyx's hosted MCP server over HTTPS and sends the API key to authenticate against the Telnyx API.
  • Prefer a dedicated or restricted key for autonomous agents rather than a full-access production key.

Privacy notes

  • The server calls Telnyx APIs with your key; account, phone-number, messaging, and call data it returns is passed to the LLM/MCP client.
  • Communications data can include phone numbers, message content, and call metadata, which are personal data, so avoid exposing production data to the model unnecessarily.
  • Requests and the API key are sent to Telnyx's hosted MCP server; review Telnyx's data-handling terms before using real customer data.
  • The API key lives in your MCP client config (argument or `TELNYX_API_KEY` env var) — keep that config out of version control and restrict access to it.

Prerequisites

  • Node.js and npm (the server runs via `npx -y @telnyx/mcp`)
  • A Telnyx account and an API key (create one in the Telnyx portal under API Keys)
  • Outbound HTTPS access, since the package proxies to Telnyx's hosted MCP server at api.telnyx.com
  • An MCP-compatible client (Claude Desktop, Cursor, VS Code, etc.)

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "telnyx": {
      "command": "npx",
      "args": ["-y", "@telnyx/mcp", "--api-key=YOUR_TELNYX_API_KEY"]
    }
  }
}

About this resource

Content

The Telnyx MCP Server is the official Model Context Protocol server from Telnyx. It lets LLMs and agentic clients use Telnyx's communications APIs through function calling — spanning messaging (SMS/MMS), voice and call control, phone-number management, SIP connections, verification, and wireless — so an agent can operate real communications workflows conversationally.

It ships as the npm package @telnyx/mcp (v0.1.0, MIT), runs over stdio via npx, and authenticates with a Telnyx API key (--api-key or the TELNYX_API_KEY environment variable). Telnyx also hosts a remote MCP server at https://api.telnyx.com/v2/mcp, and this package proxies MCP requests to that hosted server over HTTPS. Setup details live in the package README.

Source Review

The following real repository and package sources were fetched and reviewed for this entry:

  • tools/mcp README — the npx -y @telnyx/mcp install command, the --api-key / TELNYX_API_KEY auth options, the hosted-server endpoint (https://api.telnyx.com/v2/mcp), and the note that the package proxies requests to the hosted MCP server over HTTP(S).
  • npm: @telnyx/mcp — package name and version (0.1.0), MIT license, and the telnyx-mcp bin entry.
  • Telnyx developer docs — the underlying Telnyx APIs (messaging, voice, numbers, SIP, verification, wireless) the hosted MCP server exposes.
  • LICENSE — MIT License.

Repository facts confirmed at review time: official team-telnyx organization, repository team-telnyx/ai (MCP package under tools/mcp), not archived, actively maintained, and released as @telnyx/mcp v0.1.0 on npm.

Features

  • Messaging — send and manage SMS/MMS through Telnyx's messaging APIs.
  • Voice & call control — place and control calls via Telnyx's voice APIs.
  • Phone numbers — search, order, and manage phone numbers on your account.
  • SIP connections — work with SIP connections and related voice configuration.
  • Verification — use Telnyx Verify for one-time passcodes and 2FA flows.
  • Wireless — manage Telnyx wireless (IoT SIM) resources.
  • Hosted-server proxy — the local package forwards MCP requests to Telnyx's hosted MCP server (https://api.telnyx.com/v2/mcp) over HTTPS, so tools stay current with the hosted service.
  • API-key auth — authenticates with a single Telnyx API key via --api-key or TELNYX_API_KEY.
  • One-command install — runs via npx -y @telnyx/mcp with no clone or build step.

Installation

Run the published package with npx, providing your Telnyx API key:

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

Add it to an MCP client (e.g. Claude Desktop's claude_desktop_config.json) using the API key argument:

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

Or provide the key via an environment variable:

{
  "mcpServers": {
    "telnyx": {
      "command": "npx",
      "args": ["-y", "@telnyx/mcp"],
      "env": {
        "TELNYX_API_KEY": "YOUR_TELNYX_API_KEY"
      }
    }
  }
}

The package proxies MCP requests to Telnyx's hosted server at https://api.telnyx.com/v2/mcp, so outbound HTTPS access is required.

Use Cases

  • Conversational messaging — send and manage SMS/MMS from an agentic workflow.
  • Voice automation — initiate and control calls through Telnyx's voice APIs.
  • Number provisioning — search for and order phone numbers on demand.
  • Verification flows — trigger one-time passcodes for 2FA use cases.
  • Wireless management — inspect and manage IoT SIM resources.

Safety and Privacy

  • Real communications, real cost. The API key can send SMS/MMS, place or control calls, and manage numbers/SIP — actions that reach real recipients and incur charges.
  • Key is the boundary. Scope the Telnyx API key to the minimum needed and prefer a restricted or test key for autonomous agents; treat it as a secret.
  • Proxies to Telnyx. Requests and the API key are sent to Telnyx's hosted MCP server over HTTPS; review Telnyx's data-handling terms before using real customer data.
  • Data flows to the model. Account, number, messaging, and call data (including phone numbers and message content) is returned to the LLM/MCP client.
  • Credential hygiene. The key lives in your MCP client config (argument or TELNYX_API_KEY) — keep it out of version control and restrict access.

Duplicate Check

No existing entry in the directory matches this server. A search of all directory entries for "telnyx" across slugs, titles, repository URLs, and install commands returned no results, and there is no prior entry pointing at github.com/team-telnyx/ai or the npm package @telnyx/mcp. This is therefore a net-new, non-duplicate entry.

Source citations

Add this badge to your README

Show that Telnyx MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/telnyx-mcp-server.svg)](https://heyclau.de/entry/mcp/telnyx-mcp-server)

How it compares

Telnyx MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

The official Telnyx MCP server (@telnyx/mcp) that lets AI assistants use Telnyx's communications APIs through function calling — messaging (SMS/MMS), voice and call control, phone-number management, SIP connections, verification, and wireless. The npx package proxies to Telnyx's hosted MCP server over HTTPS and authenticates with a Telnyx API key.

Open dossier

The official Mux MCP server (@mux/mcp) that gives AI agents access to the Mux API for video and analytics. It uses a "Code Mode" scheme — exposing a documentation-search tool and a code tool that runs agent-written TypeScript against the Mux SDK in an isolated sandbox — to work with Mux Video (assets, live streams, playback IDs, uploads) and Mux Data (viewer metrics and monitoring).

Open dossier

The official Paddle MCP server (@paddle/paddle-mcp) that lets AI assistants work with Paddle Billing — managing the product catalog, prices, and discounts, customers and businesses, subscriptions, transactions and adjustments, and financial reports — over the Paddle API, with sandbox or production environments and a read-only / non-destructive / all tool-permission filter.

Open dossier

The official Xero MCP server (@xeroapi/xero-mcp-server) that lets AI assistants work with a Xero accounting organisation — managing contacts, chart of accounts, invoices, credit notes, payments, bank transactions, manual journals, quotes, items, and payroll, and reading financial reports — using Xero OAuth2 custom connections or a bearer token.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitterdavion-knightdavion-knightdavion-knightdavion-knight
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
BrandTelnyx MCP Server logoTelnyx MCP ServerMux MCP Server logoMux MCP ServerPaddle MCP Server logoPaddle MCP ServerXero MCP Server logoXero MCP Server
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
Authorteam-telnyxmuxincPaddleHQXeroAPI
Added2026-07-082026-07-082026-07-082026-07-08
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesThe Telnyx API key grants access to your account's communications APIs, so tools can take real actions — sending SMS/MMS, placing or controlling calls, and managing phone numbers, SIP connections, and messaging profiles. Messaging and voice operations reach real recipients and incur usage charges, so use a limited or test key and review actions before running against a production account. Access is bounded by the API key's permissions, not by tool naming; scope the key to the minimum needed and treat it as a secret. The package proxies your requests to Telnyx's hosted MCP server over HTTPS and sends the API key to authenticate against the Telnyx API. Prefer a dedicated or restricted key for autonomous agents rather than a full-access production key.This server uses a Code Mode scheme — the agent writes TypeScript against the Mux SDK and the server runs it in an isolated sandbox that has no web or filesystem access, then returns what the code prints or returns. The sandboxed code runs with your Mux access token, so it can create, modify, and delete real Mux resources (assets, live streams, playback IDs, uploads) within that token's permissions. Access is bounded by the Mux token's permissions, not by tool naming — scope the token to least privilege and prefer a non-production environment when an agent acts autonomously. Optional Mux signing and private keys enable signed playback URLs and JWTs; treat `MUX_SIGNING_KEY` and `MUX_PRIVATE_KEY` as secrets. Launching the client with the remote HTTP transport opens a network listener, so secure and authenticate it before exposing it beyond localhost.The server acts on your real Paddle Billing account via its API key; with write permissions it can create and adjust products, prices, discounts, customers, subscriptions, and transactions. Tool permissions are controlled by `--tools` / `PADDLE_MCP_TOOLS`; `non-destructive` (the default) allows reads and safe writes, `read-only` allows reads only, and `all` enables every operation — choose the narrowest mode for the task. Adjustment and transaction tools can move real money (refunds, credits, charges), so prefer `read-only` or `non-destructive` unless a destructive action is explicitly intended. Use `--environment=sandbox` with a sandbox API key while developing; point at `production` only when you intend to act on live billing data. Treat the Paddle API key as a secret with broad account access, and scope what the agent can do through the environment and tools settings rather than the tool names alone.Write-capable tools create and update real accounting records — invoices, contacts, credit notes, payments, bank transactions, manual journals, quotes, items, tracking categories, and payroll timesheets in the connected organisation. Creating payments, invoices, credit notes, and manual journals affects real financial data and ledgers, so start with a Demo Company and review actions before connecting a production organisation. Access is bounded by the custom connection's OAuth2 scopes (optionally `XERO_SCOPES`); grant only the scopes the workflow needs rather than the full set. Payroll timesheet tools can create, update, approve, revert, and delete timesheets (NZ/UK regions), which affect real payroll data. Xero credentials (`XERO_CLIENT_ID`/`XERO_CLIENT_SECRET` or `XERO_CLIENT_BEARER_TOKEN`) grant API access to the organisation and must be treated as secrets.
Privacy notesThe server calls Telnyx APIs with your key; account, phone-number, messaging, and call data it returns is passed to the LLM/MCP client. Communications data can include phone numbers, message content, and call metadata, which are personal data, so avoid exposing production data to the model unnecessarily. Requests and the API key are sent to Telnyx's hosted MCP server; review Telnyx's data-handling terms before using real customer data. The API key lives in your MCP client config (argument or `TELNYX_API_KEY` env var) — keep that config out of version control and restrict access to it.The server calls the Mux API with your credentials; asset metadata, live-stream details, and Mux Data results it returns are passed to the LLM/MCP client. Mux Data covers viewer and playback analytics (video views, errors, quality-of-experience metrics), which can include viewer and session information. Credentials (`MUX_TOKEN_ID`, `MUX_TOKEN_SECRET`, and any signing/webhook secrets) are provided via environment variables in your MCP client config — keep that config out of version control and restrict access to it. Video assets and analytics can reference real customer-facing content and usage, so avoid exposing a production account's data to the model unnecessarily.The server sends requests to the Paddle Billing API using your API key; customer, business, subscription, transaction, and report data it returns is passed to the LLM/MCP client. Billing data can include personal and financial information (names, emails, addresses, purchase history, payment metadata), so avoid exposing production data to the model unnecessarily. Reports and customer/subscription tools can surface aggregate revenue and account details; treat that output as sensitive business data. The API key is provided via a command-line argument or the `PADDLE_API_KEY` environment variable in your MCP client config — keep that config out of version control and restrict access to it.The server calls the Xero API with your credentials; contact, invoice, payment, bank transaction, payroll, and report data it returns is passed to the LLM/MCP client. Accounting and payroll data includes personal and financial information (customer and employee details, amounts, bank and tax data), so avoid exposing a production organisation's data to the model unnecessarily. Financial reports (profit and loss, balance sheet, aged payables/receivables, trial balance) reveal aggregate business financials; treat that output as sensitive. Credentials live in your MCP client config's `env` block — keep that config out of version control and restrict access to it.
Prerequisites
  • Node.js and npm (the server runs via `npx -y @telnyx/mcp`)
  • A Telnyx account and an API key (create one in the Telnyx portal under API Keys)
  • Outbound HTTPS access, since the package proxies to Telnyx's hosted MCP server at api.telnyx.com
  • An MCP-compatible client (Claude Desktop, Cursor, VS Code, etc.)
  • Node.js and npm (the server runs via `npx -y @mux/mcp@latest`)
  • A Mux account and an access token (token ID and secret) from the Mux dashboard
  • Optional Mux signing/private keys or webhook secret if you use signed playback or webhook features
  • An MCP-compatible client (Claude Desktop, Cursor, VS Code, Windsurf, etc.)
  • Node.js and npm (the server runs via `npx -y @paddle/paddle-mcp`)
  • A Paddle Billing account (this server does not support Paddle Classic)
  • A Paddle API key created under Paddle > Developer tools > Authentication (use a sandbox key to start)
  • A choice of environment (`sandbox` or `production`) and tool-permission mode (`read-only`, `non-destructive`, or `all`)
  • Node.js 18 or newer and npm or pnpm (the server runs via `npx -y @xeroapi/xero-mcp-server@latest`)
  • A Xero account and organisation (a Demo Company is recommended to start; free trial available)
  • A Xero developer account with API credentials — a custom connection (client ID/secret) or a bearer token
  • The OAuth2 scopes your workflow needs (optionally set via `XERO_SCOPES`); Payroll queries require an NZ or UK region
Install
npx -y @telnyx/mcp --api-key=YOUR_TELNYX_API_KEY
npx -y @mux/mcp@latest
npx -y @paddle/paddle-mcp --api-key=YOUR_API_KEY --environment=sandbox
npx -y @xeroapi/xero-mcp-server@latest
Config
{
  "mcpServers": {
    "telnyx": {
      "command": "npx",
      "args": ["-y", "@telnyx/mcp"],
      "env": {
        "TELNYX_API_KEY": "YOUR_TELNYX_API_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "mux": {
      "command": "npx",
      "args": ["-y", "@mux/mcp"],
      "env": {
        "MUX_TOKEN_ID": "your_token_id",
        "MUX_TOKEN_SECRET": "your_token_secret"
      }
    }
  }
}
{
  "mcpServers": {
    "paddle": {
      "command": "npx",
      "args": ["-y", "@paddle/paddle-mcp"],
      "env": {
        "PADDLE_API_KEY": "YOUR_API_KEY",
        "PADDLE_ENVIRONMENT": "sandbox",
        "PADDLE_MCP_TOOLS": "non-destructive"
      }
    }
  }
}
{
  "mcpServers": {
    "xero": {
      "command": "npx",
      "args": ["-y", "@xeroapi/xero-mcp-server@latest"],
      "env": {
        "XERO_CLIENT_BEARER_TOKEN": "your_bearer_token"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.