Image Extractor

Created By
ifmelatea year ago
Overview

what is Image Extractor?

Image Extractor is an MCP server designed for extracting and converting images to base64 format for LLM analysis, enabling AI assistants to process images efficiently.

how to use Image Extractor?

To use Image Extractor, install it via Smithery or manually from GitHub, and then utilize its tools to extract images from local files or URLs, or process base64-encoded images.

key features of Image Extractor?

  • Extract images from local files and URLs
  • Convert images to base64 format
  • Automatically resize images for optimal LLM analysis

use cases of Image Extractor?

  1. Extracting images from user-uploaded files for analysis.
  2. Fetching images from the web for processing in AI applications.
  3. Converting images to base64 for integration with LLMs.

FAQ from Image Extractor?

  • Can Image Extractor handle all image formats?

Yes! Image Extractor can process various image formats as long as they are supported by the underlying libraries.

  • Is there a limit on image size?

Yes, the maximum image size is configurable, with a default limit of 10MB.

  • How do I install Image Extractor?

You can install it via Smithery or manually by cloning the GitHub repository and following the installation instructions.

Server Config

{
  "mcpServers": {
    "image-extractor": {
      "command": "node",
      "args": [
        "/full/path/to/mcp-image-extractor/dist/index.js"
      ],
      "disabled": false
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ifmelate
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago