Netdiag MCP vs Azure DevOps (ADO)
A side-by-side look at the Netdiag MCP and Azure DevOps (ADO) MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Azure DevOps (ADO)Developer Tools · Local subprocess (stdio)The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.55GoodAuth: not declaredVerdict: choose Netdiag MCP for developer tools work as a local process; choose Azure DevOps (ADO) 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.
AChoose Azure DevOps (ADO) when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Azure DevOps (ADO) | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 52/100 · Good | 55/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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2,063 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 12 | Not listed |
| Full listing | View Netdiag MCP | View Azure DevOps (ADO) |
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
Azure DevOps (ADO) tools
No tool names declared yet. Check the project README from 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"
]
}
}
}
Azure DevOps (ADO)
{
"mcpServers": {
"azure-devops-ado": {
"command": "npx",
"args": [
"-y",
"@azure-devops/mcp"
]
}
}
}
Frequently asked questions
Netdiag MCP is categorized under Developer Tools and uses a local stdio subprocess. Azure DevOps (ADO) belongs to Developer Tools and uses a local stdio subprocess. Pick Netdiag MCP for developer tools work and Azure DevOps (ADO) 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. Azure DevOps (ADO) 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 azure-devops-ado 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. Azure DevOps (ADO) has 55/100 (Good) with 6 views, 0 installs and 2,063 GitHub stars.