Skip to main content
Glama

ssh_docker_deploy

Deploy Docker containers to remote servers via SSH using docker-compose, build, or run commands with working directory context.

Instructions

Deploy Docker containers with working directory context

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionIdYesSSH connection ID
workingDirectoryYesDirectory containing docker-compose.yml or Dockerfile
deploymentTypeYesType of Docker deployment
imageNameNoDocker image name (for build/run)
containerNameNoContainer name (for run)
composeFileNoDocker compose file namedocker-compose.yml
buildArgsNoBuild arguments for Docker build
envVarsNoEnvironment variables
portsNoPort mappings (e.g., ["8080:80", "3000:3000"])
volumesNoVolume mappings (e.g., ["/host/path:/container/path"])
detachedNoRun in detached mode

Implementation Reference

  • Handler function implementing the ssh_docker_deploy tool. Parses input with DockerDeploySchema, constructs Docker commands (compose up, build, or run) based on deploymentType, executes via SSH execCommand in the specified working directory, and returns command output.
    private async handleDockerDeploy(args: unknown) {
      const params = DockerDeploySchema.parse(args);
      
      const context = connectionContexts.get(params.connectionId);
      if (!context) {
        throw new McpError(
          ErrorCode.InvalidParams,
          `Connection ID '${params.connectionId}' not found`
        );
      }
    
      try {
        // Set working directory for this operation
        const workingDir = params.workingDirectory;
        
        let command = '';
        let envPrefix = '';
        
        // Build environment variables prefix
        if (params.envVars) {
          const envVarStrings = Object.entries(params.envVars).map(([key, value]) => `${key}="${value}"`);
          envPrefix = envVarStrings.join(' ') + ' ';
        }
        
        switch (params.deploymentType) {
          case 'compose':
            command = `${envPrefix}docker-compose`;
            if (params.composeFile && params.composeFile !== 'docker-compose.yml') {
              command += ` -f ${params.composeFile}`;
            }
            command += ' up';
            if (params.detached) {
              command += ' -d';
            }
            break;
            
          case 'build':
            if (!params.imageName) {
              throw new McpError(
                ErrorCode.InvalidParams,
                'imageName is required for build deployment type'
              );
            }
            command = `${envPrefix}docker build`;
            if (params.buildArgs) {
              Object.entries(params.buildArgs).forEach(([key, value]) => {
                command += ` --build-arg ${key}="${value}"`;
              });
            }
            command += ` -t ${params.imageName} .`;
            break;
            
          case 'run':
            if (!params.imageName) {
              throw new McpError(
                ErrorCode.InvalidParams,
                'imageName is required for run deployment type'
              );
            }
            command = `${envPrefix}docker run`;
            if (params.detached) {
              command += ' -d';
            }
            if (params.containerName) {
              command += ` --name ${params.containerName}`;
            }
            if (params.ports) {
              params.ports.forEach(port => {
                command += ` -p ${port}`;
              });
            }
            if (params.volumes) {
              params.volumes.forEach(volume => {
                command += ` -v ${volume}`;
              });
            }
            command += ` ${params.imageName}`;
            break;
        }
        
        const result = await context.ssh.execCommand(command, {
          cwd: workingDir,
        });
        
        return {
          content: [
            {
              type: 'text',
              text: `Docker ${params.deploymentType} deployment:\nCommand: ${command}\nExit Code: ${result.code}\n\nSTDOUT:\n${result.stdout}\n\nSTDERR:\n${result.stderr}`,
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Docker deployment failed: ${error instanceof Error ? error.message : String(error)}`
        );
      }
  • Zod schema for validating input parameters to the ssh_docker_deploy tool.
    const DockerDeploySchema = z.object({
      connectionId: z.string().describe('SSH connection ID'),
      workingDirectory: z.string().describe('Directory containing docker-compose.yml or Dockerfile'),
      deploymentType: z.enum(['compose', 'build', 'run']).describe('Type of Docker deployment'),
      imageName: z.string().optional().describe('Docker image name (for build/run)'),
      containerName: z.string().optional().describe('Container name (for run)'),
      composeFile: z.string().default('docker-compose.yml').describe('Docker compose file name'),
      buildArgs: z.record(z.string()).optional().describe('Build arguments for Docker build'),
      envVars: z.record(z.string()).optional().describe('Environment variables'),
      ports: z.array(z.string()).optional().describe('Port mappings (e.g., ["8080:80", "3000:3000"])'),
      volumes: z.array(z.string()).optional().describe('Volume mappings (e.g., ["/host/path:/container/path"])'),
      detached: z.boolean().default(true).describe('Run in detached mode')
    });
  • src/index.ts:443-462 (registration)
    Registration of the ssh_docker_deploy tool in the ListTools response, including name, description, and JSON input schema.
    {
      name: 'ssh_docker_deploy',
      description: 'Deploy Docker containers with working directory context',
      inputSchema: {
        type: 'object',
        properties: {
          connectionId: { type: 'string', description: 'SSH connection ID' },
          workingDirectory: { type: 'string', description: 'Directory containing docker-compose.yml or Dockerfile' },
          deploymentType: { type: 'string', enum: ['compose', 'build', 'run'], description: 'Type of Docker deployment' },
          imageName: { type: 'string', description: 'Docker image name (for build/run)' },
          containerName: { type: 'string', description: 'Container name (for run)' },
          composeFile: { type: 'string', default: 'docker-compose.yml', description: 'Docker compose file name' },
          buildArgs: { type: 'object', description: 'Build arguments for Docker build' },
          envVars: { type: 'object', description: 'Environment variables' },
          ports: { type: 'array', items: { type: 'string' }, description: 'Port mappings (e.g., ["8080:80", "3000:3000"])' },
          volumes: { type: 'array', items: { type: 'string' }, description: 'Volume mappings (e.g., ["/host/path:/container/path"])' },
          detached: { type: 'boolean', default: true, description: 'Run in detached mode' }
        },
        required: ['connectionId', 'workingDirectory', 'deploymentType']
      },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions 'working directory context' which hints at behavioral context, but doesn't disclose critical traits: whether this is a mutating operation (likely yes), authentication requirements (SSH connection needed), potential side effects (container creation/startup), or error conditions. The description is insufficient for a complex 11-parameter deployment tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that gets straight to the point. There's no wasted language or unnecessary elaboration. It's appropriately sized for what it communicates, though what it communicates is limited.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (11 parameters, no annotations, no output schema), the description is inadequate. It doesn't explain the deployment workflow, what happens after deployment, error handling, or the relationship between parameters. For a Docker deployment tool with SSH integration, more context about the deployment process and expected outcomes is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, providing good documentation for all 11 parameters. The description adds minimal value beyond the schema - 'working directory context' relates to the workingDirectory parameter but doesn't explain its significance or how it interacts with other parameters. With high schema coverage, the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Deploy Docker containers with working directory context' states the general action (deploy) and resource (Docker containers) but is vague about the specific deployment methods. It mentions 'working directory context' which hints at directory-based deployment but doesn't specify the three deployment types (compose, build, run) or distinguish this tool from sibling tools like ssh_docker_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an SSH connection), when to choose compose vs build vs run, or how it relates to sibling tools like ssh_docker_status. Usage is implied through parameter names but not explicitly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mahathirmuh/mcp-ssh-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server