Skip to main content
Glama
landynsnipes

Enterprise MCP Kit

by landynsnipes

Related Servers

Alternatives to Enterprise MCP Kit

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to perform read-only queries against a Netdisco network management system via its REST API, supporting device searches and other GET requests while handling authentication automatically.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for NetBox that enables LLMs to query NetBox objects (devices, IPAM, etc.) and change logs through natural language, with field filtering for token optimization.
      4
      234
      Apache 2.0
    • A
      license
      B
      quality
      A
      maintenance
      Enables MCP-compatible clients to query and manage LenelS2 S2 NetBox physical access-control systems via the NBAPI, with read-only tools by default and opt-in write/destructive operations.
      51
      489 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query an organization's device posture, compliance, policies, and software/CVE status through a remote, read-only, OAuth-secured MCP endpoint.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Provides MCP tools for governed multi-vendor network device operations, including configuration management (backup, diff, merge, replace, rollback) and read-only queries (facts, interfaces, BGP, LLDP, ARP) via NAPALM, with optional NetBox source-of-truth integration.
      33
      MIT

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct read perspective—device context, site overview, site-to-site connectivity, rack context, and power path—so an agent can usually choose the right one. There is mild thematic overlap in site/rack/power summaries, but the bounded scopes keep the boundaries clear.

    Naming Consistency4/5

    All tool names consistently begin with get_, making the read-only convention obvious and predictable. However, the suffixes vary between context, overview, and path, so the naming is not perfectly uniform.

    Tool Count5/5

    Five tools is a focused and appropriate size for a read-only infrastructure visibility server. Each tool covers a meaningful query area without unnecessary redundancy.

    Completeness4/5

    The set covers the core infrastructure visibility concerns: site, device, rack, power, and site-to-site connectivity evidence. It lacks broader device-detail or circuit-list tools, but the bounded summaries avoid major dead ends for the apparent read-only scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues