AI Wave vs Llm Prices Cn
A side-by-side look at the AI Wave and Llm Prices Cn 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 Llm Prices Cn 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 Llm Prices Cn 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 want tools like
query_model_price, estimate_cost.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 52/100 · Good | 59/100 · Good |
| 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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View AI Wave | View Llm Prices Cn |
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?
Llm Prices Cn tools 2
query_model_price查询指定大模型（如 GPT-5, Claude, DeepSeek）的最新 API 输入、输出和缓存输入单价（单位：每百万 tokens）。estimate_cost估算一段文本或指定 token 数在某个大模型上的**输入侧**调用成本，以人民币 ¥ 计价。text_or_tokens 支持两种模式：传自然语言文本时自动估算 token 数（中文按字符、英文按词分别计），传纯数字字符串时直接作为已知 token 数使用。返回：所用估算方法、token 数、按原价计的输入成本；若该模型提供缓存输入价，另给出缓存命中成本、相对原价的节省百分比与倍数差价；末尾附该模型的输入 / 输出 / 缓存输入单价（每百万 tokens）。⚠️ 本工具只计算输入成本，不含输出 token 费用——要估算完整往返成本，需另取输出单价自行相加。
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"
}
}
}
}
Llm Prices Cn
{
"mcpServers": {
"szp2005-llm-prices-cn": {
"url": "https://www.llmabacus.com/api/mcp/mcp"
}
}
}
Frequently asked questions
AI Wave is categorized under Aggregators and uses a local stdio subprocess. Llm Prices Cn belongs to Aggregators and uses a remote HTTP/SSE transport. Pick AI Wave for aggregators work and Llm Prices Cn 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. Llm Prices Cn 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 szp2005-llm-prices-cn 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. Llm Prices Cn has 59/100 (Good) with 3 views, 0 installs and 0 GitHub stars.