AllMCPs Server vs Mediamcp
A side-by-side look at the AllMCPs Server and Mediamcp MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AllMCPs Server for aggregators work over a hosted endpoint; choose Mediamcp 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 AllMCPs Server when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
ALLMCPS_MCP_URL. - You want tools like
search_mcp_servers, get_mcp_install_config, recommend_mcp_stack.
Choose Mediamcp 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:
OPENROUTER_API_KEY. - You want tools like
generate_image, edit_image, generate_video.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Multimedia Process |
| Quality signal | 85/100 · Excellent | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | ALLMCPS_MCP_URL | OPENROUTER_API_KEY |
| Verified owner | Verified | Community listing |
| GitHub stars | 4 | 4 |
| Directory activity | 59 views 20 installs 1 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 11 | 6 |
| Full listing | View AllMCPs Server | View Mediamcp |
Tools & capabilities
AllMCPs Server tools 11
search_mcp_serversSearch the AllMCPs directory for Model Context Protocol (MCP) servers by keyword or category.get_mcp_install_configGet the exact claude_desktop_config.json setup snippet and documentation for a specific MCP server by ID.recommend_mcp_stackRecommend a curated multi-tool MCP server stack for a specific developer role or workflow (e.g. "fullstack", "data science", "devops").list_mcp_categoriesList all categories available in the AllMCPs directory along with server counts.get_boost_pricingGet pricing and features for boosting / featuring an MCP server on AllMCPs.com.boost_mcp_serverInitiate a sponsorship / boost order for an MCP server by ID, returning a Stripe checkout session URL and x402 invoice.get_boost_statusCheck current boost status, verified badge level, and sponsorship expiration for an MCP server by ID.submit_mcp_serverProgrammatically submit a new MCP server repository to AllMCPs.com for indexing and review. Supports the same optional enrichment fields as the human submission form — fill in whichever you can confidently determine from the repository (README, package.json, code) to produce a fully flushed-out listing. Omit anything you are not confident about rather than guessing; all enrichment fields are optional and unrecognized enum values are simply dropped, not rejected.verify_mcp_claimVerify ownership and claim an MCP server listing by checking GitHub README badge, website badge, or DNS TXT record. Works two ways: (1) fully unattended — pass `agentToken` from confirm_mcp_agent (or set an `Authorization: Bearer <token>` header if your client supports it), no human sign-in needed; or (2) if called with neither, requires the caller to already have an active AllMCPs browser session. Unattended agents should use register_mcp_agent + confirm_mcp_agent first.register_mcp_agentStart unattended-agent registration: emails a 6-digit confirmation code to the given address. Follow up with confirm_mcp_agent to exchange the code for a bearer token, which unlocks verify_mcp_claim (and future privileged tools) without ever needing a human to sign in via browser.confirm_mcp_agentExchange the 6-digit code emailed by register_mcp_agent for a durable bearer token (90-day TTL). Pass the returned token as `agentToken` on verify_mcp_claim, or set it as an `Authorization: Bearer <token>` header on subsequent MCP requests if your client supports that.
Mediamcp tools 6
generate_imageGenerate one or more images from a text prompt using a cloud AI model. Every image is saved to disk and its absolute path is returned, along with a small inline preview. Use edit_image instead when starting from an existing image.edit_imageEdit or transform existing image(s) with a text instruction — restyle, add or remove elements, change background, or combine several images into one scene. The result is saved to disk and its absolute path is returned, along with a small inline preview.generate_videoGenerate a video from a text prompt, and optionally from an input image (image-to-video). Async job: starts generation, then waits and polls. Video generation typically takes 1-5 minutes. The finished file is saved to disk and its absolute path is returned. If waiting times out, a polling_url is returned — pass it to check_video_status later instead of starting a new (billed) job. For image-to-video, pass first_frame_image so the clip animates from that exact picture (e.g. a still produced by generate_image). Image inputs require an image-to-video-capable model such as 'bytedance/seedance-2.0', 'bytedance/seedance-2.0-fast', or 'google/veo-3.1'.check_video_statusCheck a previously started video generation job (from generate_video's polling_url or video id). If the job has completed, downloads the video, saves it to disk, and returns the absolute path.list_modelsList image- and video-capable model slugs available on the configured endpoint, with pricing where known. Use this to pick a `model` value for generate_image, edit_image, or generate_video.check_configDiagnose the mediamcp server setup: endpoint, API key presence and validity, default models, and output directory writability. Run this first when any other mediamcp tool fails.
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.
AllMCPs Server
{
"mcpServers": {
"allmcps-server": {
"command": "npx",
"args": [
"-y",
"allmcps-server"
],
"env": {
"ALLMCPS_MCP_URL": "YOUR_ALLMCPS_MCP_URL_HERE"
}
}
}
}
Mediamcp
{
"mcpServers": {
"legolev-mediamcp": {
"command": "npx",
"args": [
"-y",
"mediamcp"
],
"env": {
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE"
}
}
}
}
Frequently asked questions
AllMCPs Server is categorized under Aggregators and uses a remote HTTP/SSE transport. Mediamcp belongs to Multimedia Process and uses a local stdio subprocess. Pick AllMCPs Server for aggregators work and Mediamcp 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.
AllMCPs Server is listed as free. Auth: no auth required. Mediamcp is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 allmcps-server and legolev-mediamcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AllMCPs Server has a quality signal of 85/100 (Excellent) with 59 views, 20 installs and 4 GitHub stars. Mediamcp has 64/100 (Good) with 2 views, 0 installs and 4 GitHub stars.
