About Imagor MCP
Imagor MCP adds a template layer to imagor, letting agents turn image layouts such as social cards, product grids, and testimonials into imagor URLs. It is for users who run imagor and want clients to compose and render layouts without writing its path syntax.
Key features
- 01Compile agent-written layouts into imagor URLs
- 02Compose and render image layouts through tools
- 03Reject layouts that cannot be rendered
- 04Includes a skill and ready-made recipes
Use cases
- 01Generating social sharing cards
- 02Rendering product grids
- 03Creating quote or testimonial images
MCP support
The MCP server exposes tools that let clients compose layouts, render them through an existing imagor instance, inspect the result, and return its URL. It connects to imagor using IMAGOR_BASE_URL and matching mode settings.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEImagor MCP
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.
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 client | what to do |
|---|---|
| VS Code | add it from here — one click |
| Claude Desktop | open imagor-mcp.mcpb — one click |
| Cursor, Claude Code, Windsurf | add the block below to its config file |
| Codex | the 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.