claude-foundry-image

Claude Code plugin that gives every project and every conversation an image generator backed by your own Azure AI Foundry deployment (MAI image API, e.g. MAI-Image-2.5-Pro).

• MCP server (server/server.mjs) — Node ≥ 18, zero dependencies. Tools: generate_image, edit_image, check_config.

• Skill generate-image — teaches Claude when to reach for the tools, how to expand a one-liner into a usable prompt, valid dimensions, where to write files.

• Skill setup — one-time configuration walkthrough.

Images are written to disk; only the file path enters the conversation. No base64 in context.

Install

claude plugin marketplace add jpaarhuis/claude-foundry-image

claude plugin install foundry-image@jpaarhuis

Or in an interactive session: /plugin → Marketplaces → add jpaarhuis/claude-foundry-image → install foundry-image.

Related MCP server: gpt-image-mcp

Configure (once)

The server reads its settings from environment variables. Put them in ~/.claude/settings.json under env — one file, all platforms, only Claude Code sees it:

{
  "env": {
    "MAI_IMAGE_ENDPOINT": "https://<resource>.services.ai.azure.com/mai/v1/images/generations",
    "MAI_IMAGE_DEPLOYMENT": "MAI-Image-2.5-Pro",
    "MAI_IMAGE_API_KEY": "<key>",
    "MAI_IMAGE_OUTPUT_DIR": "C:/Users/<you>/Pictures/ai"
  }
}

Or set them as OS user environment variables (setx on Windows, export in your shell profile on macOS/Linux). Restart Claude Code either way.

Then, in any session: "run check_config" or /foundry-image:setup for a guided pass.

Use

Just ask: "maak een hero image voor de README, donker, isometrisch, geen tekst". Claude expands the prompt, picks dimensions, writes the PNG (into the repo when it belongs there) and returns the path.

Tool parameters, for reference:

Dimension rules from the MAI API: each side ≥ 768 px and width × height ≤ 1 048 576 px. So 1024x1024, 1024x768, 1280x800 work; 1024x1536 and 1920x1080 do not.

Why env vars and not a config file or setup dialog?

Claude Code plugins have no per-plugin secret storage or setup UI. The convention — same one the official GitHub plugin uses for its PAT — is ${VAR} expansion in the plugin's .mcp.json, with the user setting the variables once. settings.json → env is the least-friction place for that: it travels with your Claude Code profile, applies to every project, and survives plugin updates.

If you want the key out of plaintext files, load it into the environment from a secret store at login (Key Vault, 1Password CLI, Windows Credential Manager) — the server does not care where the variable comes from.

Develop

npm test

Runs an offline smoke test: MCP handshake, tool listing, dimension guards, missing-config errors, and checks that check_config never leaks a key.

License

MIT