MCP SSH Docker Server

Created By
awehera year ago
MCP server to play with IA and containerlab instances
Overview

What is MCP SSH Docker Server?

MCP SSH Docker Server is a Message Control Protocol (MCP) server that allows users to execute SSH and Docker commands on remote systems and containers through a standardized interface.

How to use MCP SSH Docker Server?

To use the MCP SSH Docker Server, clone the repository, set up your SSH configuration, and start the server. You can then execute commands on remote systems or Docker containers using the provided tools.

Key features of MCP SSH Docker Server?

  • SSH command execution on remote systems
  • Docker container command execution
  • Real-time command output streaming
  • Progress reporting for long-running commands
  • Structured JSON output support
  • Command cancellation support
  • Comprehensive error handling

Use cases of MCP SSH Docker Server?

  1. Executing administrative commands on remote servers.
  2. Managing Docker containers remotely.
  3. Automating deployment and management tasks in a containerized environment.

FAQ from MCP SSH Docker Server?

  • What are the prerequisites for using MCP SSH Docker Server?

You need Python 3.7+, SSH access to the target system, and Docker installed on the target system for Docker commands.

  • Is there a license for MCP SSH Docker Server?

Yes, it is licensed under GPLv3.

  • How can I contribute to the project?

You can fork the repository, create a feature branch, commit your changes, and submit a Pull Request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aweher
Star
0
Language
Python
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