Back to Browse

Imagor MCP Server

by Cshum
Developer ToolsLow Risk10.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

Build and verify imagor image URLs, and render layouts at any canvas size, from an MCP client.

About

Build and verify imagor image URLs, and render layouts at any canvas size, from an MCP client.

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (4 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

7 files analyzed · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

The imagor server these tools build URLs for, for example http://localhost:8000Optional

Environment variable: IMAGOR_BASE_URL

Set to 1 when the imagor server runs in unsafe mode. Leave unset when it is signed.Optional

Environment variable: IMAGOR_UNSAFE

The signing secret, when the imagor server is signed. Must match the server's own secret and signer settings.Required

Environment variable: IMAGOR_SECRET

sha1, sha256 or sha512. Must match the imagor server, and defaults to sha1 as the server does.Optional

Environment variable: IMAGOR_SIGNER_TYPE

Documentation

View on GitHub

From the project's GitHub README.

Imagor MCP

Test Status Docs

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.

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.

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
{
  "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

Reviews

No reviews yet

Be the first to review this server!