# Docker Agent Deploy

Use this skill when exposing a Docker Agent as a server (MCP, HTTP API, A2A, ACP, or...

- Repository: https://github.com/docker/skills (609 stars)
- Category: Testing
- License: Apache-2.0
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add docker/skills --skill docker-agent-deploy -g -a claude-code -y`
Codex: `npx skills add docker/skills --skill docker-agent-deploy -g -a codex -y`
Cursor: `npx skills add docker/skills --skill docker-agent-deploy -g -a cursor -y`
Gemini CLI: `npx skills add docker/skills --skill docker-agent-deploy -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add docker/skills`

## Description

Use this skill when exposing a Docker Agent as a server (MCP, HTTP API, A2A, ACP, or OpenAI-compatible chat), distributing an agent via an OCI registry with `docker agent share`, or measuring agent quality with `docker agent eval`. Even if the user just says they want to "turn my agent into an MCP server", "let Claude Desktop use my agent", "publish my agent to Docker Hub", "push my agent like an image", or "test my agent in CI", this skill applies. Covers `serve mcp/api/a2a/acp/chat` listen addresses and auth flags, `share push/pull`, eval session JSON format, scoring metrics, and the `--baseline` regression gate.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Docker Agent: Serving, Sharing, and Evaluating

## Overview
This skill owns the integration surface of Docker Agent: making an agent
reachable by other software (`docker agent serve`), distributing it through
an OCI registry the way container images are distributed (`docker agent
share`), and proving it still behaves after a change (`docker agent eval`).
It assumes the agent config already exists, see `docker-agent-config` for
authoring it, and `docker-agent-run` for interactive/local invocation.

## When to use this skill
Activate this skill when:
- The user wants an agent reachable over MCP, an OpenAI-compatible chat endpoint, a plain HTTP API, or A2A/ACP.
- The user wants to publish an agent to Docker Hub (or any OCI registry) or pull one someone else published.
- The user wants automated evaluations (regression tests) for an agent, or wants to gate CI on eval results.

## Do not use this skill when
Do not use this skill when:
- The task is authoring the agent.yaml itself (models, toolsets, sub_agents), use `docker-agent-config`.
- The task is running the agent interactively on a developer's machine, choosing `--safety`/`--sandbox`, or aliases, use `docker-agent-run`.

## Core guidance

### Serving an agent
- Five server modes, each with its own default loopback listen address, never expose any of them beyond loopback without authentication:

  | Mode | Default listen | Auth flag | Has `--safety`? |
  | --- | --- | --- | --- |
  | `serve mcp` | `127.0.0.1:8081` | `--auth-token` (only with `--http`) | Yes (only with `--http`) |
  | `serve api` | `127.0.0.1:8080` | `--auth-token` | No |
  | `serve chat` | `127.0.0.1:8083` | `--api-key` / `--api-key-env` | Yes |
  | `serve a2a` | `127.0.0.1:8082` | `--auth-token` | Yes |
  | `serve acp` | (stdio only) | n/a | No |

The rest: https://github.com/docker/skills/blob/HEAD/skills/docker-agent-deploy/SKILL.md