Corent vs Imgx

A side-by-side look at the Corent and Imgx MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Corent logoCorentMultimedia Process · Local subprocess (stdio)Generate images and videos via the Corent API — auto model routing with provider fallback.51GoodAuth: not declaredImgx logoImgxMultimedia Process · Local subprocess (stdio)AI image generation and editing via CLI or MCP. Text-based editing, multi-provider.52GoodAuth: not declared

Verdict: choose Corent for multimedia process work as a local process; choose Imgx 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?

Corent logoChoose Corent when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: CORENT_API_KEY.
  • You want tools like plan, create, generate_image.
Explore Corent

Imgx logoChoose Imgx when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: GEMINI_API_KEY.
  • You want tools like generate_image, edit_image, edit_last.
Explore Imgx

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCorent logoCorentImgx logoImgx
CategoryMultimedia ProcessMultimedia Process
Quality signal51/100 · Good52/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsCORENT_API_KEYGEMINI_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars01
Directory activity 0 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools710

Tools & capabilities

Corent tools 7

  • planDescribe a request in plain language; Corent returns the plan (image vs video, tier, settings) + cost estimate, without generating
  • createDescribe what you want + a spend ceiling; Corent decides everything and generates it (the "zero decisions" path)
  • generate_imageText → image, synchronous, returns a permanent URL
  • generate_videoText (or image) → video, async job
  • get_jobPoll a job until completed
  • get_balanceRemaining account balance
  • get_statusLive tier health

Imgx tools 10

  • generate_imageGenerate an image from a text prompt
  • edit_imageEdit an existing image with text instructions
  • edit_lastEdit the last generated/edited image (no input path needed)
  • undo_editUndo the last edit, reverting to the previous image in the session
  • redo_editRedo a previously undone edit
  • edit_historyShow all sessions and their edit history with metadata
  • switch_sessionSwitch to a different editing session
  • clear_historyClear project history (optionally delete image files)
  • set_output_dirChange the default output directory (optionally move existing files)
  • list_providersList available providers and capabilities

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.

Corent

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "corent-2": {
      "command": "npx",
      "args": [
        "-y",
        "corent-mcp"
      ],
      "env": {
        "CORENT_API_KEY": "YOUR_CORENT_API_KEY_HERE"
      }
    }
  }
}

Imgx

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "imgx": {
      "command": "npx",
      "args": [
        "-y",
        "has"
      ],
      "env": {
        "GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Corent is categorized under Multimedia Process and uses a local stdio subprocess. Imgx belongs to Multimedia Process and uses a local stdio subprocess. Pick Corent for multimedia process work and Imgx 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.

Corent has no declared pricing — check the project's own site. Imgx has no declared pricing — check the project's own site. 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 corent-2 and imgx as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Corent has a quality signal of 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Imgx has 52/100 (Good) with 0 views, 0 installs and 1 GitHub stars.