MCP Server for SAP OData v4
by shahidla
README.md
# MCP Server for SAP OData v4
An [MCP (Model Context Protocol)](https://modelcontextprotocol.io) server that exposes SAP OData v4 actions as AI-callable tools. Designed to be used with MCP-compatible AI clients such as Claude.
## Tools
| Tool | Description |
|---|---|
| `hello` | Smoke test — returns a hello message |
| `schedule_background_job` | Calls a SAP OData v4 action with a given option |
## Setup
1. Clone the repo:
```bash
git clone https://github.com/your-username/mcp.git
cd mcp
```
2. Install dependencies:
```bash
npm install
```
3. Copy `.env.example` to `.env` and fill in your SAP credentials:
```bash
cp .env.example .env
```
4. Build the TypeScript source:
```bash
npm run build
```
5. Start the MCP server:
```bash
npm start
```
## Configuration
| Variable | Description |
|---|---|
| `SAP_URL` | Base URL of your SAP OData v4 service |
| `SAP_USER` | SAP username |
| `SAP_PASSWORD` | SAP password |
| `SAP_CLIENT` | SAP client number (required) |
| `SAP_ACTION_PATH` | OData action path (e.g. `your-namespace/your-namespace.your-service.ActionName`) |
## Requirements
- Node.js 18+
- A SAP system exposing an OData v4 service
## License
ISC
TDQS
D1.2/5.0
Scored across 2 tools
Disambiguation4/5
Only two tools with distinct names, so they are unlikely to be confused. However, the lack of descriptions for 'hello' introduces some ambiguity about its purpose.
Naming Consistency1/5
No consistent naming pattern: 'hello' is arbitrary while 'schedule_background_job' follows a verb_noun structure, indicating a mismatch.
Tool Count1/5
Two tools are grossly insufficient for an SAP OData v4 server, which would typically require many tools for CRUD operations on entities.
Completeness1/5
The tool set lacks any OData-specific operations (e.g., read, create, update, delete entities), making it severely incomplete for the stated domain.
Maintenance
ActivityInactive
ResponsivenessNo issues