Image workflows are runtime-gated like the rest of the platform: provider keys, build profile, and registration mode decide what the client can actually call.

Images for Web Projects Directly from MCP

SindByte can generate and refine web assets from the same local automation surface that handles files, text, and deployment steps. The image path is especially useful when you want an agent to create a full page package instead of stopping at raw copy.

1. Enable the image provider and publish the relevant routes.

2. Generate a base image with CUTools::GenerateImage.

3. Adapt it for delivery with CUTools::PictureResize.

4. Use PictureConvert or the optional PictureEdit route when you need alternate formats or a second stylistic pass.

Generated and resized with the live SindByte server for this documentation refresh. It summarizes the prompt-to-website asset flow in one picture.

Enable the Image Surface

Use the live configuration surface to turn on provider-backed routes. The published client catalog changes immediately with tool flags, credential status, and registration mode.

Minimum Configuration

Provider key: store the OpenAI-compatible image credential in the config or cloud settings surface.

Feature switch: enable OpenAIImageToolEnabled=true.

Model choice: select OpenAIImageModel such as gpt-image-1.

Publication: reload the client or registration payload so the image routes become visible.

Example Pipeline

1) GenerateImage(prompt="clean MCP capability map", target="file", target_file="assets/img/feature-map-generated.png")
2) PictureResize(source="file", source_file="assets/img/feature-map-generated.png", target="file", target_file="assets/img/feature-map-generated-web.png", width=840, height=840)
3) PictureConvert(source="file", source_file="assets/img/feature-map-generated-web.png", target="file", target_file="assets/img/feature-map-generated-web.jpg", format="jpg")
4) Integrate the generated asset into HTML/CSS and continue with normal site edits

Target Modes You Can Use

`file`

Write the asset directly into the site or build workspace when the next step is HTML/CSS integration.

`memory`

Keep generated output inside the workflow state when you want an agent to compare variants before writing anything to disk.

`clipboard`

Move assets quickly into another desktop tool or design step without saving intermediate files.

`both`

Use when you want a durable file plus a transient workflow copy at the same time.

Generated sample: Capability Map

Generated sample: Runtime Surface Map

Generated sample: Asset Pipeline

Operational note: Image generation is part of the same audited platform surface as the other tools, but it is one of the clearest examples of why the runtime-visible catalog varies. Without credentials or with a stricter registration mode, the client sees fewer routes than the full 237-entry config audit or the 239-tool host-callable runtime surface.

Created with the server itself: the new explanatory images on this page were produced with the running SindByte MCP server using CUTools::GenerateImage and CUTools::PictureResize, then placed back into the website during the same local documentation workflow.

Continue with the Full Workflow

Combine image generation with file writes, HTML edits, and deployment steps through the rest of the SindByte stack.

Workflow Guides Manual Capability Map