Skip to main content
Glama

run_container

Run Docker containers with configurable options like ports, volumes, environment variables, and commands to deploy applications or services.

Instructions

Run a Docker container

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYesDocker image to run
nameNoName for the container
detachNoRun container in background
portsNoPort mappings (e.g. ["8080:80"])
volumesNoVolume mappings (e.g. ["/host/path:/container/path"])
envNoEnvironment variables (e.g. ["KEY=value"])
commandNoCommand to run in the container

Implementation Reference

  • The main handler function that constructs and executes the 'docker run' command using child_process.execAsync based on the provided arguments, returning the stdout as text content.
    private async runContainer(args: RunContainerArgs) {
      if (!args.image) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Image parameter is required'
        );
      }
    
      let command = 'docker run';
      
      if (args.detach) {
        command += ' -d';
      }
      
      if (args.name) {
        command += ` --name ${args.name}`;
      }
      
      if (args.ports && Array.isArray(args.ports)) {
        args.ports.forEach((port: string) => {
          command += ` -p ${port}`;
        });
      }
      
      if (args.volumes && Array.isArray(args.volumes)) {
        args.volumes.forEach((volume: string) => {
          command += ` -v ${volume}`;
        });
      }
      
      if (args.env && Array.isArray(args.env)) {
        args.env.forEach((env: string) => {
          command += ` -e ${env}`;
        });
      }
      
      command += ` ${args.image}`;
      
      if (args.command) {
        command += ` ${args.command}`;
      }
      
      const { stdout } = await execAsync(command);
      
      return {
        content: [
          {
            type: 'text',
            text: stdout.trim(),
          },
        ],
      };
    }
  • TypeScript interface defining the structure of input arguments for the run_container tool.
    interface RunContainerArgs {
      image: string;
      name?: string;
      detach?: boolean;
      ports?: string[];
      volumes?: string[];
      env?: string[];
      command?: string;
    }
  • JSON schema for input validation in the tool's registration.
    inputSchema: {
      type: 'object',
      properties: {
        image: {
          type: 'string',
          description: 'Docker image to run',
        },
        name: {
          type: 'string',
          description: 'Name for the container',
        },
        detach: {
          type: 'boolean',
          description: 'Run container in background',
        },
        ports: {
          type: 'array',
          items: {
            type: 'string',
          },
          description: 'Port mappings (e.g. ["8080:80"])',
        },
        volumes: {
          type: 'array',
          items: {
            type: 'string',
          },
          description: 'Volume mappings (e.g. ["/host/path:/container/path"])',
        },
        env: {
          type: 'array',
          items: {
            type: 'string',
          },
          description: 'Environment variables (e.g. ["KEY=value"])',
        },
        command: {
          type: 'string',
          description: 'Command to run in the container',
        },
      },
      required: ['image'],
    },
  • src/index.ts:90-136 (registration)
    Registration of the 'run_container' tool in the ListTools response, including name, description, and schema.
    {
      name: 'run_container',
      description: 'Run a Docker container',
      inputSchema: {
        type: 'object',
        properties: {
          image: {
            type: 'string',
            description: 'Docker image to run',
          },
          name: {
            type: 'string',
            description: 'Name for the container',
          },
          detach: {
            type: 'boolean',
            description: 'Run container in background',
          },
          ports: {
            type: 'array',
            items: {
              type: 'string',
            },
            description: 'Port mappings (e.g. ["8080:80"])',
          },
          volumes: {
            type: 'array',
            items: {
              type: 'string',
            },
            description: 'Volume mappings (e.g. ["/host/path:/container/path"])',
          },
          env: {
            type: 'array',
            items: {
              type: 'string',
            },
            description: 'Environment variables (e.g. ["KEY=value"])',
          },
          command: {
            type: 'string',
            description: 'Command to run in the container',
          },
        },
        required: ['image'],
      },
    },
  • Dispatcher in CallToolRequest handler that routes to the runContainer method.
    case 'run_container':
      return await this.runContainer(request.params.arguments as unknown as RunContainerArgs);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Run a Docker container' implies a creation/execution operation but doesn't specify if it's idempotent, what happens on failure, whether it requires specific permissions, or how output is handled. This is a significant gap for a tool that likely involves system-level changes.

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 with zero waste—it directly states the tool's purpose without unnecessary elaboration. It's appropriately front-loaded and concise for a straightforward action.

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 complexity of running a Docker container (a mutation with potential side effects), no annotations, and no output schema, the description is incomplete. It fails to address behavioral aspects like error handling, resource implications, or return values, leaving critical gaps for agent decision-making.

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?

The input schema has 100% description coverage, clearly documenting all 7 parameters. The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline of 3 for adequate but not enhanced parameter information.

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

Purpose4/5

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

The description 'Run a Docker container' clearly states the action (run) and resource (Docker container), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'stop_container' or 'remove_container' beyond the basic verb, missing explicit distinction in scope or purpose.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_containers' or 'stop_container'. It lacks context about prerequisites (e.g., needing an image pulled first) or typical use cases, leaving the agent to infer usage from the tool name alone.

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/suvarchal/docker-mcp'

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