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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

11 hours ago
Voyei

an hour ago