abap2UI5 MCP Server
OfficialRelated Servers
Alternatives to abap2UI5 MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI coding agents to read, review, and test ABAP code stored as abapGit files without an SAP system. Agents can list and outline objects, check Clean ABAP conventions, run full static analysis, and execute ABAP Unit tests locally on a laptop.5MIT
- AlicenseNot gradedqualityAmaintenanceEquips agentic AI tools with UI5-specific capabilities such as scaffolding new UI5 applications and integration cards, retrieving API references, guidelines, and version info, and validating manifests or running linters to detect and fix UI5 coding issues. It gives AI assistants the context and tooling needed to build and maintain UI5 projects more reliably.511 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables agentic AI tools to scaffold UI5 applications, detect and fix UI5-specific code issues, fetch API references and guidelines, validate manifests, and run linters.511 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables agentic AI tools to scaffold UI5 applications and integration cards, fetch API documentation, validate manifests, run UI5 linter, and apply UI5 development guidelines.511 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables agentic AI tools to scaffold new UI5 applications and integration cards, look up UI5 API references and development guidelines, and validate manifests and lint code to detect and fix UI5-specific errors.511 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to read, write, activate, and transport ABAP code in SAP systems via ABAP ADT REST API, without needing SAP GUI.24576 npmMIT
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: capabilities and scope_of differ (abap2UI5 feature map vs. UI5 control entity verdicts), validate_view/deploy_app/run_app form a sequential loop, and backend/build_backend/run_app/remove_app manage separate aspects of the dev environment. No two tools appear to do the same thing.
The action tools mostly follow verb_noun (deploy_app, validate_view, build_backend, run_app, remove_app), but the knowledge/management tools use noun-style names (capabilities, generation_rules, scope_of, backend). All are snake_case and readable, but the pattern is not consistent throughout.
Nine tools is well-scoped for an MCP server focused on abap2UI5 development. Each tool earns its place in the workflow, from capability lookup and rule reading to validation, deployment, backend management, and cleanup.
The tool set covers the full development lifecycle: understand what's possible (capabilities, generation_rules, scope_of), validate (validate_view), deploy (deploy_app), build and run (build_backend, run_app, backend), and remove (remove_app). No obvious dead ends or missing critical operations.