AmplifierSkills and tools for thoughtful work

Tool

Imagen Provider

Generate the image without losing the requirements.

For agents and developers adding image generation. Imagen Provider exposes one library, CLI and MCP interface, qualifies the configured provider against requested features and returns image paths and metadata through the same integration.

Use Imagen ProviderWatch the 70-second filmWalk through an example
What you getFictional illustration
Request
  task: fictional packaging mockup
  required feature: reference-image support
  output: caller-selected image path

Selection
  capable configured provider → submit explicit request
  no capable configured provider → setup/capability error

Result after generation: image bytes or path plus provider metadata

Fictional request and routing outline. No image was generated and no provider was invoked for this example.

Keep the brief intact

A required feature, such as a reference image, must remain a requirement when the provider is selected.

Reuse one integration

Call the stable native interface from an agent host or from Python while provider adapters handle the differences.

Get an actionable setup failure

When no configured provider can satisfy the request, stop with a clear capability or configuration error.

The film

A requirement is not a preference.

In 70 seconds, Otto the octopus switchboard operator drops a must to get a request through: the line that takes reference sketches is dark, so he plugs in anyway. Imagen Provider never drops a must. If no configured provider can meet it, the call stops and says what to set up; a preference can fall back, with a note saying why. One interface serves agents, terminals and code, and you get the file and which provider made it. Captions are on the player; a transcript is below.

Download the film 15-second cut Captions
Read the transcript

Meet Otto. Otto puts your image requests through to a provider.

This one must use the fox from your approved sketch.

The line that takes sketches is dark. So Otto drops the must, and plugs in anyway.

Imagen Provider never drops a must, whatever line is lit.

If no lit line can meet it, the call stops and says what to set up.

A preference can bend, with a note saying why.

One interface for agents, terminals and code. You get the file, and which provider made it.

Its tests made no paid calls. Real images cost money, and judging the fox stays your job.

On screen: A requirement is not a preference.

Imagen Provider. Generate the image without losing the requirements.

The tea-tin label and its fox sketch are a fictional example. Provider names on screen are the tool’s real settings and messages. The film shows how the tool behaves; it does not report results.

See the work take shape.

Fictional request and routing outline. No image was generated and no provider was invoked for this example.

Install and inspect

Install the native package in a virtual environment and inspect imagen --help or the MCP tool schema.

Fictional example

Fictional provider requirement

The brief Inspect Imagen Provider’s installed help and MCP schema. Prepare a fictional packaging-image request that requires a reference image and an explicit output path. Explain which configured provider can meet it or what setup is missing. Do not make a paid generation call during this inspection.

Before

A missing provider silently drops the reference requirement.

After applying the method

The selector either picks the available capable provider or stops with a setup error.

Provider availability must not erase a requested feature.

A clear job.
A useful stopping point.

Generate or edit an image through an explicitly configured provider.

Use it when

  • An agent needs an MCP image tool with explicit provider requirements.
  • An application needs generation or editing behind a stable Python interface.
  • A missing feature must fail clearly instead of being dropped.

Choose another route when

  • A free offline image generator.
  • A video provider; the older video stub is not a functioning capability.

Select

A request needs a provider.

A qualified provider recommendation or a precise capability failure.

Generate

The input and provider access are available.

Provider-produced image bytes, paths and metadata.

Integrate

An agent host needs the interface.

Installed MCP/CLI entry points and verified namespace compatibility.

Read the canonical method

Use the native tool and its documented command interface.

Limits and prerequisites
  • Provider invocation can cost money and requires an approved environment credential. Selector/mock tests do not generate images.
  • The parked video-mcp stub is retained separately as reference; it is not advertised as a functioning video provider.
  • Server defaults to environment-only configuration; IMAGEN_MCP_CONFIG_PROFILE=local explicitly enables the retained dotenv setup profile.

Your first useful run.

Install in a virtual environment, inspect the tool schema and configure only the provider your request needs.

This is a native tool or library. Install its package in an isolated environment, then use the documented command or protocol.

Source on GitHub

Start from the public source

git clone https://github.com/michaeljabbour/amplifier-tool-imagen-provider.git
cd amplifier-tool-imagen-provider
python3 -m venv .venv
.venv/bin/python -m pip install .
.venv/bin/imagen --help

Use the native package and command interface described in the installation guide. This capability does not require a portable skill.

  • Native distribution: imagen; command: imagen; MCP entry point: python -m imagen_mcp.
  • Generation needs an approved OpenAI or Gemini credential and may incur provider charges.
  • The default config reads environment variables only. IMAGEN_MCP_CONFIG_PROFILE=local explicitly opts into the retained dotenv profile.
  • The shown virtual-environment commands use macOS/Linux paths; on Windows, use the corresponding .venv\Scripts executables.

Try this with your agent

Inspect Imagen Provider’s installed help and MCP schema. Prepare a fictional packaging-image request that requires a reference image and an explicit output path. Explain which configured provider can meet it or what setup is missing. Do not make a paid generation call during this inspection.

Use after installing the documented native package. Read its help, supply an explicit task and inspect the result.

Keep the guide nearby

Read the guide · License · Changes · Release metadata · CONSOLIDATION · PROVIDER_SELECTION · RELEASE_EVIDENCE_0.4.0

Know what you can rely on.

Native provider/configuration tests and a clean-wheel MCP initialize/list-tools check passed with keys empty. Those checks establish integration behavior; generated image quality needs an actual reviewed output.

Read the checks and their scope
  • Native functional baseline — passed

    324 native tests and 3 source-specific provider/configuration checks passed; no provider call.

  • Source-specific acceptance — passed

    324 native tests and 3 source-specific provider/configuration checks passed; no provider call.

  • Live execution acceptance — not-run

    No paid model call, real invitation, permission mutation, browser recording or film render was performed.

  • Clean wheel installation — passed

    Fresh-wheel distribution metadata, canonical/legacy namespace identity and real MCP stdio initialize/list-tools smoke passed outside the checkout with provider keys empty. No provider operation invoked.

Source and conformance checks are separate from demonstrated benefit. Comparative effectiveness and outside-user outcomes are not established by this site.

Fictional examples explain the capability. Tests check the stated behavior. Outside-user outcomes need their own evidence.