generate_dockerfile
Creates a Dockerfile that builds a self-hosted MCP server image for a specified capability, requiring only 'docker build' to deploy.
Instructions
Generate a ready-to-build Dockerfile for the packaged MCP server.
Takes the same capability inputs as package_capability and returns the
Dockerfile text that builds the self-hosted MCP server image for it.
Returns:
The Dockerfile contents as plain text — write it to Dockerfile and
run docker build to produce the image named in package_capability's
docker_image field.
Example: generate_dockerfile( capability_id="translate.multi@v2", product_id="prod-translate", name="Lyra Translator", )
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Human-readable display name for the packaged MCP server, shown to end users in MCP clients such as Claude Desktop (e.g. 'Lyra Translator'). | |
| registry | No | Container registry namespace for the built image. Defaults to 'aifactory'. Set your own org/namespace to publish under a different account (e.g. 'ghcr.io/acme'). | aifactory |
| product_id | Yes | Owning product ID on the AIMarket hub, e.g. 'prod-translate'. Used to namespace the Docker image and the MCP manifest. | |
| description | No | One- or two-sentence summary of what the capability does. Surfaced in the MCP manifest and the Claude Desktop config. Optional but strongly recommended — it becomes the tool description in the generated server. | |
| input_schema | No | JSON Schema object describing the capability's input. For example, an object with a required string property 'text'. Omit or pass null for a schema-less capability. | |
| capability_id | Yes | Fully-qualified capability identifier to package, e.g. 'translate.multi@v2'. This is the single capability the generated MCP server will expose as a tool. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |