Imageat vs Sequencer
A side-by-side look at the Imageat and Sequencer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Imageat for multimedia process work as a local process; choose Sequencer 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 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.
Choose Sequencer 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 | 49/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | IMAGEAT_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Imageat | View Sequencer |
Tools & capabilities
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.
Sequencer 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.
Imageat
{
"mcpServers": {
"imageat": {
"command": "npx",
"args": [
"-y",
"@imageat/mcp"
],
"env": {
"IMAGEAT_API_KEY": "YOUR_IMAGEAT_API_KEY_HERE"
}
}
}
}
Sequencer
{
"mcpServers": {
"sequencer": {
"url": "https://mcp.sequencer.media/"
}
}
}
Frequently asked questions
Imageat is categorized under Multimedia Process and uses a local stdio subprocess. Sequencer belongs to Multimedia Process and uses a remote HTTP/SSE transport. Pick Imageat for multimedia process work and Sequencer 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.
Imageat has no declared pricing — check the project's own site. Sequencer has no declared pricing — check the project's own site. 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 imageat and sequencer as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Imageat has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Sequencer has 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.