What is the key difference between Docker MCP and ScreenRIG?

Docker MCP belongs to the Developer Tools category with local stdio execution, while ScreenRIG belongs to the Developer Tools category with local stdio execution.

How do I install Docker MCP or ScreenRIG 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 Docker MCP and ScreenRIG free or paid?

Docker MCP operates under a Free / Open Source model (No auth required). ScreenRIG operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Docker MCP lists 4 tools with 3 views and 504 GitHub stars. ScreenRIG lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Docker MCP and ScreenRIG 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.

Side-by-Side Model Context Protocol Comparison

Docker MCP vs ScreenRIG

In-depth architectural comparison of the Docker MCP and ScreenRIG 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

Docker MCP

Developer Tools · Local stdio

Quality: 45/100 (Fair) | Auth: No auth required

ScreenRIG

Developer Tools · Local stdio

Quality: 44/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Docker MCP if you need specialized Developer Tools tools running via a local process. Choose ScreenRIG if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Docker MCP when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Create standalone containers, Deploy Docker Compose stacks, Retrieve container logs.

Explore Docker MCP Details

Choose ScreenRIG when:

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

Explore ScreenRIG Details

Feature & Specification Comparison

Specification	Docker MCP QuantGeekDev Developer Tools	S ScreenRIG Developer Tools
Summary
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Docker MCP Tools (4)

Create standalone containers

Deploy Docker Compose stacks

Retrieve container logs

List containers and statuses

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

Docker MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "quantgeekdev-docker-mcp": {
      "command": "uvx",
      "args": [
        "docker-mcp"
      ]
    }
  }
}

ScreenRIG Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Docker MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, ScreenRIG belongs to Developer Tools using local stdio subprocess. Select Docker MCP when you need capabilities focused on developer tools and ScreenRIG when you require tools for developer tools.

More alternatives to Docker MCP More alternatives to ScreenRIG Developer Tools category hub