mcp-image-extractor and image-worker-mcp
These two tools are complements: one provides image analysis capabilities for LLMs in agent mode, while the other focuses on image manipulation and storage, both within the MCP server framework.
About mcp-image-extractor
ifmelate/mcp-image-extractor
MCP server which allow LLM in agent mode to analyze image whenever it needs
Implements three extraction tools—from local files, URLs, and base64 data—with automatic image resizing to 512x512 pixels to optimize LLM context usage. Built as an MCP server that integrates with Cursor and Claude via stdio transport, enabling AI agents to dynamically fetch and analyze images during multi-step tasks like test result review. Handles playwright screenshots and other image-based workflows where agents need on-demand visual context without pre-loading.
About image-worker-mcp
BoomLinkAi/image-worker-mcp
Effortlessly resize, convert, optimize, and transform images with a single MCP server—then upload them directly to S3, Cloudflare R2, or Google Cloud Storage. Ideal for AI workflows, automation scripts, and developers who want seamless image handling in one tool.
Implements the Model Context Protocol (MCP) via stdio transport to integrate seamlessly with AI assistants and code editors (Cursor, Claude, VSCode, Zed, etc.). Built on the sharp library for fast image processing, it supports flexible input formats—file paths, URLs, and base64—and chains operations like resizing, format conversion, and optimization before uploading to cloud storage with configurable credentials.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work