MCP Server for SAP OData v4
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAP_URL | No | Base URL of your SAP OData v4 service | |
| SAP_USER | No | SAP username | |
| SAP_CLIENT | Yes | SAP client number (required) | |
| SAP_PASSWORD | No | SAP password | |
| SAP_ACTION_PATH | No | OData action path (e.g. your-namespace/your-namespace.your-service.ActionName) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| helloD | – |
| schedule_background_jobD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
No consistent naming pattern: 'hello' is arbitrary while 'schedule_background_job' follows a verb_noun structure, indicating a mismatch.
Two tools are grossly insufficient for an SAP OData v4 server, which would typically require many tools for CRUD operations on entities.
The tool set lacks any OData-specific operations (e.g., read, create, update, delete entities), making it severely incomplete for the stated domain.