In-depth architectural comparison of the UI5 MCP Server and Muni Dev Cost 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
UI5 MCP Server
Developer Tools · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Muni Dev Cost
Developer Tools · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose UI5 MCP Server if you need specialized Developer Tools tools running via a local process. Choose Muni Dev Cost 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 UI5 MCP Server 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).
UI5 MCP Server is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Muni Dev Cost belongs to Developer Tools using local stdio subprocess. Select UI5 MCP Server when you need capabilities focused on developer tools and Muni Dev Cost when you require tools for developer tools.
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.
Muni Dev Cost Tools (14)
get_dev_costs
The aggregated municipal development cost for a jurisdiction (single-family home), split into water+sewer vs other impact, with a per-fee summary and an honest coverage label.
get_fee_breakdown
Every fee line by line, grouped (Water / Sewer / Transportation / Parks / Drainage), with the **per-meter-size schedule** and each source + effective date.
compare_jurisdictions
Rank 2–12 markets side by side for **site selection** — total, water+sewer split, the dollar/% spread and what it costs on a 100-unit project.
get_water_sewer_detail
Water & sewer connection cost **by meter size** (5/8" → 12") — the single biggest swing in a utility connection budget.
estimate_dev_cost
Whole-project fees (fees × units) with per-unit and extended line items, dev-type aware, explicit about exclusions.
list_jurisdictions
The full **coverage map** — every jurisdiction, its depth and data freshness, which publish a per-meter schedule, plus the benchmark states.
get_fee_schedule_source
The published **source document + per-fee provenance** (published vs estimated) behind a jurisdiction's number — defensible *trazabilidad* for a pro-forma.
get_cost_trend
The **real dated revision history** of a jurisdiction's headline fee (prior years + adopted future steps) with YoY delta and CAGR — never a projection.
compare_by_meter_size
One jurisdiction's water/sewer cost across **every published meter size**, ratioed to the 5/8" residential base.
estimate_by_units
Multifamily/mixed** fee estimate by LUE (units × LUE-per-unit) — the way cities actually bill MF, so it doesn't overstate fees.
get_total_dev_cost
The **grand total across every fee category** (water/sewer, transportation, parks, drainage, public-safety, other), bucketed — with honest $0 buckets where a city simply doesn't charge that category.
breakdown_by_fee_category
Every line item within **one** category (e.g. all of a city's parks fees) with per-meter detail — errors honestly if the city doesn't levy that category.