Docker MCP Server

Created By
makbna year ago
Model Context Protocol MCP Server for Docker Commands. Provides Docker and Docker Swarm commands as MCP Tools.
Overview

What is MCP Mediator Docker Implementation?

MCP Mediator Docker Implementation is a module that provides a Docker-based implementation of a Message Communication Protocol (MCP) server, utilizing the mcp_mediator core framework.

How to use MCP Mediator Docker Implementation?

To use the MCP Mediator Docker Implementation, you can run the server using the provided Java command or create a native executable. The server can be configured with various command-line options to connect to a Docker daemon and manage MCP messages.

Key features of MCP Mediator Docker Implementation?

  • Pluggable server architecture leveraging Docker's API.
  • Supports various MCP tools for managing Docker containers and services.
  • Configurable server options for customization.

Use cases of MCP Mediator Docker Implementation?

  1. Managing Docker containers through MCP commands.
  2. Integrating with other services that require message communication via Docker.
  3. Automating Docker operations in a microservices architecture.

FAQ from MCP Mediator Docker Implementation?

  • What is the purpose of this project?

The project serves as a mediator for handling MCP messages in a Docker environment.

  • How can I build the server?

You can build the server by running mvn clean compile package to create a jar file or use GraalVM to create a native executable.

  • What are the supported Docker commands?

The implementation supports a variety of Docker commands such as starting/stopping containers, listing images, and managing networks.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
makbn
Star
0
Language
Java
License
GPL-3.0 license

Recommend Servers

View All
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