Allows calling SAP OData v4 actions, such as scheduling background jobs, via MCP-compatible AI clients.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Server for SAP OData v4 schedule a background job to run payroll"
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.
An MCP (Model Context Protocol) server that exposes SAP OData v4 actions as AI-callable tools. Designed to be used with MCP-compatible AI clients such as Claude.
Tool | Description |
| Smoke test — returns a hello message |
| Calls a SAP OData v4 action with a given option |
Related MCP server: SAP OData MCP Server
Clone the repo:
git clone https://github.com/your-username/mcp.git
cd mcpInstall dependencies:
npm installCopy .env.example to .env and fill in your SAP credentials:
cp .env.example .envBuild the TypeScript source:
npm run buildStart the MCP server:
npm startVariable | Description |
| Base URL of your SAP OData v4 service |
| SAP username |
| SAP password |
| SAP client number (required) |
| OData action path (e.g. |
Node.js 18+
A SAP system exposing an OData v4 service
ISC
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| program_name | Yes | Name of the ABAP program to execute | |
| scrambleoption | Yes | Scramble option to send to SAP, for example SCRD | |
| job_name | Yes | Name to assign to the background job |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0helloschedule_background_jobOnly 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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Create and manage scheduled, guarded AI agent jobs with built-in quality control and 900+ connectors
Give AI agents 30,000+ safe, token-optimized actions across Workday, SAP, Oracle + hundreds more.
Give your AI agents the tools to build, manage, and run automation workflows.
Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/shahidla/MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
