Everything in the atlas
Type
Domain: 2
Origin: 2
Signals
More
Group by: Capability
MCP server for the abap2UI5 check, deploy and run loop
Every gate here runs off-system, so what the class does on a real system and what the view does on the oldest UI5 release it has to serve are what the `pitfalls` catalogues carry and no local run can see. It runs abap2UI5 app classes, so ABAP that is not one has nothing here to deploy into. In system mode the sandbox tools are not offered, and an `app_act` event runs on the system as the configured user.
MCP server for CAP development: model and docs search
The tools are documented as meant for AI models and not a stable API, so anything built to parse `cds-mcp` output rather than to feed a model can break between releases. Its corpus is the CAP documentation, so Fiori elements, BTP service or ABAP questions are not in what `search_docs` indexes.
MCP server for creating and editing Fiori applications
MCP server with five tools for Mobile Development Kit work
It expects a real landscape, not just a project: a `.service.metadata` file naming the Mobile Services app, endpoint and destination, the Cloud Foundry CLI, and access to a BTP Cloud Foundry environment. From 0.4.0 macOS support is ARM64 only — Intel Macs are not supported — alongside Linux and Windows on x64 and ARM64.
MCP server for UI5 development with ten tools
It reads a UI5 project and the framework's own documentation, not a running system or a backend: a question about the service behind the app is answered somewhere else. Node.js v20.17 or v22.9 and above.
SAP's ABAP tools in VS Code for editing, debugging, ATC and transports
Local HTTP MCP server started from ABAP Development Tools for VS Code
There is nothing to install and nothing to deploy, and equally nothing to run headless: in VS Code it exists only while ADT for VS Code is running with a logged-on ABAP project, so it is a developer's local surface rather than anything a pipeline or a hosted agent can reach. No public repository, so what it exposes is what the documentation says it exposes.
SAP's AI for ABAP development in ADT for Eclipse and VS Code
Exercises building a Fiori elements app from Figma via MCP servers
TechEd 2025 workshop driving a Fiori elements app from Figma via MCP
UI5con tutorial on Fiori elements apps with AI assistants and MCP
TechEd 2025 workshop on a Fiori app with ABAP Cloud and Joule
Fiori Innovation Day exercises on Fiori elements with MCP servers
MCP server for the abap2UI5 check, deploy and run loop
Every gate here runs off-system, so what the class does on a real system and what the view does on the oldest UI5 release it has to serve are what the `pitfalls` catalogues carry and no local run can see. It runs abap2UI5 app classes, so ABAP that is not one has nothing here to deploy into. In system mode the sandbox tools are not offered, and an `app_act` event runs on the system as the configured user.
VS Code extension to preview, activate and lint abap2UI5 apps
The embedded preview needs a system that accepts basic auth: the documentation states that pure SSO or SAML without a basic-auth fallback is not supported, and points at `external` mode, which opens the app in the normal browser with the existing SAP session. On the web only the language half runs; the preview with its proxy, traffic log and screenshot, Ctrl+F3 activation, the render gate, the workspace-wide check and the MCP servers are desktop-only. The agent app tools send nothing until `abap2ui5.agent.enableAppTools` is switched on in User settings, because an event they fire runs as the configured user and changes data on the system for real.
SAP-hosted MCP endpoint for BTP account administration
It acts on a real account. Authorisation is the caller's own — single sign-on through the SAP Default Identity Provider, across the global accounts that identity reaches — so what it can change is what you can change, and an agent invoking it is doing administration rather than proposing it. No public source, so what it exposes is what the documentation says it exposes.
Hosted MCP endpoint onto an SAP LeanIX instance
This is enterprise-architecture data, not a development surface — it answers what your landscape contains, never what your code does, and nothing in it belongs in a build. Entered here because it is a first-party SAP MCP endpoint and the catalogue that tracks this corner lists it; the atlas maps SAP development, so treat it as adjacent rather than as tooling for a project.
Claude Code plugin registering hana-cli's MCP server
Developer-centric command line for SAP HANA
Agent skills for CAP development, each a SKILL.md with references
TechEd 2025 session on benchmarking and optimising prompts
VS Code extension to preview, activate and lint abap2UI5 apps
The embedded preview needs a system that accepts basic auth: the documentation states that pure SSO or SAML without a basic-auth fallback is not supported, and points at `external` mode, which opens the app in the normal browser with the existing SAP session. On the web only the language half runs; the preview with its proxy, traffic log and screenshot, Ctrl+F3 activation, the render gate, the workspace-wide check and the MCP servers are desktop-only. The agent app tools send nothing until `abap2ui5.agent.enableAppTools` is switched on in User settings, because an event they fire runs as the configured user and changes data on the system for real.
Four agent skills for SAP AI Core in SAP's AI Skills Library
Agent skills for CAP development, each a SKILL.md with references
Hosted MCP server of developers.sap.com tutorials and missions
Agent skill built from the Fiori Design Guidelines
Agent skill mapping Fiori iOS UI Kit nodes in Figma to SwiftUI
Claude Code plugin with skills migrating HTML5 apps to appFront
Skills for building an A2A agent for Joule and deploying it to CF
Skills that generate commands are not the commands: everything here still runs against a real BTP account with real entitlements, and the deployment path assumed is Cloud Foundry, with `cf login` and `joule login` done before the toolkit is used. Three of the four skills are CLI knowledge rather than anything Joule-specific, which is worth knowing if you only wanted the agent part.
CLI adding SAP developer knowledge and MCP servers to AI coding tools
Agent skill mapping the developers.sap.com content API
Eight skills for writing and operating SAP Automation Pilot content
It works against a tenant, through the REST API, with credentials in the environment — so these skills act rather than advise, and the review skill is a check on generated content rather than a substitute for one. Nothing here is useful without an Automation Pilot tenant to point at.
Claude Code plugin with two skills for SAP LeanIX scripting
Enterprise-architecture work, not development: this describes what your landscape records, never what your code does. And the skills assume the server — without [the LeanIX MCP server](artifact:sap-leanix-mcp-server) reachable against your instance, they are instructions with nothing to call.
Agent plugin on the SAP Design System and theming parameters
Knowledge about theming, not a theme build: nothing here compiles a theme or deploys one, and it says nothing about a custom control's own parameters.
Two agent skills for accessibility and styling of web components
Two skills, narrowly scoped: nothing here scaffolds an application or answers what a component's API is — that is [@ui5/webcomponents-mcp-server](artifact:ui5-webcomponents-mcp-server), which reads the same library's documentation.
UI5 plugins for coding agents
Guidance, not access: these are instructions handed to an agent, and what the agent can then read of your project comes from [@ui5/mcp-server](artifact:ui5-mcp-server) or the editor. A modernisation workflow that runs autonomously across a codebase is also a thing to point at a branch rather than at main.
Starter repository for an abap2UI5 app with CI and agent setup
Financial Risk Analyzer built by an agent grounded in SAP MCP servers
CDS plugin for building agents inside a CAP service
Not as a gateway or proxy for SAP Application APIs: capire's guide states that CAP-level agents are intended only for exposing custom CAP application services and are not an SAP-endorsed architecture or pathway for agentic access to those APIs, and sends the reader to the SAP Architecture Center for the endorsed routes. Not as the screen a user of the application talks to, either — the chat preview in the generic index.html page is marked experimental and for local development.
CLI for Joule digital assistants and Joule Studio solutions
Pro-code CLI for building and deploying Joule Studio solutions
A2A adapter turning a CAP Java service into an LLM-backed agent
SAP's managed environment for building custom agents and workflows
Low-code SAP Build capability for custom Joule skills and agents
SAP's AI engagement layer across SAP applications
Cross-cloud A2A demo of agents settling a shipment dispute
Two runnable industry AI agent projects built around Joule
A2A reference letting Joule delegate to a CAP pro-code agent
Procurement decision support cross-validating two AI agent strategies
CodeJam on code-based AI agents in Python or TypeScript on SAP BTP
Recruiting agent on SmartRecruiters data flagging stalled candidates
Hands-on building an AI agent with the SAP Cloud SDK for AI
TechEd 2025 lab building a Joule Agent for Global Track and Trace
TechEd 2025 hands-on on a Joule Studio agent collaborating over A2A
CAP travel-booking app built on xflights master data
SAP's workspace for conversations, Spaces and directing agents
Orchestration Service client for templating, grounding and masking
AI runtime on BTP with the Generative AI Hub
CAP samples comparing SAP AI Core responses with content filtering
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Sample implementations for AI-powered applications on SAP BTP
Orchestration Service client for templating, grounding and masking
AI runtime on BTP with the Generative AI Hub
CAP samples generating email through SAP AI Core with anonymization
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Sample implementations for AI-powered applications on SAP BTP
Extracts header fields and line items from business documents
CAP app validating invoices with Document Information Extraction
Value-help recommendations and SAP AI Core as a CAP service
AI Core control plane API surface of SAP's AI SDK
Shared internals of SAP's AI SDK
Client for foundation models via SAP AI Core and Generative AI Hub
Orchestration Service client for templating, grounding and masking
Client for prompts kept in SAP's prompt registry
SAP's UI elements as standard custom elements
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
SAP reuse library for calling large language models from ABAP
ABAP-native MCP endpoint that drives opted-in abap2UI5 apps
Stateful apps cannot be operated: a stateful session lives in one HTTP request and an MCP call is one request, so `app_start` refuses them. The repository carries no release yet and states the addon has not been run in production use, the 7.02 downport is lint-only with no 7.02 system having run it, and the ABAP Cloud HTTP service setup is written down but still to verify on your own system.
Bridge from CAP Java to SAP AI Core, with Fiori field recommendations
AI runtime on BTP with the Generative AI Hub
CodeJam on LLM-backed integration flows and MCP via API Management
Sample apps for SAP AI Core's Generative AI Hub capabilities
Setup guide and Python notebooks for SAP AI Core's Generative AI Hub
CAP samples calling SAP AI Core through the SAP Cloud SDK for AI
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Sample implementations for AI-powered applications on SAP BTP
CAP reference app for GenAI email support with RAG on HANA Cloud
Financial Risk Analyzer built by an agent grounded in SAP MCP servers
CodeJam on a CAP job posting service using SAP AI Core over OData
CodeJam on code-based AI agents in Python or TypeScript on SAP BTP
CodeJam deploying an LLM on Generative AI Hub and building RAG
Hands-on building an AI agent with the SAP Cloud SDK for AI
TechEd 2025 material on two SAP Databricks scenarios in BDC
UI5 workshop adding Chrome's on-device AI APIs to a TypeScript app
ML models that classify records and predict attributes
Machine learning recommendations over browsing history via REST
Tutorial notebooks and templates for a first SAP AI Core project
ML service on SAP AI Core scoring restaurant-inspection violations
FastAPI backend for SAP-RPT-1.5 predictions from SAP Analytics Cloud
SQL examples for the HANA APL APIs plus scoring runtimes
Code examples for predictive and ML scenarios on SAP HANA
Bruno collections and code for SAP-RPT predictions on tabular data
CodeJam on a first machine learning workflow in SAP HANA Cloud
TechEd 2023 session on SAP HANA features over HDI
TechEd 2025 workshop on SAP HANA Cloud's AI capabilities
TechEd 2025 material on two SAP Databricks scenarios in BDC
Orchestration Service client for templating, grounding and masking
Client for prompts kept in SAP's prompt registry
AI runtime on BTP with the Generative AI Hub
CAP samples using SAP AI Core's Prompt Registry for templates
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples filling a prompt template sent to SAP AI Core
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Sample implementations for AI-powered applications on SAP BTP
Value-help recommendations and SAP AI Core as a CAP service
CAP Node.js runtime
AI runtime on BTP with the Generative AI Hub
Managed SAP HANA database service on BTP
Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.
CAP samples embedding CSV rows into the SAP HANA Cloud vector store
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples running RAG similarity queries over SAP HANA Cloud vectors
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Sample implementations for AI-powered applications on SAP BTP
Workshop on HANA Cloud vector engine, Generative AI Hub and LangChain
CAP reference app for GenAI email support with RAG on HANA Cloud
CAP sample for semantic search with Generative AI Hub and HANA Cloud
CodeJam deploying an LLM on Generative AI Hub and building RAG
TechEd 2025 workshop on SAP HANA Cloud's AI capabilities
API proxies with security and traffic policies and Developer Hub
SAP's visual language and templates for BTP solution diagrams
Source repository of SAP's reference architectures
SAP's Eclipse plugins for ABAP development over ADT
It is an Eclipse install. A development object that is not native-integrated in Eclipse opens in the SAP GUI that is installed locally with the client.