Tokencost Dev vs Tokeven Cost Advisor
A side-by-side look at the Tokencost Dev and Tokeven Cost Advisor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
Tokeven Cost AdvisorConversational AIPrice a Claude, GPT, Gemini or Grok call before you send it. Runs locally.37FairAuth: not declaredVerdict: choose Tokencost Dev for conversational ai work as a local process; choose Tokeven Cost Advisor for conversational ai. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Tokencost Dev when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_model_details, calculate_estimate, compare_models.
TChoose Tokeven Cost Advisor when
- You need dedicated capabilities in the Conversational AI domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Tokeven Cost Advisor | |
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 60/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | 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 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Tokencost Dev | View Tokeven Cost Advisor |
Tools & capabilities
Tokencost Dev tools 4
get_model_detailsLook up pricing, context window, and capabilities for an LLM model. Uses fuzzy matching so you don't need the exact model key.calculate_estimateEstimate the cost for a given number of input and output tokens on a specific model. Supports optional cached_tokens for prompt caching discounts.compare_modelsFilter and compare models by provider, minimum context window, or mode. Returns top 5 most cost-effective matches.refresh_pricesForce a re-fetch of pricing data from the LiteLLM registry. Use this if you suspect the cached data is stale.
Tokeven Cost Advisor 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.
Tokencost Dev
{
"mcpServers": {
"tokencost-dev": {
"command": "npx",
"args": [
"-y",
"tokencost-dev"
]
}
}
}
Tokeven Cost Advisor
No confirmed install command for Tokeven Cost Advisor yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Tokencost Dev is categorized under Conversational AI and uses a local stdio subprocess. Tokeven Cost Advisor belongs to Conversational AI and uses an install path we have not confirmed yet. Pick Tokencost Dev for conversational ai work and Tokeven Cost Advisor 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. Tokeven Cost Advisor has no confirmed install command yet — follow its own setup instructions.
Tokencost Dev has no declared pricing — check the project's own site. Tokeven Cost Advisor 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 tokencost-dev and tokeven-cost-advisor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tokencost Dev has a quality signal of 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Tokeven Cost Advisor has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.