Skip to main content
Glama
greglg45

phpIPAM MCP Server

by greglg45
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to phpIPAM MCP Server

No user-submitted related servers found.

    Related Servers

    • netbox-mcp

      msemino
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that exposes NetBox IPAM data over HTTP, allowing engineers to query subnets, IPs, and VLANs using natural language through AI assistants.
      MIT

    • pve-mcp

      tiancode
      A
      license
      A
      quality
      C
      maintenance
      MCP server for managing Proxmox VE resources, VM/CT lifecycle, snapshots, backups, and clones via natural language.
      23
      MIT

    • network-mcp

      zapplebee
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing a home network via a UniFi Dream Machine, enabling device lookup, tagging, and blocking/unblocking of clients through natural language.
      -

    • Proxmox MCP Server

      raymatos
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for interacting with the Proxmox Virtual Environment API, enabling management of VMs, containers, storage, and cluster resources through natural language.
      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

    A3.5/5.0

    Scored across 16 tools

    Disambiguation3/5

    Most tools have clear, distinct purposes, but search_addresses and search_hostname overlap significantly—both search for addresses by hostname, with search_addresses also accepting IPs. This could cause agent misselection.

    Naming Consistency4/5

    Tool names follow a verb_noun pattern consistently (list_*, search_*, create_*, update_*, delete_*, reserve_*). Minor deviation: list_* for most listing operations but get_* for get_section_subnets and get_subnet_details.

    Tool Count4/5

    16 tools is slightly above the typical 3-15 range, but the server covers a broad IPAM domain (sections, subnets, IPs, VLANs, VRFs, locations, nameservers). The count is reasonable and not bloated.

    Completeness4/5

    The core subnet and IP address lifecycle is well covered: create, update, delete, and search for both. Minor gaps exist: no create/update/delete for sections, VLANs, VRFs, locations, or nameservers, but these appear to be read-only references.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources