SAP Datasphere MCP Server

A TypeScript Model Context Protocol (MCP) server that enables AI assistants like Claude and Cursor to interact with SAP Datasphere for data exploration, querying, and administration.

49 tools | 4 resources | 4 prompts | Mock data mode for instant development

Features

• Catalog & Discovery — List spaces, search assets, explore schemas

• Data Querying — Query views and analytic models with full OData V4 support ($select, $filter, $orderby, $top, $skip, $count)

• Space Management — Create, read, update, delete spaces

• Modeling Objects — Full CRUD for 14 object types (tables, views, analytic models, data flows, task chains, etc.)

• Connections — Manage and validate data connections

• User Management — SCIM 2.0 users + database users

• Role Management — Global roles and scoped roles with member/space assignment

• Task Execution — Run task chains, check logs, view execution history

• Repository — Browse repository objects and deployed objects with runtime metrics

• Audit — Export audit log entries

• Diagnostics — Test connectivity, check server health

Related MCP server: Infor Birst MCP Server

Quick Start

# Clone and install
git clone <this-repo>
cd mcp-datasphere-tools
npm install

# Configure credentials
cp .env.example .env
# Edit .env with your Datasphere OAuth credentials (see Configuration below)

# Build and run
npm run build
npm start

Configuration

1. Create OAuth Credentials

Create credentials via SAP Datasphere UI (not BTP service keys):

1. Log into SAP Datasphere

2. Go to System → Administration → App Integration

3. Create a new OAuth2.0 Client (Technical User)

4. Copy the Client ID, Client Secret, and Token URL

2. Configure .env

Copy .env.example to .env and fill in your credentials:

DATASPHERE_BASE_URL=https://<tenant-id>.eu30.hcs.cloud.sap
DATASPHERE_CLIENT_ID=<oauth-client-id>
DATASPHERE_CLIENT_SECRET=<oauth-client-secret>
DATASPHERE_TOKEN_URL=https://<tenant-id>.authentication.eu30.hana.ondemand.com/oauth/token
USE_MOCK_DATA=false
LOG_LEVEL=info
CACHE_TTL_SECONDS=300

Authentication uses client_credentials grant type — fully non-interactive, no browser login required.

Set USE_MOCK_DATA=true to explore all 49 tools without any SAP credentials.

Integration

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "sap-datasphere": {
      "command": "npx",
      "args": ["tsx", "/path/to/mcp-datasphere-tools/src/index.ts"]
    }
  }
}

Cursor IDE

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "sap-datasphere": {
      "command": "npx",
      "args": ["tsx", "src/index.ts"]
    }
  }
}

Tools Reference (49)

Architecture

MCP Client (Claude/Cursor)
  ↓ stdio
McpServer (49 tools, 4 resources, 4 prompts)
  ↓
Handler Classes (11, extend BaseHandler) → Zod validation → SQL sanitization
  ↓
API Clients (11 classes) → Mock mode → Cache → Real API
  ↓
DatasphereClient → OAuth 2.0 + CSRF → axios → SAP Datasphere APIs

Key patterns:

• Handler Classes: each domain has a handler extending BaseHandler with getTools() and handle()

• Dependency Injection: API clients passed via handler constructor, no globals

• Mock-First: all tools work without credentials via USE_MOCK_DATA=true

• Caching: TTL-based in-memory cache (catalog 5min, queries 2min)

• Type Safety: TypeScript + Zod runtime validation

Development

npm run dev       # Hot reload with tsx
npm run build     # Compile TypeScript
npm start         # Run production build
npm run inspect   # MCP Inspector UI

Supported Object Types (Modeling)

local-tables, remote-tables, views, analytic-models, data-flows, replication-flows, transformation-flows, task-chains, intelligent-lookups, er-models, data-access-controls, business-entities, fact-models, consumption-models

Reference

Inspired by MarioDeFelipe/sap-datasphere-mcp (Python, 48 tools). This TypeScript implementation provides a clean, type-safe, handler-based architecture with 49 tools.

License

ISC