SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Starting point

SAP-samples/fiori-mcp-server-hands-on

A hands-on exercise set that builds and modifies an SAP Fiori elements app from a Figma design, using the MCP servers for SAP Fiori elements and for Figma with an AI coding assistant.

The exercises take a Figma design through Cline (in SAP Business Application Studio, against Anthropic's claude-4.5-sonnet) and the two MCP servers to create a CAP project and a Fiori elements list report app, then adjust its object page: enabling automatic data loading, adding a destination column and an analytical chart, adding a custom section built with the RichTextEditor building block, and adding an object page for booking details. A troubleshooting section walks through diagnosing failed prompts and MCP tool errors by source (CDS compiler, SQLite or browser console) and using the AI client's checkpoints to restore and retry a step.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Demonstrates
Agent access to your codeUI5Agent access to your codecapabilityLetting 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.

Who is behind it

SAP SamplesSAP SamplesOrganisationMaintains this
In the atlas: maintains 222
@SAP-samples
maintainerChristoph GollmickPersonContributes to this
In the atlas: contributes to 11, wrote 1
@cfg74
Katrin PolloczekPersonContributes to this
In the atlas: contributes to 1
@katrinpollo
Martin RippelPersonContributes to this
In the atlas: contributes to 1
@Martin-Rippel
vinayhospetePersonContributes to this
In the atlas: contributes to 15
@vinayhospete
4 contributors

What it declares

Every artifact

Type
Sample
Origin
By SAP

As a sample

Form
A tutorial's companion code

Connections1

SAP-samples/fiori-mcp-server-hands-on connectionsSAP-samples/fiori-mcp-server-hands-onPROVIDES→ demonstrates1demonstrates authoredAgent access to your code

README

quoted from SAP-samples/fiori-mcp-server-hands-on under Apache-2.0, read
SAP-samples/fiori-mcp-server-hands-on/README.mdOn GitHub

REUSE status

Hands-on | Create great UX with AI, SAP Design System, SAP Fiori elements, and SAPUI5

Overview

In this hands-on tutorial you will work through a set of exercises that highlight the benefits and capabilities of the SAP Design System, the Figma design tool, and the MCP servers by SAP and for Figma to create and modify SAP Fiori applications with the help of AI coding assistants.

You will gain comprehensive knowledge of AI assisted full-stack development, and learn how to use Figma and the SAP Design System to kickstart your SAP Fiori elements application development.

Using AI during App Development

We are using Cline as AI client within SAP Business Application Studio (SBAS) and Anthropic claude-4.5-sonnet LLM (Large Language Model) throughout the exercises. When developing SAP Fiori applications with LLMs, you may encounter situations where a prompt is not executed as intended, or technical errors occur when calling MCP server tools. Knowing how to approach these issues systematically can save time and prevent disruption. Cline and the choosen LLM are powerful assistants for problem resolution.

General steps in case of issues:

Detailed steps and examples of resolving common issues

  1. Verify connectivity:

    • Check if your machine has network access.
    • Confirm that the MCP server is up and running.
  2. Approach errors systematically

    • Pause before panicking
      • Use natural pauses when the client asks for approval to inspect the current results and chat history.
      • Stop execution with the "Cancel" button. You can always proceed from there with a new prompt
    • Identify the source: Check if the issue is:
      • CDS compiler error
      • SQLite/database error
      • Console/browser runtime error
  3. Using the LLM to solve an issue

    • The LLM occasionally makes mistakes, or forgets required steps leading to error situations
    • But the LLM can read the terminal output and react to API reponses, and correct error visible there
    • Other issues, like from browser console output, can be resolved by copy-pasting the full error message into the chat and ask for a fix in a prompt
    • LLM works best when exact messages are provided rather than manual descriptions.
  4. Use Restore Points if Needed

    • If a solution strategy does not work, you can always restore the files and chat to a previous checkpoint using Cline’s restore functionality.
  5. Don’t be afraid to retry an exercise or step after restoring to a checkpoint.

Exercises

Begin your exercises here. At the end of each section, there is a link to continue to the next section.

Contributing

If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.

License

Copyright (c) 2026 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.

Apache-2.0, read

Details

Sources3
GitHub organisations and accountsdiscovered herechecked
github.com/SAP-samples/fiori-mcp-server-hands-ontree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaGitHub organisations and accounts
first seen in the atlas
ecosystem and domainui5, ai-and-agents
Flavors1
Fiori elements
“to kickstart your SAP Fiori elements application development.” — SAP-samples/fiori-mcp-server-hands-on — READMEchecked
Contributors4

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-samples-fiori-mcp-server-hands-on
JSON
/artifacts/sap-samples-fiori-mcp-server-hands-on.json
MCP
Connecting an agent