DockerManager

Created By
zaycruza year ago
Overview

what is DockerManager?

DockerManager is a powerful Model Context Protocol (MCP) server that executes code in isolated Docker containers and returns the results to language models like Claude.

how to use DockerManager?

To use DockerManager, clone the repository, set up a virtual environment, install the required packages, and run the MCP Inspector to explore its functionality.

key features of DockerManager?

  • Isolated Code Execution: Run code in Docker containers separated from your main system.
  • Multi-language Support: Execute code in any language with a Docker image.
  • Complex Script Support: Run both simple commands and complete multi-line scripts.
  • Package Management: Install dependencies using pip, npm, apt-get, or apk.
  • Container Management: Create, list, and clean up Docker containers easily.
  • Robust Error Handling: Graceful timeout management and fallback mechanisms.
  • Colorful Output: Clear, color-coded console feedback.

use cases of DockerManager?

  1. Running isolated code for testing and development.
  2. Executing multi-language scripts in a controlled environment.
  3. Managing dependencies for various programming languages in Docker containers.

FAQ from DockerManager?

  • Can DockerManager execute code in any programming language?

Yes! DockerManager supports any language that can be run in a Docker container.

  • Is DockerManager free to use?

Yes! DockerManager is open-source and free to use.

  • What are the system requirements for DockerManager?

You need Python 3.9+, Docker installed and running, and the fastmcp library.

Server Config

{
  "mcpServers": {
    "DockerManager": {
      "command": "python3",
      "args": [
        "{REPOSITORY_PATH}/src/docker_mcp.py"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zaycruz
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago