An MCP Server over Datasphere and HANA — Hands-On

What you will learn

• State correctly that SAP does not ship a packaged Datasphere or HANA MCP server, and name the governed SAP alternative (Integration Suite's MCP Gateway)
• Choose among the three Integration Suite MCP Gateway source types (API, HTTP endpoint with OpenAPI, RFC) for a given Datasphere, HANA Cloud or S/4HANA requirement
• Design a composed MCP tool that respects the 50-tool-per-artifact limit and the Integration Cell runtime requirement
• Connect an MCP tool to Datasphere's OData Consumption API (three-legged OAuth 2.0, $select/$filter/$orderby/$top/$skip) or to HANA Cloud via hdbcli with a narrow, parametrised, read-only surface
• Explain how a calling user's identity does or does not survive to the backend depending on the chosen path, and what principal propagation changes
• Register a working MCP server as an MCP-capable BTP destination so a Joule Studio agent can use it

Module overview

Who this is for. “MCP & A2A for SAP Systems” taught you what MCP is. This module builds one: a governed MCP server that exposes SAP Datasphere and SAP HANA Cloud as tools an agent can call — the tool layer “Building an Analytics Agent with Joule Studio”'s analytics agent depends on. Read the first section before anything else: it corrects an assumption the module title could invite.

Prerequisites

• MCP & A2A for SAP Systems (protocol fundamentals)
• Working knowledge of OData v4 and OAuth 2.0
• Comfort with a HANA Cloud connection (hdbcli, or an equivalent client) and basic SQL
• Recommended alongside the analytics agent this server serves and access to a Datasphere or HANA Cloud trial for the exercises

Outcomes

• Correctly brief a client on what SAP does and does not ship for MCP over Datasphere/HANA, without overstating a community project as an SAP product.
• Choose and justify an Integration Suite MCP Gateway source type for a real requirement.
• Design one composed, well-described tool that stays inside the 50-tool limit and a narrow, parametrised query surface.
• State, per tool, which identity actually reaches the backend and whether that is acceptable for the data it touches.