AI Wave vs AllMCPs Server
A side-by-side look at the AI Wave and AllMCPs Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AI Wave for aggregators work as a local process; choose AllMCPs Server for aggregators over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AI Wave when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
AIWAVE_API_KEY. - You want tools like
list_model_changes, get_model, search_models.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 52/100 · Good | 85/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | AIWAVE_API_KEY | ALLMCPS_MCP_URL |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 59 views 20 installs 1 upvotes |
| Tools | 3 | 11 |
| Full listing | View AI Wave | View AllMCPs Server |
Tools & capabilities
AI Wave tools 3
list_model_changesWhat changed since I last checked? Poll with `since`, feed back `latest`.get_modelPrice, context and catalog status for one model (OpenRouter or Hugging Face id).search_modelsWhich models fit this budget and context, ordered by current attention?
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.
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.
AI Wave
{
"mcpServers": {
"ai-wave": {
"command": "npx",
"args": [
"-y",
"@elopstudio/ai-wave-mcp"
],
"env": {
"AIWAVE_API_KEY": "YOUR_AIWAVE_API_KEY_HERE"
}
}
}
}
AllMCPs Server
{
"mcpServers": {
"allmcps-server": {
"command": "npx",
"args": [
"-y",
"allmcps-server"
],
"env": {
"ALLMCPS_MCP_URL": "YOUR_ALLMCPS_MCP_URL_HERE"
}
}
}
}
Frequently asked questions
AI Wave is categorized under Aggregators and uses a local stdio subprocess. AllMCPs Server belongs to Aggregators and uses a remote HTTP/SSE transport. Pick AI Wave for aggregators work and AllMCPs Server for aggregators.
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.
AI Wave has no declared pricing — check the project's own site. AllMCPs Server is listed as free. Auth: no auth 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 ai-wave and allmcps-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AI Wave has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. AllMCPs Server has 85/100 (Excellent) with 59 views, 20 installs and 4 GitHub stars.