Woodpecker CI vs Dockerfile Audit

In-depth architectural comparison of the Woodpecker CI and Dockerfile Audit 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 Woodpecker CI when:

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

Explore Woodpecker CI Details

Choose Dockerfile Audit when:

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

Explore Dockerfile Audit Details

Feature & Specification Comparison

Specification	Woodpecker CI Security	Dockerfile Audit Security
Summary	Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons	Hadolint-grade Dockerfile audit — 19 checks: secrets, privileges, supply chain, hygiene.
Category & Scope	Security	Security
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": {
    "woodpecker-ci": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/woodpecker-ci-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "dockerfile-audit": {
      "command": "uvx",
      "args": [
        "without"
      ]
    }
  }
}

Related MCP Server Comparisons