AI model releases, price changes and deprecations in one feed: chat, embedding, speech, video.
MCP server for AI Wave — a normalized feed of AI model releases, price changes, API changes and deprecations, assembled from vendor release notes, Hugging Face, the OpenRouter catalog and GitHub.
Picking a model? Call the OpenRouter catalog directly — it is free and public.
This is for the other question: did anything I depend on change? New releases, price moves, and models being withdrawn, in one feed, deduplicated per model, each marked official or pending review.
Get a key at https://aiwave.elopstudio.com/member, then:
{
"mcpServers": {
"ai-wave": {
"command": "npx",
"args": ["-y", "@elopstudio/ai-wave-mcp"],
"env": { "AIWAVE_API_KEY": "aiw_live_..." }
}
}
}
If your client supports remote MCP, prefer that — no install, always current:
{
"mcpServers": {
"ai-wave": {
"type": "http",
"url": "https://aiwave.elopstudio.com/api/mcp",
"headers": { "Authorization": "Bearer aiw_live_..." }
}
}
}
| Tool | What it answers |
|---|---|
list_model_changes | What changed since I last checked? Poll with since, feed back latest. |
get_model | Price, context and catalog status for one model (OpenRouter or Hugging Face id). |
search_models | Which models fit this budget and context, ordered by current attention? |
Free tier: 1,000 calls/day. Remaining calls come back in x-ratelimit-remaining.
This package is a thin stdio wrapper around the remote endpoint — tool definitions live on the server, so you get new tools without updating it.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @elopstudio/ai-wave-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-elopstudio-aiwave-ai-wave": {
"command": "npx",
"args": [
"-y",
"@elopstudio/ai-wave-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@elopstudio/ai-wave-mcpnpmAI Wave works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.