Skip to main content
Glama
landynsnipes

Enterprise MCP Kit

by landynsnipes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Enterprise MCP Kit

No user-submitted related servers found.

    Related Servers

    • TheBoringMCP_netbox

      theboringalex
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to create, read, update, and delete NetBox resources such as sites, networks, VLANs, IP addresses, devices, interfaces, cables, and VMs through generic CRUD and convenience tools, with automatic name/slug resolution and optional read-only or API-key protection.
      MIT

    • mcp-netdisco

      AngelN-Halo
      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.
      -

    • NetBox MCP Server

      mhajder
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to read and manage NetBox network infrastructure data via MCP. Supports querying all object types, search, changelogs, GraphQL, IP/prefix/VLAN allocation, cable tracing, config rendering, and write operations with safety modes.
      18
      38 PyPI
      1
      MIT
    • NetBox MCP Server by netboxlabs

      NetBox MCP Serverofficial

      netboxlabs
      A
      license
      A
      quality
      B
      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
      243
      Apache 2.0

    • s2-netbox-mcp

      J-MaFf
      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
      36 npm
      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.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

    Resources