How do I use mcp4odata?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp4odata list the latest sales orders for customer 10100001" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

mcp4odata

by horsemanjackyliu

Overview Schema Source Related Servers Discussions Admin

TypeScript

mcp4odata

An MCP (Model Context Protocol) server that exposes SAP S/4HANA OData services as tools for LLMs. Deployed on SAP Cloud Foundry (BTP).

Overview

LLM / MCP Client
      │  Bearer token (XSUAA)
      ▼
mcp4odata  (CF app)
      │  SAP Cloud SDK → BTP Destination Service
      ▼
SAP S/4HANA  (CE_SALESORDER_0001, OData v4)

Inbound auth: XSUAA Bearer token validation via @sap/xssec
Outbound connectivity: SAP Cloud SDK executeHttpRequest() with BTP Destination Service
Two MCP transports: Streamable HTTP (MCP 2025-11-25) and SSE fallback (MCP 2024-11-05)

Related MCP server: SAP S/4HANA MCP Server

Tools

`salesorder_get_list`

Retrieves a list of S/4HANA sales order headers.

Parameter	Type	Required	Description
`soldToParty`	string	No	Filter by customer number, e.g. `10100001`
`salesOrganization`	string	No	Filter by sales org, e.g. `1710`
`top`	integer	No	Max results, 1–100 (default: 20)

Returns: array of sales order headers — order number, type, sold-to party, total net amount, currency, requested delivery date.

`salesorder_create`

Creates a new S/4HANA sales order with one or more line items (deep-insert POST).

Header fields

Parameter	Type	Required	Description
`salesOrderType`	string	Yes	Order type, e.g. `OR`
`salesOrganization`	string	Yes	Sales org, e.g. `1710`
`distributionChannel`	string	Yes	Distribution channel, e.g. `10`
`organizationDivision`	string	Yes	Division, e.g. `00`
`soldToParty`	string	Yes	Customer number, e.g. `10100001`
`transactionCurrency`	string	No	ISO currency, e.g. `USD` (defaults from customer master)
`purchaseOrderByCustomer`	string	No	Customer PO number
`requestedDeliveryDate`	string	No	Delivery date, `YYYY-MM-DD`

Item fields (at least one item required)

Parameter	Type	Required	Description
`material`	string	Yes	Product number, e.g. `MZ-FG-M500`
`requestedQuantity`	string	Yes	Quantity as a string, e.g. `5`
`requestedQuantitySAPUnit`	string	Yes	SAP unit of measure, e.g. `EA`, `KG`
`plant`	string	No	Delivering plant, e.g. `1710`
`salesOrderItemCategory`	string	No	Item category, e.g. `TAN` (derived from config if omitted)
`salesOrderItemText`	string	No	Line item description (defaults to material description)

Returns: created sales order header including the generated order number.

Endpoints

Endpoint	Auth	Description
`POST/GET/DELETE /mcp`	Bearer (XSUAA)	Streamable HTTP transport — MCP 2025-11-25
`GET /sse`	Bearer (XSUAA)	SSE transport — MCP 2024-11-05
`POST /messages`	Bearer (XSUAA)	SSE message posting
`GET /health`	None	Health check (used by CF)

Local Development

Prerequisites

Node.js 20+
SAP BTP subaccount with XSUAA and Destination service instances

Setup

npm install
cp .env.example .env
# Fill in VCAP_SERVICES with your XSUAA and Destination credentials

.env structure (see .env.example for the full template):

VCAP_SERVICES='{ "xsuaa": [...], "destination": [...] }'
S4_DESTINATION_NAME=S4HANA_SALESORDER
PORT=3000

Run

npm run dev        # tsx watch mode
npm run build      # compile TypeScript → dist/

Test with MCP Inspector

Point the inspector at http://localhost:3000/mcp with a valid XSUAA Bearer token.

BTP Destination Configuration

Create an HTTP destination in the BTP cockpit with:

Field	Value
Name	`S4HANA_SALESORDER` (or your `S4_DESTINATION_NAME`)
Type	HTTP
URL	Your S/4HANA base URL
Authentication	OAuth2ClientCredentials
Token Service URL	XSUAA token endpoint for S/4HANA

The SAP Cloud SDK reads the Destination service binding from VCAP_SERVICES, fetches the destination, and injects the Authorization header automatically.

Cloud Foundry Deployment

Prerequisites

brew install cloudfoundry/tap/cf-cli@8
cf login -a https://api.cf.<region>.hana.ondemand.com
cf target -o <org> -s <space>

Create required service instances

cf create-service xsuaa application xsuaa-mcp4odata -c xsuaa-config.json
cf create-service destination lite destination-mcp4odata

Deploy

npm run build
cf push
cf logs mcp4odata --recent

Useful CF commands

cf env mcp4odata                          # inspect bound service credentials
cf set-env mcp4odata S4_DESTINATION_NAME  # override env variable
cf restage mcp4odata                      # restage after env changes

Project Structure

src/
├── server.ts           # Express app, MCP transports, route setup
├── auth/
│   └── middleware.ts   # XsuaaTokenVerifier — inbound Bearer token validation
├── odata/
│   └── client.ts       # getSalesOrders(), createSalesOrder() via SAP Cloud SDK
└── tools/
    ├── get-sales-orders.ts    # salesorder_get_list tool
    └── create-sales-order.ts  # salesorder_create tool
manifest.yml            # CF deployment manifest
.env.example            # Local dev environment template

Tech Stack

Layer	Technology
MCP Framework	`@modelcontextprotocol/sdk`
OData HTTP	`@sap-cloud-sdk/http-client`
Destination resolution	`@sap-cloud-sdk/connectivity`
Inbound auth	`@sap/xssec`, `@sap/xsenv`
Web server	Express 5
Language	TypeScript (Node.js 20+)
Deployment	SAP Cloud Foundry

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

IPStack MCP Adapter A
com.apilayer.mcp
IPStack MCP Adapter turns IPStack's REST APIs into Model Context Protocol tools so any MCP-compatible client can call them directly in conversation. The first release ships IPStack IP geolocation and security lookups (single IP, caller's IP, and bulk). Additional APILayer services are added by registering them in a single config file, so the catalog grows without client-side changes.
Location Services
32
Apideck MCP A
dev.apideck.mcp
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Developer Tools
42
hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
238
Artificial Wit AIOAuth
com.artificialwit
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
ERP Systems CRM Knowledge & Memory
2

Related MCP Servers

SAP OData to MCP Server
ERP Systems Databases App Automation
handeocakk
A
license
Not graded
quality
D
maintenance
Transforms SAP S/4HANA or ECC systems into conversational AI interfaces by exposing OData services as dynamic MCP tools. Enables natural language interactions with ERP data for querying, creating, updating, and deleting business entities.
Updated a year ago (2025-10-13 21:22 UTC)
26 npm
1
MIT
SAP S/4HANA MCP Server
ERP Systems Databases
Nidhideep
F
license
A
quality
D
maintenance
Enables interaction with SAP S/4HANA systems via OData, allowing service discovery, metadata exploration, field value retrieval, and CRUD operations through natural language.
Updated 3 months ago (2026-06-16 04:36 UTC)
4
5
-
sap-mcp-server
ERP Systems Search
Volshin
F
license
Not graded
quality
C
maintenance
Enables natural language querying of SAP business partner data by exposing OData APIs as MCP tools for LLM agents.
Updated 2 months ago (2026-07-16 00:22 UTC)
-
sap-sales-order-mcp
ERP Systems Search
coding-with-abbi
A
license
Not graded
quality
C
maintenance
MCP server for SAP S/4HANA Sales Order Management that enables natural language queries for sales orders, order details, and line items using SAP's public sandbox API. Built with offline testing, structured errors, and retry policies.
Updated a month ago (2026-08-09 19:58 UTC)
MIT

mcp4odata

Overview

Tools

salesorder_get_list

salesorder_create

Endpoints

Local Development

Prerequisites

Setup

Run

Test with MCP Inspector

BTP Destination Configuration

Cloud Foundry Deployment

Prerequisites

Create required service instances

Deploy

Useful CF commands

Project Structure

Tech Stack

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

SAP OData to MCP Server

SAP S/4HANA MCP Server

sap-mcp-server

sap-sales-order-mcp

`salesorder_get_list`

`salesorder_create`