Skip to main content
Glama

Tintloom

Image generation and editing for Claude Code, with your own provider keys.

Claude has no image model of its own. This plugin gives it one. Ask for an image and Claude makes it with OpenAI, Google Gemini, fal.ai or BytePlus ModelArk, using a key you supply. You pay the provider per image and nothing else. The saved file lands in your project.

It is free and MIT licensed. It is independent: not made or endorsed by Anthropic.

Install

claude plugin marketplace add shakee93/tintloom-images
claude plugin install tintloom@tintloom

Add a key: run /plugin, open tintloom, choose Configure, and paste a key for OpenAI, Gemini, fal or BytePlus ModelArk. Start a new session, then ask: "generate a hero image for this page".

The plugin needs Node 18 or newer and has no dependencies.

Setting it up with an AI agent: see llms-install.md.

Related MCP server: image-generator-mcp

Examples

  • Left: a photo of a cat taking a selfie.

  • Middle: the same photo after painting over the face and asking for "Give it sunglasses". Only the painted area changes.

  • Right: a sticker with a transparent background.

What you can ask for

  • A new image: "a hero image for this landing page, 16:9, left side clear for the headline".

  • An edit of a file: "make fox.png night, keep the fox and the framing".

  • One part only: "make the kite red" with a mask or a region; everything outside is kept.

  • A transparent background, a new shape, variations, or several different images at once.

In Claude Code you get the saved file and its path. In apps that show MCP Apps cards, the image also appears in a card with an editor.

Providers

Provider

Default model

Good for

openai

gpt-image-2

Text in images, layouts, precise and masked edits. For transparency use gpt-image-1.5 or a GPT Image 2.5 or 2.6 model; plain gpt-image-2 has none.

gemini

gemini-nano-banana-2.1

Consistent subjects across edits, blending references.

fal

seedream

Widest model choice; any fal model id works.

modelark

seedream

ByteDance's own Seedream (5.5); edits with up to 10 input images.

cloud

auto

Any OpenAI-compatible endpoint of your own.

Masked and region edits need openai. Splitting one image into a base plus transparent layers (layers: true, or --layers on the CLI) needs modelark; every image it returns is billed by ModelArk (usually about 5), and at most 10 are kept. Adding a provider is one file: see CONTRIBUTING.md.

How keys are handled

Keys are looked up in this order:

  1. The plugin's settings (/plugin > tintloom > Configure). The fields are marked sensitive, so Claude Code stores them in the system keychain.

  2. Environment variables: OPENAI_API_KEY, GEMINI_API_KEY, FAL_KEY, ARK_API_KEY.

  3. tintloom keys set <provider>, saved to ~/.config/tintloom/config.json, readable only by you.

A key is never typed into a chat, printed, or written inside the plugin folder. Error text from provider calls is redacted so keys do not appear in it. The plugin sends your key only to the provider you chose.

Without Claude

The engine is also a plain command:

node plugins/tintloom/skills/image/scripts/tintloom.mjs generate -p "A red fox in snow, golden hour" -a 16:9 -o fox.png
node plugins/tintloom/skills/image/scripts/tintloom.mjs edit -i fox.png -p "Make it night. Keep the fox and framing." -o fox-night.png

Other ways to run it

Claude Desktop, one machine, your keys: add to claude_desktop_config.json

{
  "mcpServers": {
    "tintloom": {
      "command": "node",
      "args": ["/absolute/path/to/tintloom/plugins/tintloom/server/tintloom-mcp.mjs"],
      "env": { "OPENAI_API_KEY": "sk-..." }
    }
  }
}

A server with one set of keys: docker build -t tintloom . and run it with OPENAI_API_KEY, TINTLOOM_SERVER_TOKEN (a long random string) and TINTLOOM_PUBLIC_URL. The connector URL is https://your-host/mcp/<token>.

No keys? The hosted version

If you would rather not create provider accounts or handle keys, tintloom.com runs the same engine as a paid connector for Claude on the web, desktop and phone, with a few free credits to start. If you are comfortable with API keys, this plugin is the better deal.

How it is built

.claude-plugin/marketplace.json     lets Claude Code install the plugin from this repository
plugins/tintloom/
  .claude-plugin/plugin.json        manifest: bundled server and key settings
  skills/image/SKILL.md             teaches Claude when and how to make and edit images
  skills/image/scripts/             command-line engine, providers/*.mjs (one file per provider), lib/
  server/core.mjs                   MCP protocol and tools
  server/tintloom-mcp.mjs           local server: stdio and HTTP
  server/ui/image-card.html         the image card and editor (MCP Apps)
test/                               end-to-end tests against a local provider stub; no keys needed

Masked edits are strict. Providers redraw the whole picture, so the server puts back every pixel outside the selected area. This needs the image as a PNG, which is what the server saves.

To see what an app sends the plugin, create ~/.config/tintloom/debug.log. The server appends each request to it (never keys or image data). Delete the file to stop.

Development and tests

npm test

Runs node --test test/*.test.mjs against a local provider stub. No keys or network needed.

npm run preview

Opens the image card in a stand-in chat at http://localhost:8790 with a fake provider, so you can work on the card without a key.

Other scripts: npm run serve (local server over HTTP), npm run validate (needs the claude CLI).

Security

  • Provider keys are never logged. HTTP errors redact them before they reach you or Claude.

  • The plugin stores keys in the system keychain (plugin settings) or in a file only you can read. It does not write keys into the plugin folder.

  • The debug log is off unless you create the file, and it never contains keys or image data.

  • Report a vulnerability privately with "Report a vulnerability" on this repository's Security tab, not in a public issue.

Licence

MIT. See LICENSE.

Available Tools

9 tools
generate_imageGenerate imageA

Create an image from a text prompt, or edit or combine existing images when images is given. The result says whether the user can already see the image; follow it. Write a specific prompt: subject, setting, composition, style, lighting, and any exact text in quotes. For edits, say what changes and what must stay the same. Make one image unless the user asks for more: every image costs them money. When the user asks for several different images at once, make ONE call with prompts (one prompt per image), never several calls: they then appear together as one gallery. When the user asks to split or separate an image into layers, or to get its elements as separate transparent PNGs, call this with layers: true and that one image.

Inputs: out, mask, size, count, +13 more.

get_generated_imageLoad a generated imageC

Used by the image card to load an image by id. Not useful to call directly.

Inputs: id (required), edge, offset.

get_layer_setLoad a layer setA

Used by the image card to reopen a split-into-layers result after the chat is reloaded. Not useful to call directly.

Inputs: id (required).

get_progressImages ready so farC

Used by the image card to show images as they finish. Not useful to call directly.

Inputs: key (required).

get_upload_urlUpload an image fileA

Answers how to give this server an image file: it runs on the user's machine and reads files directly, so pass the file's path in images: [{ path }] to generate_image. No upload is needed.

Inputs: no named parameters.

list_image_providersList image providersA

List the image providers and models that can be used, what each can do, and which have a key set.

Inputs: no named parameters.

save_layer_arrangementKeep how layers were arrangedA

Used by the image card to keep what the user moved and hid in a layer set, so it is there after a reload (and on the dashboard). Not useful to call directly.

Inputs: id (required), moves, hidden.

save_maskSave a selection maskA

Used by the image card to store the area the user painted. Not useful to call directly.

Inputs: data (required).

save_selectionRemember what is open in the image cardB

Used by the image card to say which image the user has open and what they painted on it. Not useful to call directly.

Inputs: image (required), mask, erase, regions.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation3/5

    The main agent-facing tools (generate_image, list_image_providers, get_upload_url) are reasonably distinct, but six tools are explicitly internal image-card helpers that agents should not call directly. Some boundaries are still fuzzy, such as save_mask vs. save_selection and get_generated_image vs. get_layer_set, even though the descriptions clarify them.

    Naming Consistency5/5

    All tool names use consistent snake_case with clear verb_noun phrasing (get_*, save_*, generate_image, list_image_providers). There are no mixed naming conventions or vague standalone verbs.

    Tool Count3/5

    Nine tools is not excessive in raw count, but the surface is inflated by six image-card UI helpers that are not useful for an agent to call directly. The effective agent-facing surface is only about three tools, making the set feel heavier and less focused than it should be.

    Completeness4/5

    The core image-generation workflow is well covered: generating, editing, combining, splitting into layers, multi-prompt galleries, provider listing, and local file-path guidance. Minor gaps remain around image history/listing, cancellation, or explicit deletion, but the main lifecycle is usable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers