CAP V2 Case MCP — SAP Sales Cloud V2 Case Integration

A SAP CAP (Cloud Application Programming Model) project that exposes SAP Sales Cloud V2 (C4C) case management operations as an OData V4 + MCP dual-protocol service.

📐 Architecture Overview

Client (OData V4 / MCP)
        │
        ▼
┌─────────────────────────┐
│   CaseServices (CAP)    │  ← srv/services.cds + srv/services.js
│  /odata/v4/case-services│
│                         │
│  listCases()            │
│  getCaseById()          │
│  createCase()           │
│  patchCase()            │
└────────────┬────────────┘
             │ c4c.send() — HTTP REST
             ▼
┌─────────────────────────┐
│  SAP Sales Cloud V2     │  ← REST API
│  /sap/c4c/api/v1/       │
│    case-service/cases   │
└─────────────────────────┘

Related MCP server: SAP CPI MCP Server

🗂️ Project Structure

🔑 Key Concepts

1. Dual Protocol — OData V4 + MCP

The service is annotated with both protocols:

annotate CaseServices with @protocol: ['odata-v4', 'mcp'];

This means the same service is reachable as an OData V4 endpoint and as an MCP (Model Context Protocol) tool — usable by AI agents.

2. External Service Import

The remote SAP Sales Cloud V2 API was imported using:

cds import SalesSvcCloudV2_case.json --as cds

This generates SalesSvcCloudV2_case.cds — a CDS description of the remote REST API. It is used as documentation/metadata only, not invoked by name.

3. kind: "rest" — Not OData

The remote service is bound as a plain REST adapter in package.json:

"SalesSvcCloudV2_case": {
  "kind": "rest",
  "model": "srv/external/SalesSvcCloudV2_case",
  "service": "Case.Service"
}

• kind: "rest" → CAP uses an HTTP client, not an OData client

• service: "Case.Service" → maps the requires key to the actual service definition inside the CDS model (namespace ![Case]; service Service {})

• Because it is REST (not OData), there are no entities — c4c.entities is empty

4. c4c.send() — Why Not SELECT.from()

Since SalesSvcCloudV2_case.cds defines only functions (no entities), c4c.send() is used to make a direct HTTP call to the remote path annotated with @openapi.path.

5. Handler Registration & Service Name Matching

CAP wires the JS class to the CDS service via the export key — it must match the CDS service name exactly:

// services.js
module.exports = { CaseServices: CaseService };
//                  ↑ must match service name in services.cds

Handlers are registered inside init() using the exact function/action name from services.cds:

this.on("listCases", async (req) => { ... });
//       ↑ must match function name in services.cds

🚀 Operations

▶️ Running Locally

npm install
cds watch

Service available at: http://localhost:4004/odata/v4/case-services

🔗 References

• SAP CAP Documentation

• CAP External Services

• SAP Sales Cloud V2 API