AIR SDK vs Netwright

In-depth architectural comparison of the AIR SDK and Netwright MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose AIR SDK when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore AIR SDK Details

N

Choose Netwright when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Netwright Details

Feature & Specification Comparison

Specification	AIR SDK Browser Automation	N Netwright Browser Automation
Summary	Collective intelligence for browser automation agents. Site capabilities, selectors, and extraction.	Playwright-style automation of .NET desktop apps (WPF, WinForms, WinUI) for AI agents.
Category & Scope	Browser Automation	Browser Automation
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "air-sdk": {
      "command": "npx",
      "args": [
        "-y",
        "@arcede/air-sdk"
      ]
    }
  }
}

{
  "mcpServers": {
    "netwright": {
      "command": "npx",
      "args": [
        "-y",
        "netwright"
      ]
    }
  }
}

Related MCP Server Comparisons