Day 2: Image Generation MCP
graphic design is not my passion
i'll write something around the ethics of ai art generation some other day, but to be frank, a lot of what is needed for corporate or personal media is pretty low value and wouldn't be a nice time for the artist nor the commissioning party.
as such, while i keep my writing human i'm very fine with image generation for infographics and miscellaneous things, it's crazy what you can prompt into existence.
while i was working on the ghost theme yesterday, i wanted to populate my demo 12 days with posts and i needed images for testing, so i made my day 2 deliverable a small MCP server:
(you can paste the below into Claude Code and it will install it for you)
Install: npx -y image-generation-mcp
https://www.npmjs.com/package/image-generation-mcp
You'll need to get an API key from google ai studio and save it in a .env
https://aistudio.google.com/app/api-keys
The MCP is open source and was designed so that it can be extended with more AI Image providers, feel free to review and contribute here if you'd like:
12-days-of-shipmas-2025
I also found that my MCP got indexed here:
Om-Shree-0709
I'll investigate this another day.
ciao :)
one more thing.. this one i found quite profound:
Image Generation Details
Prompt:
A surreal, absurdist scene of a robot artist having an existential crisis while painting. The robot is surrounded by floating blog post thumbnails and social media images it has created, but they’re all melting like Dali clocks. In the background, a giant glowing API key floats in the sky like a monolith from 2001 Space Odyssey. The robot holds a paintbrush but its arm is made of code and JSON brackets. Vaporwave color palette with pink and cyan gradients, retro 80s grid floor, glitch art effects. Text-free, moody lighting, cinematic composition.
Format: twitter-post
Title: When your MCP generates images but questions its own existence
Style: vaporwave, surrealist, glitch art, retro-futurism
The tool used was mcp__image-gen__generate_blog_image and it was called at timestamp 2025–12–29T23:08:19.632Z, with the result returned at 2025–12–29T23:08:27.754Z.
