cds-kb-mcp

A dataless MCP server that gives AI agents instant, ranked access to 7,355 SAP S/4HANA released CDS views via semantic search, business taxonomy, and on-demand definition retrieval.

TL;DR: No installation, no data download, no cloning required. The server is centrally hosted remotely. Just configure your MCP client to connect via supergateway using the provided URL — a fallback URL is available if the primary is unreachable. See Client Configuration.

Benchmark vs. raw file access: ~830× faster, ~94× cheaper in tokens, better top-3 relevance — full numbers in BENCHMARK.md.

Table of Contents

• What you get

• Prerequisites

• Client Configuration — The ONLY step needed to start using the MCP

• Tools Reference

• Architecture

Related MCP server: SAP ADT MCP Server

What you get

Prerequisites

Before configuring your client, ensure your local machine meets the following requirements:

1. Node.js: Must be installed (minimum version Node.js v18 or above). Verify by running node -v in your terminal.

2. Network Connectivity:

   • Outbound HTTPS access to the hosted server — primary: https://cds-kb-mcp-production.up.railway.app, fallback: https://cds-kb-mcp.cfapps.ap21.hana.ondemand.com

   • Access to registry.npmjs.org to fetch supergateway. If your machine is behind a corporate firewall/VPN/proxy that blocks npm registry downloads, you must use the global installation method (Option 2 below).

3. Compatible IDE: An IDE supporting MCP (e.g. Cursor, Claude Desktop, VS Code, Gemini IDE).

Client Configuration

Because the MCP server is hosted remotely, you do not need to clone this repository or install any local dependencies.

For any IDE that supports MCP via standard commands (Cursor, Claude Desktop, Gemini IDE), use the supergateway package to securely bridge the remote SSE server back into local stdio.

To ensure 100% stability across all devices (preventing version mismatch or Node.js v18 compatibility issues), use one of the two configurations below. Two hosted endpoints are available — start with Primary, and switch to Fallback only if the primary is unreachable from your network.

Option 1: Lock Version with npx (Recommended & Easiest)

Locks the supergateway version to 2.0.0. This works on all devices with Node.js v18 or above, and prevents NPM from dynamically fetching the latest v3.x which requires Node v20+.

Add one of these blocks to your mcpServers configuration file (e.g., claude_desktop_config.json or mcp_config.json):

Primary:

{
  "mcpServers": {
    "cds-kb": {
      "command": "npx",
      "args": [
        "-y",
        "supergateway@2.0.0",
        "--sse",
        "https://cds-kb-mcp-production.up.railway.app/sse"
      ]
    }
  }
}

Fallback (SAP BTP Cloud Foundry):

{
  "mcpServers": {
    "cds-kb": {
      "command": "npx",
      "args": [
        "-y",
        "supergateway@2.0.0",
        "--sse",
        "https://cds-kb-mcp.cfapps.ap21.hana.ondemand.com/sse"
      ]
    }
  }
}

Option 2: Global Installation (Offline & Network-Resilient)

Best for enterprise environments behind corporate firewalls, VPNs, or proxy servers where running npx dynamically on every IDE startup might fail or time out.

1. Install supergateway globally on your machine once:

   npm install -g supergateway@2.0.0

2. Update your IDE's mcpServers configuration to call the globally installed binary directly (no npx):

   Primary:

   {
     "mcpServers": {
       "cds-kb": {
         "command": "supergateway",
         "args": [
           "--sse",
           "https://cds-kb-mcp-production.up.railway.app/sse"
         ]
       }
     }
   }

   Fallback (SAP BTP Cloud Foundry):

   {
     "mcpServers": {
       "cds-kb": {
         "command": "supergateway",
         "args": [
           "--sse",
           "https://cds-kb-mcp.cfapps.ap21.hana.ondemand.com/sse"
         ]
       }
     }
   }

   (Note for Windows users: If your IDE cannot locate the global command, use supergateway.cmd as the command, or specify the absolute path to your global npm prefix).

Once configured, restart your IDE. The tools will immediately be available for your agent to use.

Tools Reference

The server exposes five tools. They are designed so an AI agent can go from a vague business question to a complete CDS view definition in two or three calls.

1. search_cds

Find CDS views by business meaning, name, tag, or classic SAP keyword (VBAK, BSEG, etc.). Returns a ranked shortlist.

Returns: ranked list with name, score, module, short description, and path.

1. **I_CAOPENITEMLIST**  [FI-FIO-AR-2CL]  (score 14.2)
   List of open items across customer and vendor accounts.
   path: views/I_CAOPENITEMLIST.md
2. **I_PARKEDOPLACCTGDOCRBLSITEM**  ...

2. get_cds_view

Fetch one view's definition by exact name. Default: full markdown (metadata + fields + associations + source). Use sections to slim down the response.

Typical pattern: search_cds → pick a hit → get_cds_view(name, sections=["metadata", "fields"]) to confirm the field list without pulling 5-10 KB of DDL source.

3. get_views_by_tag

Deterministic listing by tag. Use when search_cds is too fuzzy.

Discover valid tags with get_taxonomy first.

4. get_taxonomy

Returns the semantic map: 12 Lines of Business → 829 Business Objects, each with keywords and synonyms. Useful for the agent to orient itself before issuing a search, or to discover valid tags for get_views_by_tag.

No parameters.

5. kb_info

Report the active data source, view count, enrichment coverage, and index build timestamp. Use this to verify which version of the KB you're talking to.

source: remote:https://raw.githubusercontent.com/truongdva2/cds-kb-data/main (cache ~/.cache/cds-kb/...)
views: 7355
enriched: 7160
modules: 31
builtAt: 2026-06-25T09:13:52.301Z

Architecture

┌──────────────────────────────────────────────────────────────────┐
│                         AI Client (Claude)                       │
│              search_cds("vendor open items", "FI")               │
└──────────────────────────┬───────────────────────────────────────┘
                           │  MCP / JSON-RPC over stdio
┌──────────────────────────▼───────────────────────────────────────┐
│                   cds-kb-mcp (this server)                       │
│  ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐         │
│  │ search_cds│ │ get_view  │ │ taxonomy  │ │ kb_info   │  ...    │
│  └─────┬─────┘ └─────┬─────┘ └─────┬─────┘ └─────┬─────┘         │
│        └─────────────┴─────────────┴─────────────┘               │
│                       │                                          │
│  ┌────────────────────▼───────────────────┐                      │
│  │   MiniSearch (in-memory, 5.7 MB index) │                      │
│  └────────────────────┬───────────────────┘                      │
│                       │                                          │
│  ┌────────────────────▼───────────────────┐                      │
│  │   DataSource (Local | Remote)          │                      │
│  │   • ETag-validated cache               │                      │
│  │   • Atomic writes, SWR, retry          │                      │
│  └─────────┬───────────────────┬──────────┘                      │
└────────────┼───────────────────┼─────────────────────────────────┘
             │                   │
       ┌─────▼────┐         ┌────▼──────────────┐
       │ Local FS │         │ GitHub Raw / CDN  │
       │ cds-kb-  │         │ raw.github...     │
       │ data/    │         └───────────────────┘
       └──────────┘