Imagor MCP

io.github.cshumPublished by GitHub account cshumv0.7.9Updated Oct 24, 2026

An MCP server and a skill for imagor, compiling agent-written image layouts into one URL.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

An MCP server and skill that turn agent-written image layouts, such as OG cards and product grids, into a single imagor URL rendered by your own imagor instance

What you can do
Compose image layouts from a description, such as OG cards, product grids, quotes or testimonials, and compile them into one imagor URL. Build imagor paths through the tools instead of writing path syntax by hand, with invalid paths refused. Render the layout through your running imagor instance and inspect the result before handing back the URL. Follow ready-made recipes and prompts for common layouts.
When to use it
Use it when you already run imagor and want an assistant to design and render share cards, product grids or quote images as URLs, without learning imagor's path syntax. It suits trying out layouts locally before making anything public.
Requirements
A local process installed via Homebrew, an mcpb package, a container image or a Windows binary, plus a running imagor instance. Set IMAGOR_BASE_URL to where imagor runs (defaults to The server will not start without either IMAGOR_UNSAFE set to 1 or IMAGOR_SECRET; IMAGOR_SIGNER_TYPE and IMAGOR_SIGNER_TRUNCATE must match the imagor server's configuration.
Before you install
IMAGOR_SECRET is a signing secret and must be kept private; unsafe mode is only for trying things out and production should use the secret. Signer type and truncation settings must match the imagor server or emitted URLs will not validate. Read the project's security notes before making anything public.

Installation

In SourceWeft

  1. Open Imagor MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Imagor MCP

[Test Status] [Docs] [Imagor MCP rated A on Glama]

An MCP server and a skill that add a template layer to imagor.

An agent writes a layout: OG cards, product grids, quotes, testimonials. It compiles to one imagor URL, rendered by the imagor you already run.

[Cards, each one a single imagor URL]

See the recipes »

Quick start

1. Run an imagor.

sh
docker run --rm -p 8000:8000 shumc/imagor -imagor-unsafe

Leave it running, and use a second terminal for the rest.

Unsafe mode is for trying things out. Production runs on IMAGOR_SECRET. See imagor's security docs.

2. Install the MCP server.

sh
brew trust cshum/tap && brew install imagor-mcp

3. Point a client at it.

your clientwhat to do
VS Codeadd it from here — one click
Claude Desktopopen imagor-mcp.mcpb — one click
Cursor, Claude Code, Windsurfadd the block below to its config file
Codexthe same values in TOML, at ~/.codex/config.toml
json
{  "mcpServers": {    "imagor": {      "command": "imagor-mcp",      "env": { "IMAGOR_UNSAFE": "1", "IMAGOR_BASE_URL": "http://localhost:8000" }    }  }}

Those two settings have to match what you started in step 1: IMAGOR_UNSAFE puts this server in the same mode, and IMAGOR_BASE_URL is where imagor is.

VS Code keys its servers under servers and Codex reads TOML, so the block above fits neither. Every client's config file is in Setup.

4. Ask it for something. See the recipes — each one carries a prompt to paste, or describe the image you want. The agent composes through the tools: it writes the layout, renders it, looks at the result, and hands you back the url. Neither of you needs imagor's path syntax: the tools build the path, and refuse one that cannot work.

That is the whole install. It is also in the official MCP Registry as io.github.cshum/imagor-mcp, which some clients install by name, and as ghcr.io/cshum/imagor-mcp in a container, which needs a different base URL, in Setup. Windows binaries are on the releases page.

Before anything is public, read Security: what this server is trusted with, and what it refuses.

Going deeper

  • Setup — every setting, the config file each client reads, and what to do before it is public.
  • Reference — every tool the server serves, the layout format, and the skill.
  • Cookbook — the ready-made layouts, and the url each one resolves to.
  • Contributing — building, testing, and the CLI.

Licence

MIT

Source: README.md at commit 4aec47e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

6
  1. v0.7.9LatestOct 15, 2026
  2. v0.7.7Oct 15, 2026
  3. v0.7.5Oct 15, 2026
  4. v0.7.2Oct 14, 2026
  5. v0.6.1Oct 14, 2026
  6. v0.6.0Oct 14, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts