Skip to main content

​
Telnyx AI Connector

The Telnyx AI Connector is a remote MCP server for AI providers and assistants. Any AI assistant that supports remote MCP servers can use it.
  • Without signing in, the assistant can search the public Telnyx API reference and help you write code.
  • After you sign in with your Telnyx account, it can build, test and publish Voice AI assistants, place and end AI calls, route numbers, send messages, set up conversation insights and add content to knowledge bases. It can also read your conversations, numbers, apps, calls, recordings and balance.
Calls, messages and assistant chat use your Telnyx account and are billed at your normal rates.

​
Which Telnyx MCP endpoint to use

Telnyx exposes more than one MCP endpoint, so pick the one that matches what you need:
  • https://api.telnyx.com/v2/ai/mcp is this connector: anonymous API reference search, plus focused account tools over OAuth.
  • https://api.telnyx.com/v2/mcp is the Telnyx Remote MCP server. It executes Telnyx API actions and authenticates with an API key.
  • https://developers.telnyx.com/mcp is the documentation search server for these docs.

​
Add the connector

Add it as a custom or remote MCP connector in your AI assistant’s settings, using this server URL:
  • Transport: Streamable HTTP.
  • Authentication: OAuth. Leave any client ID and secret fields empty; Telnyx registers the client automatically.
  • Sign-in: the documentation tools work right away. When you first ask for account data, your assistant asks you to sign in with Telnyx, and then retries your request.
  • Scopes: sign-in asks for voice.read, voice.write, ai.read, ai.write, numbers.read, numbers.write, billing.read, messaging.read and messaging.write. If you connected before these were added, reconnect to grant them.
For assistants configured from a file or command line, add a remote MCP server named telnyx with the same URL, then run that tool’s login or authenticate command when you want to use account tools.

​
What you can ask

Searching the API reference needs no sign-in. Everything else does.
  • “Which Telnyx endpoint sends an SMS, and what does it take?”
  • “List the voices and models I can use for an assistant.”
  • “Create a dental receptionist assistant, chat with it once, then publish it.”
  • “Roll my reception assistant back to its previous version.”
  • “Route my number +1 555 010 0000 to that assistant.”
  • “Call +1 555 010 0001 with my reception assistant, then hang up after a minute.”
  • “Show my latest conversations and the summary of the most recent call.”
  • “Send a test SMS from my number to my own phone and check whether it was delivered.”
  • “How much credit do I have left?”

​
Tools

There are 48 tools. There is no general-purpose “call any endpoint” tool, and documenting an endpoint never makes it executable here. Each account tool calls one fixed Telnyx endpoint with only the inputs it names. Tools that change your account are labelled as writes, and deletes, hang-ups and routing changes are labelled destructive, so your assistant can ask before running them.

​
API reference (no sign-in)

  • list_api_endpoints: search the public Telnyx API reference, which covers 1,336 documented operations.
  • get_api_endpoint_schema: return the full schema for one endpoint, and the tool that can run it here, if any.

​
Voice AI assistants

  • list_assistants, get_assistant: your assistants and one assistant’s configuration.
  • list_assistant_versions, get_assistant_version: saved versions of an assistant.
  • create_assistant, update_assistant, clone_assistant, delete_assistant: build and change assistants. update_assistant saves a new version and makes it live unless you ask for a draft.
  • promote_assistant_version: publish a saved version, or roll back to an earlier one.
  • list_voices, list_models: the voices and models available to your account.
  • create_chat_conversation, chat_with_assistant: try an assistant by sending it a message. Chat can incur charges and can run the tools configured on that assistant.

​
Assistant tests

  • list_assistant_tests, list_assistant_test_runs: tests and their results.
  • create_assistant_test, delete_assistant_test: define and remove tests. Running tests is not available through the connector.

​
Conversations and insights

  • list_conversations, get_conversation: conversations and their details. The list omits callers’ numbers; the detail view shows them for one conversation.
  • get_conversation_timeline: who spoke and when, and which tools were called, without message text.
  • get_conversation_insights: the generated summary and insights for one conversation.
  • list_insight_templates, create_insight_template, update_insight_template, assign_insight_template: the questions and summaries generated after each conversation, and which assistants use them.

​
Calls

  • start_ai_call: place an outbound call answered by an assistant.
  • get_call_status, list_call_events, hangup_call: check a call, read its event timeline and end it.
  • search_recordings: recording details such as duration, channels and timestamps.

​
Numbers and apps

  • list_phone_numbers: your numbers with status, type, country, tags and routing.
  • assign_phone_number: route a number’s incoming calls to an app, such as an assistant’s TeXML app. This replaces the current routing.
  • list_call_control_apps, list_texml_apps: your voice applications.

​
Messaging

  • send_message: send one SMS or MMS from a US long-code or verified US toll-free number on your account, after you confirm the recipient, content and charge.
  • get_message: delivery status for a message you sent, for up to 10 days.
  • list_messaging_profiles, get_messaging_number, assign_messaging_profile: messaging profiles and which profile a number uses.

​
Assistant resources and knowledge

  • list_agent_tools, list_mcp_servers, list_integrations, list_knowledge_bases: the building blocks your assistants can use.
  • add_url_to_knowledge_base: add a public https page to a knowledge base. The storage bucket must already exist.
  • embed_knowledge_base: index documents already uploaded to a Telnyx Storage bucket.

​
Account

  • get_account_balance: balance, pending charges, credit limit and available credit.

​
Authentication and privacy

  • Documentation is anonymous. Searching the API reference and reading schemas use no account and touch no account data.
  • Account access is per-user and short-lived. Signing in authorizes the connector for your account only. Each request uses a Telnyx credential that expires within minutes and is never stored, and the connector keeps no long-lived end-user credential.
  • Writes are one request each. A write tool sends a single request and is never retried. If a write times out or fails upstream, the assistant is told to check the current state rather than repeat it.
  • Results are allowlisted. Each tool returns only named fields; anything else is dropped.
  • Withheld from every result: conversation message text and full transcripts (only generated summaries and insights are returned), stored message text, recording audio, recording and media links, tool arguments, webhook and callback URLs, credential and API key references, port-out PINs, and payment and billing details. Values that look like secrets are masked.
  • Data handling. The connector calls Telnyx’s own first-party API. No conversation data is collected by the connector. Logs contain only a request id, a route template, and a status class, with no request bodies, headers, credentials, or account identifiers.

​
Support