MCP server for SAP UI5/OpenUI5 development: API reference, version info, development guidelines and linting.
Five tools with complete schemas, descriptions, and proper naming. All tools follow verb_noun convention (list_, search_, get_, run_). Descriptions are substantive (100-200 chars typical). Input schemas are well-formed with types, enums, and constraints. However, output schemas are not documented, LLMs cannot see what fields to expect from responses. Error handling is minimal; tools lack recovery guidance. No tool annotations (readOnlyHint, destructiveHint). Parameter descriptions are good but could be more prescriptive about formats and constraints.
Return a class summary for a fully qualified UI5 symbol (for example sap.m.Button): description, extends, key properties, aggregations, events, and public methods, parsed from the library api.json.
Return curated UI5 development guidelines authored by Logali covering async module loading, MVC structure, data binding and OData, i18n, CSP compliance, responsive design, and testing. Pass a topic to return a single section.
List available SAP UI5/OpenUI5 versions with support status, long term maintenance flag, and end of maintenance dates, read from the SDK version overview.
Run the official UI5 linter (@ui5/linter) against a local UI5 project directory via npx and return the report. Requires a valid UI5 project (a ui5.yaml and network access to fetch the linter on first use). Degrades gracefully when the linter cannot run.
Search control, class, and namespace names across the common UI5 libraries (sap.m, sap.ui.core, sap.f, sap.ui.table, sap.ui.layout, sap.ui.comp, sap.uxap). Returns matching symbols with their kind, owning library, and a short description.
Output schemas not documented. LLMs cannot see what fields list_versions, search_api, get_api_reference, get_guidelines, and run_linter return. This forces LLMs to guess at response structure and risks failed downstream tool calls.
No tool annotations. Tools lack readOnlyHint, destructiveHint, or idempotentHint. run_linter executes external code (npx @ui5/linter), should be marked with destructiveHint or at minimum documented as having side effects (disk I/O, network access).
Error handling lacks recovery guidance. run_linter can fail if ui5.yaml is missing or linter cannot run. Error messages should guide the LLM: 'ui5.yaml not found. Ensure the project is a valid UI5 project with a ui5.yaml in the root.'
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 65 | 2025-06-18+ | v2 |
get_guidelines topic parameter lacks enum constraint. Description lists 'Known topics: async-loading, mvc, data-binding, i18n, csp, responsive, testing' as free text. Should be an enum to prevent hallucinated topic names.
search_api limit parameter defaults to 40 but max is 100. No guidance on when to use higher limits or how pagination works. If results exceed limit, does the tool return a next_cursor or offset for pagination?