Imgx vs Kuro
A side-by-side look at the Imgx and Kuro MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Imgx for multimedia process work as a local process; choose Kuro for multimedia process over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 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.
Choose Kuro when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 52/100 · Good | 70/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | GEMINI_API_KEY | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 1 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 1 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Imgx | View Kuro |
Tools & capabilities
Imgx tools 10
generate_imageGenerate an image from a text promptedit_imageEdit an existing image with text instructionsedit_lastEdit the last generated/edited image (no input path needed)undo_editUndo the last edit, reverting to the previous image in the sessionredo_editRedo a previously undone editedit_historyShow all sessions and their edit history with metadataswitch_sessionSwitch to a different editing sessionclear_historyClear project history (optionally delete image files)set_output_dirChange the default output directory (optionally move existing files)list_providersList available providers and capabilities
Kuro 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.
Imgx
{
"mcpServers": {
"imgx": {
"command": "npx",
"args": [
"-y",
"has"
],
"env": {
"GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE"
}
}
}
}
Kuro
{
"mcpServers": {
"kuro": {
"url": "https://api.meetkuro.com/mcp"
}
}
}
Frequently asked questions
Imgx is categorized under Multimedia Process and uses a local stdio subprocess. Kuro belongs to Multimedia Process and uses a remote HTTP/SSE transport. Pick Imgx for multimedia process work and Kuro 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.
Imgx has no declared pricing — check the project's own site. Kuro 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 imgx and kuro as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Imgx has a quality signal of 52/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Kuro has 70/100 (Great) with 3 views, 0 installs and 0 GitHub stars.