A side-by-side look at the ClipEmber and MakeAIVideo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ClipEmber for social media work over a hosted endpoint; choose MakeAIVideo for social media as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
C
Choose ClipEmber when
You need dedicated capabilities in the Social Media domain.
No tool names declared yet. Check the project README from the listing page.
MakeAIVideo 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.
ClipEmber is categorized under Social Media and uses a remote HTTP/SSE transport. MakeAIVideo belongs to Social Media and uses a local stdio subprocess. Pick ClipEmber for social media work and MakeAIVideo for social media.
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.
ClipEmber has no declared pricing — check the project's own site. MakeAIVideo 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 clipember and makeaivideo-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ClipEmber has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MakeAIVideo has 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.