Netdiag MCP vs Unifi MCP Server
A side-by-side look at the Netdiag MCP and Unifi MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Netdiag MCP for developer tools work as a local process; choose Unifi MCP Server for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Netdiag MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
dns_lookup, dnssec_check, ping_host.
Choose Unifi MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
UNIFI_API_KEY. - You want tools like
get_site_details, list_sites, compare_site_performance.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 52/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | UNIFI_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 308 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 12 | 19 |
| Full listing | View Netdiag MCP | View Unifi MCP Server |
Tools & capabilities
Netdiag MCP tools 12
dns_lookupResolve a DNS record via `dig` (A/AAAA/MX/TXT/NS/CNAME/SOA/PTR/CAA), optionally against a specific resolver and over plain DNS/DoT/DoHdnssec_checkQuery a known-validating resolver and report whether the AD bit is set (plain/DoT/DoH) — the only reliable way to confirm DNSSEC validation, since an RRSIG being present in a plain `dig` reply does not by itself prove anything validated itping_hostICMP ping (count clamped to 1-10)traceroute_pathHop-by-hop path/loss report via `mtr --report` (fixed cycles, not a live/continuous run)tcp_port_checkIs a TCP port open — a plain socket connect, not a port scanhttp_checkHEAD/GET a URL and report status, redirect chain, and latencyhttp_getGET a URL and return the body. Textual types only (`text/*`, JSON, XML, JavaScript, YAML, `+json`/`+xml`), capped at 1 MiB. Refuses loopback, link-local and cloud-metadata destinations, including via redirecttls_cert_checkFetch the certificate a host presents and report subject/issuer/validity/SANswhois_lookupWHOIS lookup for a domainasn_lookupASN + country-code lookup for an IP, or org info for an AS number, via Team Cymru's whois service — no API key or GeoIP database neededcurrent_timeCurrent date, time and weekday in an IANA timezone — the weekday is returned as data because deriving it from a date is arithmetic that fails silently. Also reports UTC and epoch, so it doubles as a clock checkhealth_checkVersion and which wrapped binaries (`dig`/`ping`/`mtr`/`whois`) are present on PATH
Unifi MCP Server tools 19
get_site_detailsGet detailed site information.list_sitesList all accessible sites.compare_site_performanceCompare performance metrics across all sites. Analyzes uptime, latency, bandwidth, and health status to identify best and worst performing sites.get_cross_site_statisticsGet aggregate statistics across multiple sites.get_hostGet host details by ID.get_internet_healthGet internet health metrics across sites.get_isp_metricsGet ISP metrics for a specific site.get_sdwan_configGet SD-WAN configuration by ID.get_sdwan_config_statusGet SD-WAN configuration deployment status.get_site_health_summaryGet health summary for all sites or a specific site.get_site_inventoryGet comprehensive inventory for a site or all sites. Provides detailed breakdown of resources including devices, clients, networks, SSIDs, VPN tunnels, and firewall rules.get_version_controlGet API version control information.- +7 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Netdiag MCP
{
"mcpServers": {
"netdiag-mcp": {
"command": "uvx",
"args": [
"netdiag-mcp"
]
}
}
}
Unifi MCP Server
{
"mcpServers": {
"unifi-mcp-server": {
"command": "uvx",
"args": [
"unifi-mcp-server"
],
"env": {
"UNIFI_API_KEY": "YOUR_UNIFI_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Netdiag MCP is categorized under Developer Tools and uses a local stdio subprocess. Unifi MCP Server belongs to Developer Tools and uses a local stdio subprocess. Pick Netdiag MCP for developer tools work and Unifi MCP Server for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Netdiag MCP has no declared pricing — check the project's own site. Unifi MCP Server is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add netdiag-mcp and unifi-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Netdiag MCP has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Unifi MCP Server has 63/100 (Good) with 0 views, 0 installs and 308 GitHub stars.