Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Related Servers

Alternatives to mcp-server-ipex

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to manage a Telgea business mobile operator account end to end: users, teams, plans, lines and eSIMs, live connection status, number port-ins, usage and analytics, data pools, rates and cost thresholds. Read-only tools run by default, while costly or irreversible changes such as new lines, SIM swaps, port-ins and terminations require a signed two-step prepare/commit flow, with eSIM credentials redacted everywhere except a separately gated tool and daily API request budgets enforced locally.
      32
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query and manage a web hosting billing platform through its External API — clients, tickets, invoices, domains, orders, products, and system data. It defaults to read-only with per-domain opt-in for writes, two-step confirmation for billing and destructive actions, and automatic redaction of secrets, card data, and PII.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides read-only access to Yeastar P-Series PBX System APIs, enabling querying of extensions, groups, trunks, routes, IVR menus, ring groups, queues, live call and agent status, contacts, call detail records, reports, and system metadata for AI assistants.
      26
      2
      Apache 2.0
    • F
      license
      B
      quality
      F
      maintenance
      Enables 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.
      46
      25
      -

    TDQS

    C2.5/5.0

    Scored across 75 tools

    Disambiguation3/5

    Most tools map to distinct REST paths and are separable by resource (connectors, containers, customers, invoices, reports), but there are several near-duplicate clusters: list_phone_numbers vs the deprecated list_phone_numbers_v1, and a dense family of get_report_* count/sum tools whose one-line descriptions (e.g. 'Customer count' vs 'Customer count (provider)') are easy to misselect. get_invoice_item is described as 'Get virtual service detail', which blurs it against get_service, and get_customer/get_customer_name/list_customers require reading the path to distinguish.

    Naming Consistency4/5

    Strong overall verb_noun snake_case pattern (get_*, list_*, search_*, check_*) applied uniformly across ~70 tools. Minor deviations: bare 'alive' and 'health', plus the '_v1' version suffix on the deprecated phone-number tool, break the pattern slightly.

    Tool Count2/5

    75 tools is far beyond a well-scoped set and effectively a 1:1 dump of every GET endpoint in the IPEX API, forcing the agent to sift through many narrow report and per-resource sub-lists. The surface could be consolidated (generic report tool, parameterized sub-resource listings) without losing capability.

    Completeness2/5

    The surface is entirely read-only: every tool is a GET, with no create/update/delete for orders, customers, services, or invoices, so lifecycle workflows (e.g. placing an order, modifying a service) dead-end. Coverage of reads is broad, but for a provisioning/billing API this is a significant functional gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues