Skip to main content
Glama
OpenSIPS

OpenSIPS MCP Server

Official
by OpenSIPS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to OpenSIPS MCP Server

No user-submitted related servers found.

    Related Servers

    • pbx-mcp

      ictinnovations
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that lets AI assistants inspect and control Asterisk and FreeSWITCH PBX systems, enabling natural language queries about live switch status, channels, registrations, and call control.
      10
      48 npm
      17
      MIT
    • oitvoip-mcp-server by OITApps

      oitvoip-mcp-serverofficial

      OITApps
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides AI agents with seamless access to the NetSapiens VoIP platform for user management, call analytics, and system administration.
      23
      4
      -

    • mctl

      mctlhq
      A
      license
      B
      quality
      D
      maintenance
      AI-native control plane for Kubernetes and GitOps. Provides 30+ tools for service deployment, database provisioning, and log management via natural language.
      1
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 236 tools

    Disambiguation2/5

    Several tool clusters have genuinely fuzzy boundaries: sipp_load_test and sipp_run_scenario both execute SIPp scenarios, get_memory_stats vs perf_memory_report vs perf_hotspots all report the same shm/pkg memory data, cc_status already returns queue+agents+flows making cc_list_agents/cc_list_queue redundant, and rtpengine_show overlaps with rtpengine_instance_health. With 236 tools, an agent will frequently be unsure which of several near-duplicates to call.

    Naming Consistency3/5

    The dominant module_verb convention is well followed across most domains (dialplan_add_rule, cluster_drain_node, tls_check_expiry, subscriber_bulk_import). However, there are systematic deviations: a get_* family (get_process_list, get_memory_stats, get_tcp_connections, get_statistics), a gen_* family (gen_test_subscribers, gen_test_dispatcher), and prefix-less outliers like health_check, cleanup_test_data, and sl_stats break the otherwise predictable pattern.

    Tool Count1/5

    236 tools is extreme bloat — over 15x the upper bound of a well-scoped server and 4x the 'too many' threshold. Even though OpenSIPS administration is genuinely broad, this surface would be far more usable split into focused servers (config, routing, media, monitoring, subscriber management).

    Completeness4/5

    Within each subdomain the coverage is unusually deep: dialplan, dispatcher, drouting, subscriber, TLS, fraud, and config lifecycle all have full CRUD or create/get/update/delete/reload chains, plus extras like config migration planning, snapshots, and load-testing harnesses. Minor gaps exist (address has no update, domain lacks update, no direct service start/stop control) but agents can work around them.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources