Glassypic vs MCP Image
A side-by-side look at the Glassypic and MCP Image MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Glassypic for multimedia process work as a local process; choose MCP Image for multimedia process as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Glassypic when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You want tools like
optimize_image, login, logout.
Choose MCP Image when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
GEMINI_API_KEY, OPENAI_API_KEY, ARK_API_KEY, IMAGE_PROVIDER, IMAGE_OUTPUT_DIR, IMAGE_QUALITY, SKIP_PROMPT_ENHANCEMENT.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 61/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | GEMINI_API_KEYOPENAI_API_KEYARK_API_KEYIMAGE_PROVIDERIMAGE_OUTPUT_DIRIMAGE_QUALITYSKIP_PROMPT_ENHANCEMENT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 181 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Glassypic | View MCP Image |
Tools & capabilities
Glassypic tools 5
optimize_imageOptimize an image: smart lossy compression (typically 60-80% size reduction), optional resize/upscale/format conversion, and AI-generated SEO metadata. Accepts absolute local file paths or remote URLs. In remote/API mode, only remote URLs are supported. Supported input formats: JPG, PNG, WebP, AVIF, GIF, SVG, ICO, HEIC, TIFF, BMP (max 50 MB). Supported output formats: JPG, PNG, WebP, AVIF, GIF, SVG, ICO. Credits: 3 to compress (always), +1 if width or height is set, +2 to upscale, +1 for SEO tags (on by default). A full pipeline is 7 credits. Upscale is charged whether you request it or the server adds it automatically — it does so whenever a resize target exceeds the source by more than 1.2x, so a resize-only call on a small image also costs 7. SVG or ICO output is a flat 1 credit, overriding everything above. Animated GIFs are billed per frame: (per-frame operations x frames) + 1 if tags, up to 601 credits at the 100-frame limit — confirm_gif_cost gates that path. GIFs are excluded from automatic upscaling. Guest (unregistered): 20 credits/day, no signup. Log in with the login tool for more credits — registered Free tier is 30/day. Use status tool to check remaining credits before batch processing.loginLog in to your GlassyPic account via browser to unlock more credits. Opens a browser window where you complete login (Google, Facebook, or email). After login, MCP automatically picks up your account with shared credits across web and MCP. Registered accounts receive a larger credit allowance than guest sessions; use the status tool to read the account's actual tier and remaining credits. Your access token and email are stored locally at ~/.glassypic/session.json (file mode 0600) until you run logout.logoutLog out of your GlassyPic account. Reverts to guest session (20 free credits/day). Your web app account is not affected.statusCheck your GlassyPic account status: login state, tier, credits remaining, and credit reset time. Use this before batch processing to verify sufficient credits.upgradeOpen the GlassyPic pricing page in the user's browser, where the account's plan can be reviewed and changed. Call this only when the user asks to change or review their plan.
MCP Image tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Glassypic
{
"mcpServers": {
"glassypic": {
"command": "npx",
"args": [
"-y",
"@glassypic/mcp-server@latest"
]
}
}
}
MCP Image
{
"mcpServers": {
"mcp-image": {
"command": "npx",
"args": [
"-y",
"mcp-image"
],
"env": {
"GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE",
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"ARK_API_KEY": "YOUR_ARK_API_KEY_HERE",
"IMAGE_PROVIDER": "YOUR_IMAGE_PROVIDER_HERE",
"IMAGE_OUTPUT_DIR": "YOUR_IMAGE_OUTPUT_DIR_HERE",
"IMAGE_QUALITY": "YOUR_IMAGE_QUALITY_HERE",
"SKIP_PROMPT_ENHANCEMENT": "YOUR_SKIP_PROMPT_ENHANCEMENT_HERE"
}
}
}
}
Frequently asked questions
Glassypic is categorized under Multimedia Process and uses a local stdio subprocess. MCP Image belongs to Multimedia Process and uses a local stdio subprocess. Pick Glassypic for multimedia process work and MCP Image for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Glassypic has no declared pricing — check the project's own site. MCP Image is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add glassypic and mcp-image as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Glassypic has a quality signal of 61/100 (Good) with 3 views, 0 installs and 2 GitHub stars. MCP Image has 53/100 (Good) with 2 views, 0 installs and 181 GitHub stars.