What is the key difference between McpProxy and Sniff?

McpProxy belongs to the Browser Automation category with local stdio execution, while Sniff belongs to the Browser Automation category with local stdio execution.

How do I install McpProxy or Sniff in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are McpProxy and Sniff free or paid?

McpProxy operates under a Free / Open Source model (No auth required). Sniff operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

McpProxy lists 5 tools with 2 views and 966 GitHub stars. Sniff lists 0 tools with 0 views and 0 GitHub stars.

Can I use both McpProxy and Sniff together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install McpProxy or Sniff in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are McpProxy and Sniff free to use, or do they require API keys?

McpProxy is listed under a Free / Open Source model with No auth required . Sniff operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both McpProxy and Sniff at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both jetbrains-mcpproxy and sniff as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, McpProxy has a Quality Score of 59 /100 ( Good ) with 2 views, 0 installs, and 966 GitHub stars. Sniff holds a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

McpProxy vs Sniff

In-depth architectural comparison of the McpProxy and Sniff 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.

At a Glance & Executive Verdict

McpProxy

Browser Automation · Local stdio

Quality: 59/100 (Good) | Auth: No auth required

Sniff

Browser Automation · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose McpProxy if you need specialized Browser Automation tools running via a local process. Choose Sniff if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose McpProxy 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).
You have access to required keys: IDE_PORT, HOST, LOG_ENABLED.
Primary tools included: Proxies MCP requests to JetBrains IDEs via local webserver, Supports configuration of IDE host and port, Enables logging via environment variable.

Explore McpProxy Details

Choose Sniff 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 Sniff Details

Feature & Specification Comparison

Specification	McpProxy jetbrains Browser Automation	S Sniff Browser Automation
Summary	A model context protocol server to work with JetBrains IDEs: IntelliJ, PyCharm, WebStorm, etc. Also, works with Android Studio	QA + a11y scanner: walks your running app's real user flows and reports what's broken.
Category & Scope	Browser Automation	Browser Automation

Tools & Capabilities Breakdown

McpProxy Tools (5)

Proxies MCP requests to JetBrains IDEs via local webserver

Supports configuration of IDE host and port

Enables logging via environment variable

Compatible with VS Code and Claude Desktop MCP clients

Supports external connections with proper IDE settings

Sniff Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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).

McpProxy Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "jetbrains-mcpproxy": {
      "command": "npx",
      "args": [
        "-y",
        "executable"
      ],
      "env": {
        "IDE_PORT": "YOUR_IDE_PORT_HERE",
        "HOST": "YOUR_HOST_HERE",
        "LOG_ENABLED": "YOUR_LOG_ENABLED_HERE"
      }
    }
  }
}

Sniff Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

McpProxy is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Sniff belongs to Browser Automation using local stdio subprocess. Select McpProxy when you need capabilities focused on browser automation and Sniff when you require tools for browser automation.

More alternatives to McpProxy More alternatives to Sniff Browser Automation category hub