MCP Cost Tracker Rout… vs UI5 MCP Server | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Cost Tracker Router vs UI5 MCP Server
In-depth architectural comparison of the MCP Cost Tracker Router and UI5 MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Cost Tracker Router
Developer Tools · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
UI5 MCP Server
Developer Tools · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Cost Tracker Router if you need specialized Developer Tools tools running via a local process. Choose UI5 MCP Server if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Cost Tracker Router when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Returns token totals and USD cost estimates for the current session. Read-only.
get_tool_costs
Returns per-tool cost breakdown for the session, sorted by cost descending. Read-only.
reset_session
Start a new cost-tracking session. Previous session data is retained in history.
record_usage
Record token usage for a tool call. Takes `tool_name`, `model` (optional), `input_tokens`, and `output_tokens`. Emits a budget warning notification if 80% of threshold is reached.
set_budget_alert
Set a budget threshold in USD (`threshold_usd`). Warns at 80% and 100% of the threshold. Use with `--enforce-budget` to block calls beyond the limit.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MCP Cost Tracker Router is categorized under Developer Tools and uses a local stdio subprocess. In contrast, UI5 MCP Server belongs to Developer Tools using local stdio subprocess. Select MCP Cost Tracker Router when you need capabilities focused on developer tools and UI5 MCP Server when you require tools for developer tools.
Heuristic model recommendation by task type. Takes `task_description` and optional `constraints.max_cost_usd`. Returns recommended model with reasoning and estimated cost.
check_routing_policy
Check whether a model is allowed for a given task type under the routing policy. Takes `task_type` and `model`.
get_spend_history
Query historical spend aggregated by `period` (`day`/`week`/`month`). Returns breakdown by model and tool. Read-only.
estimate_workflow_cost
Pre-run cost estimation for a multi-step workflow. Takes a `steps` array with `tool_name`, `estimated_input_tokens`, `estimated_output_tokens`, and optional `model`. Read-only.
export_spend_report
Generate a single-file HTML spend report with session breakdown, historical spend, model cost comparison, and budget status. Read-only.
export_budget_audit
Export the audit log of budget enforcement decisions. Accepts optional `from_date`, `to_date`, and `format` (`json`/`csv`). Read-only.
set_project
Create or update a project with an optional `budget_usd`. Takes `project_name`.
+3 more tools listed on main page
UI5 MCP Server Tools (10)
create_integration_card
Scaffolds a new UI Integration Card.
create_ui5_app
Scaffolds a new UI5 application based on a set of templates.
get_api_reference
Fetches and formats UI5 API documentation.
get_guidelines
Provides access to UI5 development best practices.
get_integration_cards_guidelines
Provides access to UI Integration Cards development best practices.
get_project_info
Extracts metadata and configuration from a UI5 project.
get_typescript_conversion_guidelines
Provides guidelines for converting UI5 applications and controls from JavaScript to TypeScript.
get_version_info
Retrieves version information for the UI5 framework.
run_manifest_validation
Validates the manifest against the UI5 Manifest schema.
run_ui5_linter
Integrates with [`@ui5/linter`](https://github.com/UI5/linter) to analyze and report issues in the UI5 code.