EverArt Forge MCP Server

EverArt Forge MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Generates both vector and raster images using EverArt's AI models, providing flexible storage and format conversion.

What you get

An advanced Model Context Protocol (MCP) server for Cline that integrates with EverArt's AI models to generate both vector and raster images. This server provides powerful image generation capabilities with flexible storage options and format conversion.

• Vector Graphics Generation —
• Create SVG vector graphics using Recraft-Vector model
• Automatic SVG optimization
• Perfect for logos, icons, and scalable graphics
• Raster Image Generation —
• Support for PNG, JPEG, and WebP formats

What the assistant can call

Once EverArt Forge is connected, these are the calls the assistant has available:

• generate_image — Notes: - SVG format is only available with Recraft-Vector (8000) model - Default format is "svg" for model 8000, "png" for others - You can specify
• list_images — The list_images tool exposed by this server
• view_image — The view_image tool exposed by this server

Configuration and credentials

You will need one environment variable: EVERART_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. EverArt Forge's toolset — generate_image, list_images, view_image — is a fair guide to whether it matches your workflow. It is maintained by nickbaumann98; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against EverArt Forge's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the everart forge mcp server does with a few real requests.