MCP 도구로 OData 및 REST API를 노출하는 구성 구동 MCP (모델 Context Protocol) 서버. Claude와 같은 AI 조수가 자연 언어를 통해 쿼리, 관리, 모니터링 및 SAP 백엔드와 같은 가능하게 합니다.

서버는 SAP BTP Cloud Foundry에서 실행되며 BTP Destinations를 사용하여 OData API에 대한 보안, 토큰 관리 연결.

---

특징

• **32 OData entity 세트 ** 6 API 카테고리 이상, MCP 도구로 자동 등록 -Full CRUD 지원 – 목록, 얻고, 생성, 업데이트, API가 허용하는 작업을 삭제 -OData V2 쿼리 기능 – $filter, $select, $expand], $top], $skip, $inlinecount]
• Navigation property traversal – 관련 엔티티티에 대한 전용 도구 (예 : iFlow 구성, 메시지 첨부 파일, 오류 세부 사항)
• Category 기반 필터링 – 구성을 통해 필요한 API 범주만 가능
• ** 일반 운송 모드 ** – BTP 배포를위한 스트리밍 HTTP, 로컬 Claude Desktop 사용에 대한 stdio
• ** 자동 OAuth 토큰 관리 ** – 토큰은 BTP Destination Service를 통해 투명하게 재생됩니다.

---

건축

OData MCP Proxy

A config-driven MCP (Model Context Protocol) server that exposes OData and REST APIs as MCP tools. This enables AI assistants such as Claude to query, manage, and monitor SAP backends through natural language.

The server runs on SAP BTP Cloud Foundry and uses BTP Destinations for secure, token-managed connectivity to OData APIs.

---

Features

• 32 OData entity sets across 6 API categories, automatically registered as MCP tools
• Full CRUD support – list, get, create, update, and delete operations where the API permits
• OData V2 query capabilities – $filter, $select, $expand, $orderby, $top, $skip, and $inlinecount
• Navigation property traversal – dedicated tools for related entities (e.g., iFlow configurations, message attachments, error details)
• Category-based filtering – enable only the API categories you need via configuration
• Dual transport modes – Streamable HTTP for BTP deployment, stdio for local Claude Desktop use
• Automatic OAuth token management – tokens are refreshed transparently via the BTP Destination Service

---

Architecture

Claude / AI Assistant
        |
        | MCP Protocol (stdio or HTTP)
        v
 OData MCP Proxy
        |
        | OData V2 + JSON
        v
   OData Client
        |
        | OAuth2 (via BTP Destination Service)
        v
  BTP Destination
        |
        v
 SAP Cloud Integration
   OData Admin APIs

The server resolves a BTP Destination at startup to obtain the Cloud Integration tenant URL and OAuth2 credentials. On each API call, the destination is re-resolved to ensure tokens remain valid. The OData client translates MCP tool invocations into OData V2 HTTP requests and returns structured JSON results to the AI assistant.

---

Prerequisites

• Node.js 20+ (18+ minimum, 20+ recommended)
• SAP BTP account with a Cloud Foundry environment
• SAP Integration Suite tenant (Cloud Integration capability)
• BTP Destination configured to point to your Cloud Integration tenant’s OData API with OAuth2 authentication
• Cloud Foundry CLI (cf) and MBT Build Tool (mbt) for BTP deployment

---

Quick Start (Local Development)

1. Clone and install

git clone 
cd odata-mcp-proxy
npm install

2. Configure environment

cp .env.example .env

Edit .env and set at minimum:

SAP_DESTINATION_NAME=your_ci_destination_name
MCP_TRANSPORT=stdio

Note: For local development with stdio transport, you must have BTP Destination Service credentials available in your environment (e.g., via VCAP_SERVICES or a default-env.json file).

3. Build and run

npm run build
npm run start:stdio

Or use the development watcher:

npm run dev

4. Connect from Claude Desktop

Add the server to your Claude Desktop MCP configuration (claude_desktop_config.json):

{