Tokencost Dev vs Truthroute
A side-by-side look at the Tokencost Dev and Truthroute MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Tokencost Dev for conversational ai work as a local process; choose Truthroute 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 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.
Choose Truthroute when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 60/100 · Good | 43/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 | None listed | OPENAI_API_KEYANTHROPIC_API_KEYGEMINI_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Tokencost Dev | View Truthroute |
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.
Truthroute 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"
]
}
}
}
Truthroute
{
"mcpServers": {
"truthroute": {
"command": "npx",
"args": [
"-y",
"truthroute-cli"
],
"env": {
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Tokencost Dev is categorized under Conversational AI and uses a local stdio subprocess. Truthroute belongs to Conversational AI and uses a local stdio subprocess. Pick Tokencost Dev for conversational ai work and Truthroute 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.
Tokencost Dev has no declared pricing — check the project's own site. Truthroute 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 truthroute 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. Truthroute has 43/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.