Imagician

Created By
flowy1110 months ago
A Model Context Protocol (MCP) server for comprehensive image editing operations including resizing, format conversion, cropping, compression, and more.
Overview

What is Imagician?

Imagician is a Model Context Protocol (MCP) server designed for comprehensive image editing operations, including resizing, format conversion, cropping, compression, and more.

How to use Imagician?

To use Imagician, install it via npm or clone the repository from GitHub. You can then configure it with Claude Desktop or run it directly from the command line.

Key features of Imagician?

  • Resize images with various fit options
  • Convert between formats like JPEG, PNG, WebP, and AVIF
  • Crop specific regions from images
  • Compress images while controlling quality
  • Rotate and flip images
  • Batch processing for generating multiple sizes from a single image
  • Extract metadata from images

Use cases of Imagician?

  1. Resizing images for web optimization
  2. Converting images to different formats for compatibility
  3. Cropping images for social media profiles
  4. Compressing images to save storage space
  5. Batch processing images for responsive design

FAQ from Imagician?

  • Can Imagician handle all image formats?

Yes! Imagician supports various formats including JPEG, PNG, WebP, and AVIF.

  • Is Imagician free to use?

Yes! Imagician is open-source and free to use.

  • How do I install Imagician?

You can install it via npm or clone the repository from GitHub.

Server Config

{
  "mcpServers": {
    "imagician": {
      "command": "npx",
      "args": [
        "-y",
        "@flowy11/imagician"
      ]
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
flowy11
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)

2 days ago