Modelmeter vs Openrouter
A side-by-side look at the Modelmeter and Openrouter MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Modelmeter for conversational ai work over a hosted endpoint; choose Openrouter for conversational ai as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Modelmeter when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
estimate_cost, get_model, list_models.
Choose Openrouter when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_models, get_model, compare_models.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 56/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 7 | 3 |
| Full listing | View Modelmeter | View Openrouter |
Tools & capabilities
Modelmeter tools 7
estimate_costEstimate the USD cost of an LLM API call for a given model and token counts. Returns input/output/total cost, plus reseller markup vs. the upstream model when applicable.get_modelUnified card for one model in a single call: normalized pricing, capabilities (context window, vision, reasoning, tags), availability, reseller markup vs. upstream, and a price-history summary (launch vs. current price, percent change, last change date, all-time low/high).list_modelsList available models with their current pricing. Optionally filter by provider.get_price_historyHistorical pricing time-series for a model or provider. Each point is a dated snapshot of the per-Mtok rates.list_eventsThe changelog of record for the model layer: deprecations, price changes, launches, and the market events around them. Filter by severity to find what demands action: 'breaking' (model going away, ID changing), 'action_required' (price/rate-limit/context changes), 'informational' (releases, funding).check_model_dependenciesIs my stack okay? Check a list of model ids against the record: scheduled retirements with days-remaining countdowns and migration targets, past retirements, and other breaking/action-required changes. Id matching tolerates dots vs dashes, dated snapshot suffixes, and bare or provider-prefixed forms. Call this at startup or in CI with the models you depend on.list_deprecationsPer-model retirement rows from the record: which model dies when, with runway and migration target. Default shows scheduled (upcoming) retirements sorted by shutdown date.
Openrouter tools 3
list_modelsList LLMs from the OpenRouter catalog (~340 models across all major providers) with normalized $/1M-token pricing, context windows, and modality. Filter by search, free-only, minimum context, or modality (e.g. "image" for vision models). Sorted cheapest-first by completion price. Keyless.get_modelGet full details for one OpenRouter model by id — normalized $/1M pricing (prompt, completion, plus per-request/image/web-search costs), context window, modality, supported parameters, tokenizer, knowledge cutoff. e.g. id "anthropic/claude-sonnet-4.5". Keyless.compare_modelsSide-by-side comparison of pricing ($/1M tokens), context window, and modality for 2-5 OpenRouter models. Answers "is claude-sonnet-4.5 cheaper than gpt-4o". Keyless.
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.
Modelmeter
{
"mcpServers": {
"modelmeter": {
"url": "https://modelmeter.xyz/mcp"
}
}
}
Openrouter
{
"mcpServers": {
"openrouter": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-openrouter"
]
}
}
}
Frequently asked questions
Modelmeter is categorized under Conversational AI and uses a remote HTTP/SSE transport. Openrouter belongs to Conversational AI and uses a local stdio subprocess. Pick Modelmeter for conversational ai work and Openrouter for conversational ai.
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.
Modelmeter has no declared pricing — check the project's own site. Openrouter 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 modelmeter and openrouter as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Modelmeter has a quality signal of 56/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Openrouter has 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars.