OpenWrt Network Diagnostics MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIHOMO_SECRET | Yes | The Mihomo secret, provided only through the MCP subprocess environment variable. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| snapshot_networkA | Collect a bounded router-side network snapshot and retain it in memory for later comparison. |
| inspect_config_stateA | Compare whitelisted Nikki generated startup fields with Mihomo runtime General state and provider summaries. |
| trace_dnsA | Compare OpenWrt and Mihomo DNS observations, generated DNS settings, Fake-IP addresses, and listeners. |
| observe_clientB | Observe bounded Mihomo connection/log activity and conntrack state associated with one client address. |
| inspect_flowB | Correlate live Mihomo, routing, aggregated nftables, and conntrack evidence for a client and destination. |
| capture_flowC | Run an explicitly requested, non-persistent packet capture using a generated restricted filter. |
| inspect_subscriptionsA | Return safe Nikki cache metadata and Mihomo provider summaries without URLs or credentials. |
| read_logsA | Read filtered and redacted OpenWrt, Nikki, or newly observed Mihomo logs. |
| compare_snapshotsA | Return mechanically computed field changes between snapshots from the current MCP process. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target clearly distinct diagnostic aspects (snapshot, config, DNS, client, flow, capture, subscriptions, logs). The only potential overlap is between observe_client and inspect_flow, but their descriptions clarify different scopes (client-level vs. flow-level).
All tool names follow a consistent verb_noun pattern in snake_case (e.g., snapshot_network, inspect_config_state, capture_flow). Even with repeated verbs like 'inspect', the nouns clearly differentiate the tools.
9 tools is well-scoped for a specialized network diagnostics server, covering both data collection and analysis without unnecessary bloat or missing core functionality.
The tool set covers major diagnostic workflows: snapshots, config comparison, DNS tracing, client observation, flow inspection, packet capture, subscription metadata, and logs. Minor gaps exist such as an explicit connectivity test or snapshot management, but core capabilities are solid.