Skip to main content
Glama
alsamasu

phpIPAM MCP Server

by alsamasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to phpIPAM MCP Server

No user-submitted related servers found.

    Related Servers

    • NetBox MCP Server

      jseifeddine
      A
      license
      B
      quality
      D
      maintenance
      Enables read-only interaction with NetBox network documentation and infrastructure data through LLMs. Allows querying devices, sites, IP addresses, and viewing change history via natural language.
      3
      Apache 2.0

    • AI Network Troubleshooting MCP

      Praneeth7997
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to safely troubleshoot networks through read-only tools for device inventory, interface status, VLAN paths, BGP neighbors, route lookups, and interface error detection. Integrates with Microsoft Copilot Studio and Teams for natural-language-driven network diagnostics.
      -

    • 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
    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 13 tools

    Disambiguation4/5

    Tools are mostly distinct, with clear resource-action patterns for sections, subnets, and addresses. Minor ambiguity exists between 'search' and 'addresses.get', but descriptions clarify their different use cases.

    Naming Consistency4/5

    Most tools follow a consistent 'phpipam.<resource>.<action>' pattern. Exceptions include 'phpipam.health' and 'phpipam.search', which omit the resource segment, but the overall style is uniform.

    Tool Count5/5

    13 tools is well-scoped for an IPAM server, covering health checks, sections, subnets, and addresses without excessive redundancy. Each tool serves a clear purpose within the domain.

    Completeness3/5

    Address lifecycle is well covered with allocate, release, and upsert, but sections and subnets lack update and delete operations. The ensure tools provide creation, but no way to modify or remove these entities, leaving notable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources