mcp-server-telgea
Related Servers
Alternatives to mcp-server-telgea
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables AI agents to look up and manage a company's phone lines, usage, invoices, employees, cost centers, and assets, including actions such as blocking lines, changing plans, and porting numbers. Billable actions return a quote and require confirmation before being charged.MIT- AlicenseCqualityBmaintenanceEnables assistants to query and manage IPEX B2B data—customers, services, VoIP/mobile numbers, calls, invoices, PBX, connectors, and reports—through the IPEX REST API, with read-only tools by default and opt-in tools for credits, SMS, and customer updates.75MIT

Telnyx MCP Serverofficial
FlicenseBqualityFmaintenanceEnables interaction with Telnyx's telephony, messaging, and AI assistant APIs to manage phone numbers, send messages, make calls, and create AI assistants. Includes webhook support for real-time event handling and comprehensive tools for voice, SMS, cloud storage, and embeddings.4625-- AlicenseAqualityBmaintenanceEnables AI agents to manage real US phone numbers on an account—listing numbers, reading and waiting for texts, sending messages, checking wallet balance, and buying numbers—while also searching and purchasing travel eSIMs and retail US plans, retrieving activation QR codes, and topping up lines.161MIT

@dialgem/mcpofficial
AlicenseNot gradedqualityCmaintenanceLets AI assistants manage voice agents, calls, and phone numbers, exposing read and write tools plus spend tools gated behind explicit opt-in.Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with the TelecomsXChange wholesale telecom API for voice termination, SMS, DID management, eSIM, and account operations through 55 tools and 7 guided workflows using natural language.3MIT
TDQS
Scored across 32 tools
Most tools target a distinct resource+action, and descriptions explicitly route between near-neighbours (e.g. list_usage vs get_usage_analytics, list_lines vs get_line). The main soft spots are find_user_plan vs get_user_plan vs list_user_plans, and get_user_cost_threshold vs list_cost_thresholds, where boundaries require reading the descriptions to resolve.
Every tool uses a uniform telgea_ verb_noun snake_case pattern (get_, list_, create_, update_, set_, remove_, find_, validate_, prepare_, commit_). Verb choices are semantically consistent across resources, so an agent can predict names.
32 tools is heavy and sits above the comfortable range, though the domain genuinely spans users, teams, lines, plans, SIMs, usage, port-ins, thresholds, pools and meta-discovery. Some consolidation is possible (e.g. find/get user plan, the several threshold readers), but each tool maps to a real operation rather than filler.
Coverage is broad and lifecycle-aware: writes are funnelled through the prepare/commit two-step, and reads cover users, teams, lines, plans, SIM credentials, usage, port-ins, thresholds, pools and rates. Minor gaps remain — no team deletion, no data-pool creation/update, no direct user deletion outside prepare_change — but these are workable.