Image Processing
Let your agent resize, convert, compress, and pipeline images via Pictomancer without shelling out to ad-hoc ImageMagick scripts.
Overview
ai.pictomancer/image-processing is a MCP server for the Build phase that lets agents resize, convert, compress, and pipeline images through Pictomancer's HTTP API.
What is this MCP server?
- Resize, convert, compress, and multi-step image pipelines for agent workflows
- Hosted streamable-http remote at https://api.pictomancer.ai/mcp (v0.3.0)
- Targets AI agents that need deterministic media ops during build and content tasks
- GitLab-backed pig-gateway repository for the gateway implementation
- Reduces one-off CLI image scripts in frontend and landing-page generation loops
- Catalog version 0.3.0
- Remote URL https://api.pictomancer.ai/mcp
- Transport: streamable-http
What problem does it solve?
Agents waste turns and break builds when image assets need manual resizing, conversion, or compression outside the repo.
Who is it for?
Builders automating OG images, app icons, screenshot crops, and compress-and-upload prep from the agent.
Skip if: Heavy creative retouching, on-prem-only media pipelines with no external API, or teams that require all bytes to stay local.
What do I get? / Deliverables
After you add the remote MCP URL, the agent can run image processing steps as tools while you build UI and content.
- Remote MCP registration for Pictomancer image tools
- Agent-driven resize, convert, and compress operations on image files
- Repeatable image pipelines for build and content deliverables
Recommended MCP Servers
Journey fit
Image prep lands in Build when you are shipping UI assets, thumbnails, OG images, and marketplace screenshots alongside the product. Integrations is the shelf because the server is a remote HTTP MCP endpoint your agent calls—not a design critique skill.
How it compares
Remote image-ops MCP integration, not a Figma plugin or a static design SKILL.
Common Questions / FAQ
Who is ai.pictomancer/image-processing for?
Developers and solo founders who want their MCP agent to handle routine image transforms during build and content work.
When should I use ai.pictomancer/image-processing?
Use it while building frontends, docs, or landing pages whenever the agent must normalize dimensions, formats, or file size before commit or deploy.
How do I add ai.pictomancer/image-processing to my agent?
Register the streamable-http remote https://api.pictomancer.ai/mcp in your MCP client and follow Pictomancer auth or account setup if required.