Everygen vs Imageat
A side-by-side look at the Everygen and Imageat MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Everygen for multimedia process work over a hosted endpoint; choose Imageat 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 Everygen 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.
Choose Imageat when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
IMAGEAT_API_KEY. - You want tools like
imageat_generate_image, imageat_generate_video, imageat_check_credits.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 41/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | IMAGEAT_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Everygen | View Imageat |
Tools & capabilities
Everygen tools
No tool names declared yet. Check the project README from the listing page.
Imageat tools 3
imageat_generate_imageText-to-image / image-to-image. Returns CDN image URL(s).imageat_generate_videoText-to-video / image-to-video. Returns a CDN mp4 URL.imageat_check_creditsCurrent credit balance.
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.
Everygen
{
"mcpServers": {
"everygen": {
"url": "https://everygen-ai.com/mcp"
}
}
}
Imageat
{
"mcpServers": {
"imageat": {
"command": "npx",
"args": [
"-y",
"@imageat/mcp"
],
"env": {
"IMAGEAT_API_KEY": "YOUR_IMAGEAT_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Everygen is categorized under Multimedia Process and uses a remote HTTP/SSE transport. Imageat belongs to Multimedia Process and uses a local stdio subprocess. Pick Everygen for multimedia process work and Imageat 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.
Everygen has no declared pricing — check the project's own site. Auth: oauth 2.0. Imageat 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 everygen and imageat as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Everygen has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Imageat has 49/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.