MCP Server

9.1 Overview & Requirements

The MCP server connects directly to Neo4j or PostgreSQL using the same query files as the REST API. It runs as a stdio transport process — the AI client starts it as a subprocess and communicates over stdin/stdout. No HTTP server or port is required.

Install the MCP Extras

pip install "meshoptixiq-network-discovery[mcp]"

# Or with PostgreSQL support
pip install "meshoptixiq-network-discovery[postgres,mcp]"

Environment Variables (MCP)

Test the MCP Server

GRAPH_BACKEND=neo4j \
NEO4J_URI=bolt://localhost:7687 \
NEO4J_PASSWORD=your-password \
MESHOPTIXIQ_LICENSE_KEY=mq-prod-xxxxxxxxxx \
  meshq-mcp

The server will print its initialisation options to stderr and then wait for MCP protocol messages on stdin. Use Ctrl+C to stop.

9.2 Claude Desktop Setup

Figure 9.1 — Claude Desktop using the meshq_blast_radius_device MCP tool to answer a blast radius question

Add MeshOptixIQ to your Claude Desktop configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Python Installation

{
  "mcpServers": {
    "meshoptixiq": {
      "command": "meshq-mcp",
      "env": {
        "GRAPH_BACKEND": "neo4j",
        "NEO4J_URI": "bolt://localhost:7687",
        "NEO4J_USER": "neo4j",
        "NEO4J_PASSWORD": "your-password",
        "MESHOPTIXIQ_LICENSE_KEY": "mq-prod-xxxxxxxxxx"
      }
    }
  }
}

Docker

{
  "mcpServers": {
    "meshoptixiq": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "--network", "host",
        "-e", "GRAPH_BACKEND=neo4j",
        "-e", "NEO4J_URI=bolt://localhost:7687",
        "-e", "NEO4J_PASSWORD=your-password",
        "-e", "MESHOPTIXIQ_LICENSE_KEY=mq-prod-xxxxxxxxxx",
        "meshoptixiq/meshoptixiq:latest",
        "meshq-mcp"
      ]
    }
  }
}

Restart Claude Desktop after editing the config. MeshOptixIQ should appear in the tool panel (plug icon).

9.3 Claude Code Setup

Add MeshOptixIQ as an MCP server in your Claude Code project:

# In your project directory
claude mcp add meshoptixiq meshq-mcp \
  --env GRAPH_BACKEND=neo4j \
  --env NEO4J_URI=bolt://localhost:7687 \
  --env NEO4J_PASSWORD=your-password \
  --env MESHOPTIXIQ_LICENSE_KEY=mq-prod-xxxxxxxxxx

Or add it globally (available in all projects):

claude mcp add --global meshoptixiq meshq-mcp \
  --env MESHOPTIXIQ_LICENSE_KEY=mq-prod-xxxxxxxxxx \
  --env NEO4J_PASSWORD=your-password

9.4 Available Tools, Resources & Prompts

Tools (134 total)

Resources (6 total)

Resources expose read-only network data as background context for AI reasoning.

Prompts (6 pre-defined templates)

9.4.1 Tool Count by Category

The 134 tools span 36 modules covering Topology, Endpoints, Blast Radius, Addressing, Hygiene, Inventory, Firewall, Routing, IGP/MPLS, InfiniBand, DCGM GPU, NVLink, NCCL Operations, eBPF Telemetry, Interface Metrics, SD-WAN, VXLAN/EVPN, Wireless, NAC/ITSM, Sites, Alerts, Compliance, Compliance Expand, Flows, Kubernetes, Synthetic Monitors, Vulnerabilities, Security Ops, Anomaly Detection, Capacity Planning, Tracing, Chaos Engineering, AI Query, Tenant Management, Cert Scanner, and Event Streaming.

9.4.2 MCP Resources

Six read-only resources expose key network state to AI assistants:

• network://inventory/summary — aggregate device/interface/endpoint counts
• network://topology/edges — all device-to-device connection edges
• network://health/platform — platform health (API, graph, Redis, license)
• network://firewall/devices — all devices with collected firewall rules
• network://alerts/active — currently fired (unacknowledged) alerts
• network://compliance/latest — most recent compliance scan results

9.4.3 MCP Prompts

Six structured prompts guide Claude through common network operations workflows:

Example Conversations

User: "What would be the impact if sw-core-01 went offline right now?"

Claude: [calls meshq_blast_radius_device with device="sw-core-01"]
        [calls meshq_topology_device_neighbors with device_name="sw-core-01"]
        "If sw-core-01 went offline, 47 endpoints would lose connectivity,
         distributed across VLANs 10, 20, and 100. Three distribution
         switches — dist-sw-01, dist-sw-02, and dist-sw-03 — would lose
         their uplink..."