MCP Image vs Vocuno
A side-by-side look at the MCP Image and Vocuno MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Image for multimedia process work as a local process; choose Vocuno 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 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.
Choose Vocuno when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 53/100 · Good | 74/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | OAuth 2.0 |
| Pricing | BYOK (pay the provider) | Freemium |
| Required env vars | GEMINI_API_KEYOPENAI_API_KEYARK_API_KEYIMAGE_PROVIDERIMAGE_OUTPUT_DIRIMAGE_QUALITYSKIP_PROMPT_ENHANCEMENT | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 181 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 48 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Image | View Vocuno |
Tools & capabilities
MCP Image tools
No tool names declared yet. Check the project README from the listing page.
Vocuno 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.
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"
}
}
}
}
Vocuno
{
"mcpServers": {
"vocuno": {
"url": "https://vocuno.com/mcp"
}
}
}
Frequently asked questions
MCP Image is categorized under Multimedia Process and uses a local stdio subprocess. Vocuno belongs to Multimedia Process and uses a remote HTTP/SSE transport. Pick MCP Image for multimedia process work and Vocuno 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.
MCP Image is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Vocuno is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 mcp-image and vocuno as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Image has a quality signal of 53/100 (Good) with 2 views, 0 installs and 181 GitHub stars. Vocuno has 74/100 (Great) with 48 views, 0 installs and 1 GitHub stars.