Model Context Protocol server for SAP Datasphere — MCP SDK v2 / 2026-07-28 stateless spec, Streamable HTTP, per-asset capability discovery, and config-driven PII masking (fail-closed, audit-logged).
Listed on its own since 2026-09-25. Until then it was part of mariodefe-sap-datasphere-mcp, where its earlier checks remain.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"sap-datasphere-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# 🚀 SAP Datasphere MCP Server [](https://pypi.org/project/sap-datasphere-mcp/) [](https://www.npmjs.com/package/@mariodefe/sap-datasphere-mcp) [](https://www.python.org/downloads/) [](https://modelcontextprotocol.io/) [](https://opensource.org/licenses/MIT) [](https://pypi.org/project/sap-datasphere-mcp/) []() > **Production-ready Model Context Protocol (MCP) server that enables AI assistants to seamlessly interact with SAP Datasphere environments for real tenant data discovery, metadata exploration, analytics operations, ETL data extraction, database user management, data lineage analysis, and column-level data profiling — with built-in config-driven PII masking so sensitive fields never reach the LLM.** ## 📦 Which version do I install? | Package | MCP Python SDK | Status | |---|---|---| | **2.x** (current) | `mcp>=2.0,<3` | Active development. Implements the 2026-07-28 stateless spec. | | **1.x** | `mcp>=1.28,<2` | Maintenance only — security and critical fixes. | `pip install sap-datasphere-mcp` gives you 2.x. **The 2.x server is dual-era**: it answers both the modern `server/discover` handshake and the legacy `initialize` one, so 2025-era clients keep working without changes. Stay on 1.x only if your environment cannot install SDK 2.x: ```bash pip install 'sap-datasphere-mcp<2' ``` ## 🆕 What's New (v2.0.1 — MCP SDK v2 / stateless spec) - **Ported to MCP Python SDK 2.0.0** and the 2026-07-28 stateless specification. Handlers moved from the …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.