MCP Image Extractor
MCP 图像提取器
MCP 服务器用于提取图像并将其转换为 base64 以进行 LLM 分析。
该 MCP 服务器为 AI 助手提供以下工具:
从本地文件提取图像
从 URL 中提取图像
处理 base64 编码的图像
它在 Cursor 中的样子:
适用案例:
分析剧作家测试结果:屏幕截图
对于 Cursor 或其他客户端
手动安装
# Clone and install
git clone https://github.com/ifmelate/mcp-image-extractor.git
cd mcp-image-extractor
npm install
npm run build
npm link这将使mcp-image-extractor命令在全球范围内可用。
使用 .cursor/mcp.json 文件
对于本地开发或在特定项目中工作时,您可以在项目根目录中添加.cursor/mcp.json文件:
{
"mcpServers": {
"image-extractor": {
"command": "node",
"args": ["/full/path/to/mcp-image-extractor/dist/index.js"],
"disabled": false
}
}
}或者,如果您已经通过 npm link 安装:
{
"mcpServers": {
"image-extractor": {
"command": "mcp-image-extractor",
"disabled": false
}
}
}光标用户的重要提示:如果您看到“无法创建客户端”错误,请尝试以下替代方法:
选项 1:使用直接 GitHub 安装
git clone https://github.com/ifmelate/mcp-image-extractor.git cd mcp-image-extractor npm install npm run build npm link然后在
.cursor/mcp.json中进行配置:{ "mcpServers": { "image-extractor": { "command": "mcp-image-extractor", "disabled": false } } }选项 2:克隆并在本地运行
git clone https://github.com/ifmelate/mcp-image-extractor.git cd mcp-image-extractor npm install npm run build然后在
.cursor/mcp.json中进行配置:{ "mcpServers": { "image-extractor": { "command": "node", "args": ["/full/path/to/mcp-image-extractor/dist/index.js"], "disabled": false } } }
可用工具
从文件中提取图像
从本地文件中提取图像并将其转换为 base64。
参数:
file_path(必需):本地图像文件的路径
**注意:**所有图像都会自动调整为最佳尺寸(最大 512x512),以进行 LLM 分析,从而限制 base64 输出的大小并优化上下文窗口的使用。
从 URL 中提取图像
从 URL 中提取图像并将其转换为 base64。
参数:
url(必填):要提取的图像的 URL
**注意:**所有图像都会自动调整为最佳尺寸(最大 512x512),以进行 LLM 分析,从而限制 base64 输出的大小并优化上下文窗口的使用。
从base64提取图像
处理 base64 编码的图像以进行 LLM 分析。
参数:
base64(必需):Base64 编码的图像数据mime_type(可选,默认值:“image/png”):图像的 MIME 类型
**注意:**所有图像都会自动调整为最佳尺寸(最大 512x512),以进行 LLM 分析,从而限制 base64 输出的大小并优化上下文窗口的使用。
Related MCP server: MCP URL Fetcher
示例用法
以下是如何使用 Claude 工具的示例:
Please extract the image from this local file: images/photo.jpgClaude 会自动使用extract_image_from_file工具来加载和分析图像内容。
Please extract the image from this URL: https://example.com/image.jpgClaude 将自动使用extract_image_from_url工具来获取和分析图像内容。
Docker
使用 Docker 构建并运行:
docker build -t mcp-image-extractor .
docker run -p 8000:8000 mcp-image-extractor执照
麻省理工学院
Available Tools
3 toolsextract_image_from_base64A
Extract and analyze images from base64-encoded data. Ideal for processing screenshots from clipboard, dynamically generated images, or images embedded in applications without requiring file system access.
Inputs: base64 (required), max_height, max_width, mime_type, +1 more.
extract_image_from_fileA
Extract and analyze images from local file paths. Supports visual content understanding, OCR text extraction, and object recognition for screenshots, photos, diagrams, and documents.
Inputs: file_path (required), max_height, max_width, resize.
extract_image_from_urlA
Extract and analyze images from web URLs. Perfect for analyzing web screenshots, online photos, diagrams, or any image accessible via HTTP/HTTPS for visual content analysis and text extraction.
Inputs: url (required), max_height, max_width, resize.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose based on the source of the image: base64-encoded data, local file paths, and web URLs. The descriptions reinforce this by specifying different use cases (e.g., clipboard screenshots, local files, online images), leaving no ambiguity for an agent to misselect.
All tool names follow a consistent verb_noun pattern with 'extract_image_from_' as a prefix, followed by the source type (base64, file, url). This predictable naming scheme makes it easy for agents to understand and navigate the tool set without confusion.
With 3 tools, the server is well-scoped for its purpose of extracting images from different sources. Each tool earns its place by covering a distinct input method (base64, file, URL), providing a complete set for the domain without being overly sparse or bloated.
The tool surface is complete for the domain of image extraction, covering all major input sources: base64 data, local files, and web URLs. There are no obvious gaps, as these three methods encompass the typical ways images are accessed in applications, ensuring agents can handle various scenarios without dead ends.
Related MCP Connectors
A Model Context Protocol server for Wix AI tools
OCR, transcription, file extraction, and image generation for AI agents via MCP.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Generate images from Claude, ChatGPT, Cursor and Codex with 12 top AI image models. Up to 4 images per call, SVG vectorization, background removal, upscaling and image-to-video. Remote MCP with OAuth, no API keys.
Related MCP Servers
- AlicenseAqualityBmaintenanceA Model Context Protocol server that enables fetching and processing images from URLs, local file paths, and numpy arrays, returning them as base64-encoded strings with proper MIME types.122MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables LLMs to fetch and process web content in multiple formats (HTML, JSON, Markdown, text) with automatic format detection.56MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that converts diverse file types, including PDFs, images, audio, and Office documents, into Markdown format. It also transforms web content like YouTube transcripts and Bing search results into readable text for model consumption.13681 npmMIT
- FlicenseNot gradedqualityDmaintenanceA powerful Model Context Protocol (MCP) server for image processing, designed to empower AI models with advanced image manipulation capabilities.1-