pulsemcp verified Safe content atomic mcp-remote

Docker Container Execution

This MCP server provides Docker container execution capabilities with intelligent process management and file operations, built by kenforthewin using TypeScript with a Debian-based container pre-configured with Node.js and Playwright. The implementation offers command execution with smart timeout handling based on output activity rather than fixed intervals, background process tracking with unique IDs for long-running tasks, interactive process input capabilities, and comprehensive file operations including reading, writing, editing, directory listing, and content searching. Features include automatic process backgrounding after inactivity periods, persistent container state with mounted file storage, safety mechanisms requiring file reads before edits, and support for both immediate and background command execution patterns, making it valuable for developers who need programmatic access to containerized development environments, automated testing workflows, or AI-assisted development tasks that require isolated execution contexts.

Cognium trust score

94%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: cloud-infra
Source: PulseMCP
Repository: github.com/kenforthewin/docker-mcp-server
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve Docker Container Execution from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"