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
T
Telnyx MCP Server
Official
Official proxy connecting your IDE to Telnyx's remote MCP server
GitHub source repository ↗
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.
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.
Tools
The tool list has not been reviewed yet.
Setup
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).
claude_desktop_config.json
{
"mcpServers": {
"telnyx": {
"command": "npx",
"args": [
"-y",
"@telnyx/mcp",
"--api-key=YOUR_TELNYX_API_KEY"
]
}
}
}
Fit and risk
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
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
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
CursorFull support
Claude CodePartial support
Gemini CLIPartial support