PersonIndependent
Wouter Lemaire
GitHub@lemaiwolast push
Capabilities
Provides
Account provisioningBTPAccount provisioningSetting up cloud accounts, their organisational structure, resource entitlements, subscriptions and access assignments so the setup can be repeated from code. [Deployment](capability:deployment) puts an application onto a runtime that this account structure makes available.Agent access to your systemsBTPABAPCAPAgent access to your systemsGiving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. [Serving your application over MCP](capability:mcp-servers) exposes your own service contract; system access reaches the systems behind it, and one implementation may do both. Development assistance belongs to [agent access to your code](capability:agent-code-access).Agent guidanceCAPUI5BTPABAPAgent guidancePackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.Agent toolingCAPBTPAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.Architecture diagramsBTPArchitecture diagramsDrawing the architecture and components of a solution so another person can understand their responsibilities and connections. Shared notation makes diagrams readable across teams.Build and dev-server toolingUI5Build and dev-server toolingServing an app locally and building it for deployment — proxying a backend, transpiling, bundling, and shaping the result for whatever will host it.Custom controls and librariesUI5Custom controls and librariesExtending the set of controls an app is built from: a control of its own, a wrapper around a third-party widget, or an icon font registered with the framework, packaged so another app can reuse it. Distinct from [Web Components interop](capability:ui5-web-components), which brings in standard custom elements, and from [generators](capability:generators), which scaffold a control project rather than being one.GeneratorsCAPABAPUI5GeneratorsGetting from nothing to a project that runs, and from a project that runs to one that has the piece you just decided you need. Two different moments: the first is a one-time decision about layout, the second recurs for the life of the project.Importing and exporting table dataABAPUI5CAPImporting and exporting table dataGetting a file somebody supplies, a spreadsheet, a CSV or a JSON dump, into tables with its columns mapped and its values checked, and getting table content back out as a file. Data shipped with an application for development and demonstration is [seed data](capability:seed-data).LLM integrationCAPUI5BTPABAPLLM integrationCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.Server-side renderingCAPUI5Server-side renderingRendering a UI on the server before it reaches the browser — first paint without waiting for a client framework to boot, and markup a crawler can read.TypeScript patternsCAPTypeScript patternsHow an application is arranged once it is written in TypeScript — where handlers live, what registers them, and how business logic is kept apart from persistence. Distinct from typing, which is about the model being visible to the compiler; this is about the shape of the code around it.
Demonstrates
Agent toolingCAPBTPAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.Database connectorsCAPBTPABAPDatabase connectorsConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).LLM integrationCAPUI5BTPABAPLLM integrationCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.Web Components interopUI5Web Components interopUsing standards-based custom elements inside an app, and the question of which control set an app should be built from at all, two concerns that are often answered as one.
Contributes to
Agent access to your codeCAPABAPUI5BTPAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.Integrated frontend dev serverCAPUI5Integrated frontend dev serverServing a frontend and its backend services together during development, so they can be reached through one local origin. Serving prebuilt files and integrating a frontend toolchain that assembles resources on demand are different requirements.TypeScript supportUI5TypeScript supportWriting apps and libraries in TypeScript — the type definitions, the module syntax the loader expects, and the build step that gets from one to the other.
Entries
Group by39 of 39 entries
EntrySignals
Maintains
AI Core MCP ServerAI Core MCP ServerAn MCP server that exposes SAP AI Core's APIs as tools, defined entirely in one JSON config file for a proxy, so deployments, configurations and scenarios are managed through an assistant.independent, btp
Configuration over an API you must already have entitled and provisioned; and the smallest of these repositories, so what it covers is what its config file happens to name.
SAP AI Core APIs as MCP tools from one JSON config file
BTP CF MCP ServerBTP CF MCP ServerThe Cloud Foundry V3 API on SAP BTP as MCP tools — apps, orgs, spaces, services, routes and quotas — declared in one JSON config file and run by odata-mcp-proxy.independent, btp
It administers a live Cloud Foundry landscape: `Apps`, `Organizations`, `Spaces`, `ServiceInstances` and `SecurityGroups` all carry create, update and delete alongside list and get. What a caller can reach is set by the role they hold, and the three templates in `xs-security.json` are MCPViewer for read, MCPEditor for read and write, and MCPAdmin for full administrative access.
Cloud Foundry V3 API on SAP BTP as MCP tools
BTP MCP ServerBTP MCP ServerBTP Core Services as MCP tools, and the only server in this corner that renders dashboards inside the chat — a subaccount overview with drill-down, a geomap of data-centre locations, consumption and users.independent, btp
It administers a real account through Core Services, so what it can change is what the caller can change. And the UI half depends on hosts that render mcp-ui or MCP Apps resources; elsewhere those five tools return markup nobody displays.
BTP Core Services as MCP tools with in-chat dashboards
btp-sap-odata-to-mcp-serverbtp-sap-odata-to-mcp-serverExposes every OData service on an S/4HANA or ECC system as MCP tools, in three discovery levels so a large catalogue does not have to be loaded at once.independent, btp
It puts create, update and delete on business entities behind natural language. Whatever the destination's principal may change, an agent may change — and "create a new customer" is a sentence, not a form somebody signed off.
Exposes S/4HANA or ECC OData services as MCP tools
btp-solution-diagram-generatorbtp-solution-diagram-generatorA Claude plugin that writes BTP solution diagrams as .drawio files in the style of the SAP BTP Solution Diagram Guidelines.independent, btp
Claude plugin writing BTP solution diagrams as .drawio files
cap-agent-ui5-webuicap-agent-ui5-webuiGives a CAP agent a UI5 web interface out of the box, so an agent built in the service has somewhere to be talked to without a separate frontend project.independent, cap
Not where the agent is reached over anything other than A2A: the README states the plugin does not speak anything other than A2A as @cap-js/agents serves it. Not where an upgrade has to be uneventful either — it pins @cap-js/agents to exactly 0.9.1, calls that package pre-1.0 and days old at the time of writing, and says this plugin inherits that instability and to expect breakage on upgrade.
UI5 web interface for an agent built in a CAP service
cds-plugin-handlerscds-plugin-handlersA CAP plugin that structures handlers as one file per entity, in a folder per service, instead of one service implementation that keeps growing.independent, cap
One handler file per entity in CAP services
cds-spreadsheetimporter-plugincds-spreadsheetimporter-pluginA CAP plugin that adds an ImporterService accepting an uploaded Excel file, parses it on the server and writes its rows into the CDS entity named in the URL.community org, cap
Spreadsheet upload into a CDS entity, parsed on the server
CI MCP ServerCI MCP ServerAn MCP server that exposes SAP Cloud Integration's OData APIs as tools, defined entirely in one JSON config file, so an assistant works integration content, logs and configurations in natural language.independent, btp
A thin declaration over CPI's APIs: it reaches what those APIs expose and nothing else, and it inherits whatever the tenant's own authorisations allow.
SAP Cloud Integration OData APIs as MCP tools
generator-ui5-ts-app-fclgenerator-ui5-ts-app-fclA generator that scaffolds a UI5 TypeScript application built around the FlexibleColumnLayout and bound to an OData service, asking for the endpoint, entity set, key and fields to show.community org, ui5
Generator for a TypeScript UI5 FlexibleColumnLayout app on OData
generator-ui5-ts-librarygenerator-ui5-ts-libraryA Yeoman generator, built on the official UI5 tooling, that scaffolds a new UI5 library in TypeScript as a plug-in for Easy-UI5.community org, ui5
Easy-UI5 generator scaffolding a TypeScript UI5 library
odata-mcp-proxyodata-mcp-proxyA config-driven proxy that turns OData and REST endpoints into MCP tools from a JSON file — no code — and runs on BTP Cloud Foundry against BTP Destinations.independent, btp
It fronts APIs you already have; nothing here reads a system's source or model, and a config file is only as good as the entity sets somebody wrote into it. OData V2 is the query surface it names.
Config-driven proxy turning OData and REST endpoints into MCP tools
ui5-cap-ai-featuresui5-cap-ai-featuresBoth halves of an AI text feature in one package: a CDS plugin serving an AIService over SAP AI Core's Orchestration Service, and the be.wl.ai UI5 control library that calls exactly that service.independent, cap
It is text processing, not an agent: there is no tool calling, no retrieval and no conversation. It needs SAP AI Core, and the backend half needs [@sap-ai-sdk/orchestration](artifact:sap-ai-sdk-orchestration) installed alongside it — an optional peer, so a frontend-only install stays lean.
CDS plugin and UI5 controls for AI text features via SAP AI Core
ui5-cap-serverside-rendering-pluginui5-cap-serverside-rendering-pluginA CAP plugin that fills UI5 views and fragments with entity data on the server through Handlebars and streams them as XML, and renders a Vue app to HTML on a route of its own.independent, cap
On the UI5 path what comes back is an XML view or fragment with the data already substituted, streamed as the entity's media content, rather than an HTML page — the README calls this pre-rendering, and only the Vue path produces markup. The view kept under `srv/` has its UI5 bindings replaced by Handlebars expressions, so it is a second copy of the view, separate from the one the application ships. Version 1.0.8 declares `@sap/cds` `>=8` as its peer dependency, which puts a project on CAP 7 outside its stated range.
CAP plugin rendering UI5 views with entity data on the server
ui5-control-generatorui5-control-generatorA command-line generator that writes UI5 custom controls, in JavaScript or TypeScript, from the html files in a project, with control logic and renderer split into two files by default.independent, ui5
Release and repository quiet for 29 months.
Command line generator of UI5 custom controls from html
ui5-middleware-route-proxyui5-middleware-route-proxyA UI5 server middleware that forwards requests matching a route prefix to a backend host, configured per route in ui5.yaml, with credentials read from a .env file rather than the yaml.independent, ui5
Release and repository quiet for 36 months.
UI5 server middleware proxying route prefixes to a backend
ui5-task-cachebuster-indexingui5-task-cachebuster-indexingA UI5 builder task that copies the build output into a timestamped folder inside dist so the UI5 cachebuster can resolve it; it supports timestamps only, not the hash mode.independent, ui5
Release and repository quiet for 66 months.
UI5 builder task preparing build output for the cachebuster
ui5-task-transpile-genui5-task-transpile-genA UI5 builder task that transpiles ES6 to ES5, including async/await, with Babel at build time, registered in ui5.yaml with a bundle definition that includes the regenerator runtime.independent, ui5
Release and repository quiet for 50 months.
UI5 builder task transpiling ES6 to ES5 with Babel
Maintains: samples, sketches and references
btp-agentbtp-agentOne LangGraph agent in a CAP service, with a UI5 chat screen in front of it and four odata-mcp-proxy MCP server modules behind it, deployed to Cloud Foundry as a single MTA.independent, cap
Neither the package manifest nor the repository tree declares a licence.
LangGraph agent and UI5 chat screen over four BTP MCP servers
btpvulnerabilityreportbtpvulnerabilityreportA CAP application that displays findings from the BTP Application Vulnerability Report, a working CAP and Fiori app running on HANA.independent, cap
Neither the package manifest nor the repository tree declares a licence.
CAP and Fiori app showing BTP Application Vulnerability Report data
cap-agent-ui5-webui-samplecap-agent-ui5-webui-sampleA worked example of the cap-agent-ui5-webui plugin, shown running locally, in hybrid mode against SAP AI Core, and deployed.independent, cap
Neither the package manifest nor the repository tree declares a licence.
Worked example of the cap-agent-ui5-webui plugin
ui5-ai-features-demoui5-ai-features-demoA product-review screen on CAP and SAPUI5 that consumes ui5-cap-ai-features and contains no library source at all — written to prove the package is enough on its own.independent, cap
Neither the package manifest nor the repository tree declares a licence.
Product-review screen consuming ui5-cap-ai-features on CAP
ui5-cap-serverside-rendering-demoui5-cap-serverside-rendering-demoThe demo project the ui5-cap-serverside-rendering-plugin README points to: a CAP bookshop whose Books list and detail views sit in srv/views and reach the browser already filled with data.independent, cap
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary As a deployment template it stops at the service: the `mta.yaml` has one module, `gen/srv` on the Node.js buildpack, and no HTML5 repository or router module for the app.
Demo CAP bookshop with server-rendered UI5 views
ui5-space-webcomponent-libraryui5-space-webcomponent-libraryA step-by-step UI5 library, be.wl.SpaceLibrary, that wraps the components of a UI5 Web Components package as UI5 controls through @ui5/tooling-webc, with a kitchen-sink page to test them.independent, ui5
UI5 library wrapping a UI5 Web Components package, step by step
ui5-space-webcomponent-packageui5-space-webcomponent-packageA step-by-step UI5 Web Components package, titled UI5con2023, with a SpaceComponent and a SpaceItemComponent written in TypeScript, which the matching UI5 library wraps as controls.independent, ui5
Step-by-step UI5 Web Components package in TypeScript
Contributes to
@ui5/tooling-webc@ui5/tooling-webcDeprecated UI5 Tooling extensions that generate UI5 library wrapper projects for UI5 Web Components and serve them during development; the README points to ui5-tooling-modules instead.sap official, ui5
The declared repository is archived.
Deprecated UI5 Tooling extensions for UI5 Web Components wrappers
arc-1arc-1An MCP server in front of the ADT REST API that runs locally and on Cloud Foundry with twelve tools that read, search, write, activate, lint and transport ABAP objects.independent, abap
MCP server over the ADT REST API for ABAP objects
cds-plugin-ui5cds-plugin-ui5A CDS plugin that runs the UI5 CLI express middlewares inside the CDS server, so a UI5 CLI project is served from the same port as the services, mounted under a path from its ui5.yaml.community org, cap
For a deployed application's UI. The README adds it with `npm add cds-plugin-ui5 -D`, a development dependency of the CDS server, and states nothing about a build or a deployment.
UI5 CLI middlewares running inside the CDS server
generator-ui5-appgenerator-ui5-appA Yeoman generator, built on the official UI5 tooling, that scaffolds a new UI5 application in one pass, run as a plug-in for Easy-UI5 or standalone, ready for npm start.community org, ui5
Easy-UI5 generator scaffolding a new UI5 application
generator-ui5-library-webcgenerator-ui5-library-webcA Yeoman generator that scaffolds a UI5 library wrapping UI5 Web Components on the official UI5 tooling, run through Easy-UI5 or standalone, and served afterwards with npm start.community org, ui5
No published releases; repository quiet for 35 months.
Yeoman generator for UI5 libraries wrapping UI5 Web Components
hacking-away-sampleapphacking-away-sampleappA UI5con 2022 demo app showing an end-to-end TypeScript setup for a UI5 application with a custom UI5 library, backed by a CAP service, in a pnpm monorepo with wdi5 tests.community org, ui5
UI5con 2022 demo of an end-to-end TypeScript UI5 setup with CAP
spreadsheetimporter/sample-full-btpspreadsheetimporter/sample-full-btpA CAP project with Risks and Mitigations, two Fiori elements apps and a Spreadsheet Upload button in the risks list report, packaged as an MTA for Cloud Foundry.community org, cap
CAP Risks and Mitigations project with a Spreadsheet Upload button
ui5-cc-spreadsheetimporterui5-cc-spreadsheetimporterA UI5 component that adds a spreadsheet upload dialog to a Fiori elements or freestyle app and submits the rows it reads through the app's own OData model.community org, ui5
UI5 component adding a spreadsheet upload dialog to Fiori apps
ui5-middleware-livereloadui5-middleware-livereloadA dev-server middleware that adds live reload to the UI5 dev server, reloading the page when the sources in the app's webapp folder change.community org, ui5
Live reload middleware for the UI5 dev server
ui5-middleware-simpleproxyui5-middleware-simpleproxyA UI5 dev-server middleware that proxies requests from the local dev server to a backend system, so the app can reach the backend's services during development.community org, ui5
Dev-server middleware proxying requests to a backend system
ui5-middleware-ui5ui5-middleware-ui5A UI5 middleware that lets one UI5 application be included as a dependency of another and served through that application's dev server.community org, ui5
UI5 middleware including one UI5 application in another
ui5-task-transpileui5-task-transpileA UI5 Tooling task that transpiles TypeScript, ES modules and other ES6+ sources during the build so the UI5 runtime can load them.community org, ui5
UI5 Tooling task transpiling TypeScript and ES modules
ui5-task-zipperui5-task-zipperA build task for the UI5 tooling that packages the UI5 build result, the webapp, as a zip archive at the end of the build.community org, ui5
Build task packaging the UI5 build result as a zip archive
ui5-tooling-modulesui5-tooling-modulesA set of UI5 tooling extensions that load and convert plain npm packages into UI5 AMD-like modules, so the UI5 module loader can consume them.community org, ui5
UI5 tooling extensions loading npm packages as UI5 modules
Writing and topics
12 of 12 pieces
Piece, what it offersStill applies
Building Code-Based AI Agents on the BAIPBuilding Code-Based AI Agents on the BAIPA Devtoberfest 2026 session on writing the agent yourself rather than configuring one, which is the agent tooling edge: an agent is a model with tools, skills, memory and context around it, and the session reads the code of one built in CAP as a LangGraph state graph, with an agent node that calls the model, a tools node holding the MCP clients, and the edge between them looping until no tool is needed. It then shows the shorter route, a CDS service annotated for the agent protocol with its instructions and skills in an agent.md file. SAP AI Core carries both, with the CAP service in front of it as middleware so the credentials never reach the browser, and that is what cap-agent-ui5-webui is demonstrated against: added as a dependency, it gives the annotated service a UI5 chat interface that can be deployed rather than only previewed. A Python multi-agent application on Cloud Foundry, where an orchestrator delegates to per-stack specialists so no single model sees every tool, closes the session.published 2026-10-09
UI5 AI Features library is now an npm PackageUI5 AI Features library is now an npm PackageThe release note for a demo turning into a dependency, and it is explicit about why that matters: the earlier version worked, but using it meant cloning the repo and copying both halves, which stops working the moment one of them changes. The post walks through what shipping the CAP plugin and the be.wl.ai control library in one npm version buys — a client and server contract that cannot drift — then lists the eleven controls by group, shows the two-line configuration that activates each half, and notes that this version is actually deployed on BTP behind both a standalone approuter and Work Zone. It closes on the demo repository, written with no library source in it as the test that the package stands alone.published 2026-08-31
UI5 AI Features library is now an npm Package
cds 8, line ended. Affects Runnable code.
Agentic AI on BTP: a Multi‑Agent App with Pydantic AIAgentic AI on BTP: a Multi‑Agent App with Pydantic AISplits a single CAP/TypeScript agent that had grown to juggle five BTP MCP servers behind one bloated tool list into btp-multiagent-app, a Python and Pydantic AI rewrite where the Cloud Foundry and BTP Core MCP servers each get a dedicated specialist agent, with an audit log specialist scaffolded but left disabled, behind an orchestrator whose only tools are delegation calls to those specialists, which is the agent-tooling pattern the piece works through. Each specialist authenticates to its MCP server over Streamable HTTP with OAuth 2.1, and a shared module centralises the SAP AI Core GenAI Hub model setup behind two credential layouts, one for local runs and one for the Cloud Foundry service binding, the LLM integration side of the rewrite. Tool lists per agent drop from well over a hundred to a dozen or two, and routing failures become separable from tool-misuse failures by reading the trace.published 2026-05-03
Agentic AI on BTP: a Single Agent with LangGraphAgentic AI on BTP: a Single Agent with LangGraphA CAP TypeScript agent puts a LangGraph StateGraph in front of AzureOpenAiChatClient from @sap-ai-sdk/langchain, reaching SAP AI Core's Generative AI Hub, and lets its tool-calling loop draw on five deployed MCP servers — OData MCP Proxy, CI MCP Server, AI Core MCP Server, BTP MCP Server and BTP CF MCP Server — through @langchain/mcp-adapters' MultiServerMCPClient. Because agent, servers and APIs share one XSUAA tenant, the chat service forwards the signed-in user's own JWT instead of a service account, so each downstream server enforces that user's own authorizations. Past roughly a hundred combined tools the single prompt slows down and stops separating concerns, which is why the author's next post splits it into one specialist agent per MCP server behind an orchestrator.published 2026-05-03
BTP Audit Log MCP Server: Security Monitoring with AI AssistantsBTP Audit Log MCP Server: Security Monitoring with AI AssistantsWouter Lemaire builds an MCP server over SAP BTP's Audit Log Retrieval API using odata-mcp-proxy, with a single entity set and zero custom code, so an AI assistant can answer natural-language questions like "Were there any configuration changes yesterday?" by calling AuditLogRecords_list against a BTP destination authenticated with the Audit Log service's service key. It covers the destination setup, the entity-set configuration that maps the PascalCase entity name to a lowercase auditlogrecords path, and handling the API's 500-record pagination limit.published 2026-03-13
BTP Cloud Foundry MCP Server: Managing CF Environments with AIBTP Cloud Foundry MCP Server: Managing CF Environments with AIWalks through a server built on odata-mcp-proxy that exposes the Cloud Foundry V3 API's 28 entity sets — apps, orgs, spaces, services, networking, quotas — as MCP tools from a JSON config with no application code. It shows the config shape that bridges the API's snake_case paths to PascalCase tool names via a urlPath field, and the OAuth2 client-credentials destination setup an assistant needs to reach a CF landscape.published 2026-03-13
UI for the BTP Application Vulnerability ReportUI for the BTP Application Vulnerability ReportAn open-source SAPUI5 front end for SAP's Application Vulnerability Report API, backed by a CAP Node.js service that projects the external findings as an OData V4 entity and forwards each query with api.run(req.query). The CAP service reaches that API through a Destination service instance configured with OAuth2ClientCredentials authentication from a service key, so the address and credentials stay out of the application code.published 2026-02-10
Consume ABAP RFC Function Modules in CAPConsume ABAP RFC Function Modules in CAPCalling an existing RFC function module from CAP instead of asking somebody to build an OData service for it — which is the actual decision, since the alternative is custom development on the ABAP side for a function that already works.published 2025-03-28
CAP multitenancy with Work ZoneCAP multitenancy with Work ZoneA gap in the tooling and the manual edit that closes it. cds add portal wires the Portal service, which is deprecated; Work Zone supports multitenancy but has no equivalent command. The author runs the portal command anyway and then rewrites the resource and module config in mta.yaml to point at Work Zone. Short, and honest that it is a workaround rather than a supported path.published 2025-03-14
Create your first CAP pluginCreate your first CAP pluginA step-by-step guide to the cds-plugin.js extension point: scaffold a package, add an index.cds for shared model artifacts, and test it locally against a throwaway CAP project before publishing to npm, with a separate section on building the same plugin in TypeScript and compiling it with tsc. Points to the author's own cds-plugin-handlers and ui5-cap-serverside-rendering-plugin as worked examples.published 2024-12-09
Upload attachments in a Freestyle UI5 and CAP appUpload attachments in a Freestyle UI5 and CAP appAttachments where the UI is freestyle rather than Fiori elements, so none of the generated upload behaviour applies and both ends have to be written.published 2023-12-19
How to add OData v2 adapter proxy to your CAP projectHow to add OData v2 adapter proxy to your CAP projectThe problem is stated in one line — a UI5 application that only speaks OData v2 in front of a CAP service that speaks v4 — and the answer is a proxy in the middle rather than a rewrite of either end. Written while v4 support in the UI5 stack was still patchy, which is the whole reason the adapter exists.published 2020-06-30
How to add OData v2 adapter proxy to your CAP project
OData changed in @cap-js-community/odata-v2-adapter 1.10.0, 2023-04-05. Affects Runnable code.
IN TOPICS
onedevatlas is open for browsing. Find tools for SAP development, compare their documented capabilities, ask your AI assistant, and join a flight during TechEd week.
Details
History
- BTP MCP ServerThe tag came in with the entry on 2026-09-10 and nothing sourced it: the README names BTP Core Services and the proxy it runs on, never CAP. It read as a routing leftover from when the MCP servers capability lived on the CAP door; the entry stays on BTP, its home.
- odata-mcp-proxyThe tag came in with the entry on 2026-09-10 and nothing sourced it: the README describes a config-driven proxy on BTP Cloud Foundry and names no CAP stack. Removed with its sibling configs; the entry stays on BTP, its home.
- btp-solution-diagram-generatorcapability:agent-guidance declared the installs_into property on the BTP door, and the README's Install section names both hosts in one sentence. Cowork is the second host no other entry behind this door names.
- btp-solution-diagram-generatorThe edge said the rules are packaged and not what the package holds, which is the thing that separates this option from the other three skill sets behind the door that carry the same guideline. The README's own list was read on 2026-10-15 and its three lines are now the edge's sources.
- cap-agent-ui5-webuiThe README has grown well past what the page carried, and the entry stated the capability with no source at all. Read on 2026-10-15: it serves a freestyle SAPUI5 TypeScript chat client same-origin from the CDS server against the services carrying @agent, renders a picker for more than one agent where switching starts a new conversation, speaks nothing but A2A as @cap-js/agents serves it, pins that package to exactly 0.9.1 and says to expect breakage on upgrade, and ships a scripted LLM because the bundled mock can never call an action and leaves an @agent.hitl gate unreachable. The dependency on @cap-js/agents is what the plugin is written against, so it is a required edge rather than a sentence.
- cds-plugin-handlersThe edge carried no sentence. It now says how the plugin decides where a handler goes, which is by folder and file name rather than by a decorator, and states the handler_binding and layers values of the capability's comparison, each on the README sentence it rests on. dependency_injection and draft_events are left unstated: the README mentions neither.
- ui5-cap-ai-featurescapability:llm-integration declared two comparison properties on 2026-10-15. The edge rested on the npm README's sentence about server-side prompts, which says where the prompts live and not which service the call goes to; the package README, read the same day, names SAP AI Core's Orchestration Service outright, which is what the property states. response_streaming is left absent: the README says nothing about streaming, and absent is not no.
- ui5-cap-ai-featuresThe edge read as an unconditional prerequisite while this entry's own when_not_to_use already said the package is an optional peer. The README states it in one sentence, quoted now: a frontend-only install does not need it and a backend project installs it explicitly, which is the distinction a reader deciding what to add to package.json needs. The edge to the HTML5 Application Repository is untouched; nothing was read for it in this pass.
- AI Core MCP ServerThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
- BTP CF MCP ServerThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
- BTP MCP ServerThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
- btp-sap-odata-to-mcp-serverThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
- CI MCP ServerThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
- odata-mcp-proxyThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
- BTP MCP ServerThe README lists create, update and delete on subaccounts and directories and entitlement assignment; the only edge was to the MCP-server capability, so the account-provisioning page did not list it.
- ui5-cap-serverside-rendering-pluginThe old line said the plugin renders UI5 applications. Its README and cds-plugin.js describe two narrower things: Handlebars substitution into a single view or fragment, served as an entity's media content, and a separate Vue route that renders HTML.
- ui5-cap-serverside-rendering-pluginThe entry carried a one-line index entry and nothing answering what it does, so the page opened on readings. The paragraph states where the views live, which aspect and annotations switch the behaviour on, what the handler returns, and that the Vue path is separate.
- ui5-cap-serverside-rendering-pluginWithout it the page left the reader to assume that server-side rendering here produces a page. It produces a data-filled UI5 XML view on the UI5 path, and the peer dependency puts CAP 7 out of range.
- ui5-cap-serverside-rendering-pluginThe author marks the Vue state handling as unfinished in the source, and vueConfig is a module-level object, so the shape of that half is worth stating for anyone reading it further.
- ui5-cap-serverside-rendering-pluginA bare ref said the plugin answers the capability without saying how. The object form carries the contribution and the files it was read from.
- BTP CF MCP ServerThe server required the Cloud Foundry runtime and the Destination service as two separate dependencies. The connection says how they relate: the calls go to the CF API and run through the destination.
- AI Core MCP ServerTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
- BTP MCP ServerTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
- btp-sap-odata-to-mcp-serverTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
- CI MCP ServerTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
- CI MCP ServerPlaced on integration, which is a classification in the schema enum and not a door — so its breadcrumb read INTEGRATION and linked to a page that 404s. Cloud Integration is an Integration Suite service and the Integration Suite is BTP, which is the reasoning the door list has carried since it was written.
- odata-mcp-proxyTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
- cap-agent-ui5-webuiPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- First entry seenDiscovered via sap-ai-mcp-servers, Added by hand, GitHub API, GitHub API · lemaiwo, npm registry, The discovery pass, The discovery pass · npm, SAP Community.
For your agent
- Ref
actor:lemaiwo- JSON
- /actors/lemaiwo.json
- MCP
- Connecting an agent