AI Wave vs Settlegrid Discovery
A side-by-side look at the AI Wave and Settlegrid Discovery 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 Settlegrid Discovery for aggregators as a local process. 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 Settlegrid Discovery when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 52/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | AIWAVE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View AI Wave | View Settlegrid Discovery |
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?
Settlegrid Discovery 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.
AI Wave
{
"mcpServers": {
"ai-wave": {
"command": "npx",
"args": [
"-y",
"@elopstudio/ai-wave-mcp"
],
"env": {
"AIWAVE_API_KEY": "YOUR_AIWAVE_API_KEY_HERE"
}
}
}
}
Settlegrid Discovery
{
"mcpServers": {
"settlegrid-discovery": {
"command": "npx",
"args": [
"-y",
"create-settlegrid-tool"
]
}
}
}
Frequently asked questions
AI Wave is categorized under Aggregators and uses a local stdio subprocess. Settlegrid Discovery belongs to Aggregators and uses a local stdio subprocess. Pick AI Wave for aggregators work and Settlegrid Discovery 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. Settlegrid Discovery 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 ai-wave and settlegrid-discovery 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. Settlegrid Discovery has 39/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.