UI5 MCP Server vs Un Sdg — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
UI5 MCP Server vs Un Sdg
In-depth architectural comparison of the UI5 MCP Server and Un Sdg 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: 59/100 (Good) | Auth: No auth required
Un Sdg
Developer Tools · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose UI5 MCP Server if you need specialized Developer Tools tools running via a local process. Choose Un Sdg 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, Un Sdg belongs to Developer Tools using local stdio subprocess. Select UI5 MCP Server when you need capabilities focused on developer tools and Un Sdg when you require tools for developer tools.
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.
Un Sdg Tools (5)
list_goals
List the 17 UN Sustainable Development Goals (code, title, description). Optionally drill into one goal to get its targets and indicators.
list_indicators
The queryable catalog of SDG indicators. Each indicator (e.g. "1.1.1") nests its data series with their series codes (e.g. "SI_POV_DAY1"). Use a series code as seriesCode in get_series_data.
list_series
Flat list of all SDG data series (series code + description + goal/target/indicator it belongs to). Series codes are what you pass to get_series_data. Use this when you want the raw series list rather than the indicator-nested view from list_indicators.
list_geoareas
List geographic areas with their M49 area codes (e.g. 1 = World, 4 = Afghanistan, 8 = Albania). Pass an M49 code as areaCode in get_series_data.
get_series_data
Get observations for an SDG series in a geographic area over a time range. seriesCode comes from list_indicators/list_series; areaCode is an M49 code from list_geoareas. Returns { data: [...] } where each observation has value, timePeriodStart, geoAreaName, source, footnotes, etc.