Searches the bundled documentation corpora for SAP Fiori elements, UI annotations, UI5 development, OPA5 testing, UI Integration Cards, TypeScript conversion, CAP (CDS) development and SAP BTP destinations. Use this before generating or modifying apps to ground answers in current best practices. Local, no network required.

Returns curated UI5 development best practices for a topic: general, views, bindings, routing, i18n, performance, security, testing.

Returns best practices for developing SAP UI Integration Cards (manifest-driven cards for SAP Build Work Zone).

Returns the step-by-step guideline for converting UI5 applications and controllers from JavaScript to TypeScript.

Scans a directory for existing SAP Fiori applications (Fiori elements V2/V4, freestyle, cards, adaptation projects) that can be modified. Returns app id, type, entity set, OData version and view files. Call this before modifying an app.

Lists SAP system connections available for OData calls (from env vars SAP_BASE_URL/SAP_USER/SAP_PASSWORD, SAP_SYSTEMS_JSON or the systems.json file). Use the returned system name with download_odata_service_metadata.

Downloads the $metadata EDMX document of an OData service (V2 or V4) and saves it as localService/metadata.xml (or a custom path). Provide serviceUrl directly, or a systemName from list_sap_systems plus servicePath, or a BTP destination (destination + optional servicePath). Returns a summary of entity sets and types.

Generates a new SAP Fiori elements application for an OData V2/V4 service, e.g. from RAP. Floorplans: 'list-report' (LR+ObjectPage, V4+V2), 'object-page' (form entry, V4), 'worklist' (V4+V2), 'analytical-list-page' (V2), 'overview-page' (V2). Provide metadataXmlPath (from download_odata_service_metadata) or metadataXml content, or just entitySet. Creates manifest.json, Component.js, index.html, i18n, ui5.yaml and package.json.

Generates a new SAP Fiori elements application inside an existing SAP CAP project (app/ folder), based on an entity of the project's CDS model. Reads the CDS model to resolve the main entity and its to-many associations, and wires the app to the CAP service.

Gets the list of supported modification functionalities for an existing SAP Fiori application: add_page, delete_page, add_controller_extension, enable_fcl, enable_initial_load, update_manifest. Workflow: list_functionality → get_functionality_details → execute_functionality.

Gets the required parameters and detailed information for a specific functionality before executing it.

Executes a modification on an existing SAP Fiori application: adds/deletes pages, adds controller extensions, enables FCL or initial load, or updates manifest.json properties.

Parses a local EDMX metadata.xml and returns entity sets, entity types, keys, associations and annotation targets.

Creates a new UI5 freestyle app from templates: 'basic' (single page), 'worklist' (searchable table + object page, OData V2), 'master-detail' (FCL, 2 columns), 'fcl' (Flexible Column Layout with column routing) or 'tabs' (IconTabBar page). Generates manifest.json, Component.js, views, controllers, i18n, index.html, ui5.yaml and package.json. Fails if the target folder already exists.

Creates a manifest-based UI Integration Card (List, Object, Table, Timeline, Analytical, Adaptive, Component, Calendar) with preview index.html. Fails if the target folder already exists.

Fetches and formats the UI5 API reference (properties, aggregations, events, methods with JSDoc) for a control such as 'sap.m.Table'. Source: official UI5 TypeScript type definitions (@openui5/ts-types-esm), cached locally after first use.

Extracts metadata and configuration from a UI5 or CAP project: app ids, framework version, libraries, views, controllers, models, routing, data sources and package scripts.

Retrieves UI5 framework version information: latest version from the CDN (sap-ui-version.json) plus the local project's configured version.

Validates the manifest against UI5 rules: sap.app id pattern, dataSources, model references, routing targets, view/i18n files on disk, card structure.

Analyzes JS/XML code of a UI5 app for common issues: deprecated APIs (jQuery.sap.*, sap.ui.getCore().byId), removed libraries, deprecated controls, missing controllers and missing i18n keys.

Performs fuzzy searches against names of definitions from the compiled CDS model of a CAP project: entities, views (projections), services, types, aspects, events, actions. CDS parses all .cds files into a unified model including relationships and annotations. Example: searchModel(projectPath, 'Books', 'entity').

Returns full details of one CDS definition: elements with types and annotations, associations (target, cardinality, on-condition), actions/functions, projections and includes.

Executes a CQN-like query against the CAP sample data (CSV files in db/data following CAP conventions). Supports column projection, a WHERE-like filter (and/or, eq/ne/gt/ge/lt/le, contains), order by, skip/limit. Example filter: 'stock gt 10 and price le 50'.

Lists the SAP BTP destinations available for OData calls: local destinations (env var SAP_DESTINATIONS_JSON / SAP_DESTINATIONS_FILE / SAP_DESTINATIONS_DIR) and, when configured, destinations of the BTP Destination Service (cloud). Secrets are redacted. Use the returned destination names with query_odata_data and download_odata_service_metadata.

Returns the details of one SAP BTP destination (local or from the BTP Destination Service): URL, authentication type, sap-client, custom headers and proxy type. Secrets are redacted. Useful to verify a destination before querying it with query_odata_data.

Executes an OData query (V2 or V4) against an entity set and returns the rows as JSON. Target: a BTP destination (destination + optional servicePath), a configured SAP system (systemName + servicePath from list_sap_systems), or a full serviceUrl. Supports $filter, $top, $skip, $select, $orderby, $expand and $count. This is the remote counterpart of query_cap_data.

Opens a browser for the one-time SAP BTP login of a destination and stores the refresh token it returns, so later calls renew themselves. Use it when a destination fails with an expired or missing refresh token. The destination must carry a serviceKeyPath. Signing in takes longer than an MCP client waits for a tool call, so this returns 'pending' with the URL once the browser is open: finish the login there and call it again for the same destination to collect the outcome. Set noBrowser to get the URL back instead, for a machine with no browser of its own.