Skip to main content
Glama
labaccessnow

netops-field-notes

by labaccessnow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to netops-field-notes

No user-submitted related servers found.

    Related Servers

    • netauto MCP Server

      ters-golemi
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only, multi-vendor network device interaction, configuration auditing against vendor-guide rules, and safe diffing of proposed changes for AI agents to inspect and analyze network infrastructure without any commit or write capability.
      Apache 2.0

    • NetPulseX

      MeAkash77
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI-assisted management of multi-vendor network devices (Cisco, Juniper, Nokia, Arista, Linux) through natural language, supporting health checks, configuration changes, routing analysis, and automation workflows.
      MIT

    • Meraki MCP

      merakimiles
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides dynamic access to 400+ Meraki Dashboard API endpoints with intelligent discovery, plus advanced compliance auditing (PCI DSS, HIPAA, SOC2, ISO 27001, NIST), backup/restore operations, and network security analysis. Enables natural language queries to manage Meraki networks without pre-defined tools.
      4
      -

    • netmiko-mcp

      escrimaglia
      A
      license
      A
      quality
      B
      maintenance
      Provides read-only SSH access to network devices (routers, switches, firewalls) with command allow/deny policies, nt-templates output parsing, and an audit trail, enabling an AI agent to query device state securely.
      10
      MIT

    • network-mcp

      JohnGilligan2
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to managed network devices over SSH or Telnet via MCP, allowing users to probe devices, retrieve redacted running or startup configs, gather facts and interfaces, back up multiple devices, and compare configs for drift or unsaved changes.
      -
    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

    A4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes—config parsing, certificate checks, compliance, diffs, diagnostics, and preflight risk—so an agent can usually select correctly. However, explain_config_diff and explain_firewall_change can both apply to OPNsense config changes, and check_tls_endpoint/find_certs_in_config share the same certificate-findings logic, creating a couple of genuine boundary cases.

    Naming Consistency4/5

    The vast majority of tool names follow a predictable verb_noun snake_case pattern: check_, sanitize_, explain_, find_, extract_, infer_, diagnose_, lookup_, and preflight_. The only real outlier is latest_field_note, which is an adjective-noun phrase rather than a verb-led action, but the overall naming convention is consistent and readable.

    Tool Count5/5

    Twelve tools is well within the ideal range for a network-operations analysis server, and each tool earns its place by covering a distinct operational task: facts, compliance, sanitization, diffs, certificates, dot1x, topology, firewall changes, and preflight assessment. The count feels neither thin nor bloated.

    Completeness4/5

    The tool surface covers the main config-analysis workflow—extract facts, check compliance, explain diffs, sanitize before sharing, and preflight risk—along with certificate and dot1x troubleshooting. Minor gaps exist, such as no direct single-config plain-English explainer and no search or archive access for older field notes, but agents can generally work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources