#telephony

Read-only MCP server giving any AI assistant access to CallSphere's voice-AI (short) knowledge base, ROI calculator, industry case studies, and product facts. Works in every MCP-capable client.

MCP server for BubblyPhone — make AI phone calls, manage phone numbers, configure voice agents, and track billing from any AI assistant. Supports Claude, ChatGPT, Cursor, and any MCP-compatible client.

Real SIM-backed mobile numbers for AI agents. Provision phone numbers, receive SMS, and capture OTP codes - bypasses VoIP blocks that reject Twilio/Vonage. 5 tools: provision_number, wait_for_otp, get_messages, release_number, list_numbers.

Connect your SIM-based business calls, logs, and staff activities with AI. This remote MCP server allows AI agents to search call logs, trigger AI voice transcriptions, analyze caller sentiment, and update CRM contact details securely via OAuth 2.1.

A hosted, read-only Model Context Protocol server that gives an AI voice agent phone intelligence in one call — who is this inbound caller, and is this number one to think twice about — before it burns agent minutes. Four read-only tools: phone_lookup (validity, line type, range carrier, country, CNAM where available, STIR/SHAKEN verstat, a labeled spam signal, a first-party do-not-contact signal, and a signed receipt), caller_risk, line_type, and dnc_check. Every billable answer carries an Ed25519-signed receipt — verifiable 'checked as of T' evidence — and no raw phone number is ever stored (hashed only). Remote/hosted: nothing to install; point your agent at the URL.

Connect voice telephony to your AI agent. Make outbound calls, get transcripts, check call status — all via MCP tools. Built on Asterisk + Yandex SpeechKit. OAuth 2.1, FZ-152 compliant.

Connect AI agents to Wavix's communications platform. Make calls, send SMS, manage phone numbers, run speech analytics, and more, directly from Claude, Cursor, or any MCP-compatible client.

AgentLine is the telephony layer for AI agents. It gives your agent a real phone number making outbound calls, receiving inbound calls, and handling SMS all through a single API. No telecom infrastructure, no WebSocket wrangling, no separate STT/TTS providers to configure.