Skip to main content
Glama
InfraMCP

phpipam-mcp-server

by InfraMCP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to phpipam-mcp-server

No user-submitted related servers found.

    Related Servers

    • NetBox MCP Server - Read &

      alexkiwi1
      A
      license
      A
      quality
      F
      maintenance
      Enables comprehensive interaction with NetBox infrastructure management through both read and write operations. Supports full CRUD operations for devices, IP addresses, sites, racks, and other NetBox objects through natural language commands.
      9
      17
      Apache 2.0

    • @ipgeolocationapi/mcp

      thebigasif
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query IP intelligence tools such as geolocation, VPN/security checks, ASN, timezone, astronomy, user-agent parsing, abuse contacts, and bulk lookups via natural language.
      5 npm
      MIT

    • Netdisco MCP

      omichelbraga
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with the Netdisco network management platform through its complete REST API, supporting device inspection, port queries, VLAN searches, and job management.
      MIT
    • NetMap MCP Server by netmap-app

      NetMap MCP Serverofficial

      netmap-app
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI assistant such as Claude to read and edit the self-hosted network inventory: search and manage entries, check live TCP reachability, map hosts, link and derive relationships, inspect topology, compare configured read-only sources like Docker, OPNsense, AdGuard and Traefik against what is declared, surface conflicts and new devices, and review the audit log.
      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.6/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools are clearly distinct, targeting different resources and actions. The main overlap is between search_addresses and search_hostname, but their descriptions differentiate them (IP/hostname vs hostname only). Some potential confusion between search_subnets and get_section_subnets, but the former uses a query while the latter is section-based.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., list_sections, create_subnet, delete_ip_address). The verbs (list, get, search, create, update, delete, reserve) are used predictably, making the set highly intuitive.

    Tool Count4/5

    With 16 tools, the server is slightly above the typical well-scoped range of 3-15, but still manageable. Each tool serves a clear purpose in IP address management, and the count is not excessive or insufficient.

    Completeness4/5

    The tool set covers CRUD for subnets and IP addresses, plus listing for sections, nameservers, VLANs, VRFs, and locations. Minor gaps include no update/create/delete for VLANs, VRFs, or locations, and no explicit get-by-ID for IP addresses, but these are likely outside the primary scope and search tools compensate.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources