SAP / MODEL CONTEXT PROTOCOL
SAP MCP Server.
Controlled SAP access for Claude Code and Codex.
NeKu AI SAP MCP Server lets Claude Code and Codex work with SAP documentation, permitted analysis tasks and read-only business data within organizational data boundaries and SAP user permissions.
Request a demo ↗- 01DOCS
- 02ACTIONS
- 03DATA
- 04AUDIT
01 / SHORT ANSWER
What is an SAP MCP Server?
MCP stands for Model Context Protocol. NeKu AI SAP MCP Server creates a standard tool and context layer between AI clients and SAP systems. An agent can read exposed SAP documentation or invoke only the SAP tools it is permitted to use.
SAP authorization applies to every call. Target system, user identity, access mode, audit and output-redaction rules constrain access.
SAP Docs, SAP Actions and SAP Data support documentation research, permitted SAP tasks and read-only business data. Yargı MCP supports Turkish legal research independently of SAP.
- Protocol
- Model Context Protocol
- Use cases
- Documentation, analysis and business data
- Data access
- Limited by SAP user permissions
- First evaluation
- One task in a test environment
- Clients
- MCP-compatible clients and Agent Builder agents
START HERE / USAGE GUIDES
Choose your first SAP MCP task
Start with documentation, an ABAP read or a business-data query.
Connect Claude Code and Codex
Review supported clients, organizational access requirements and your first demo task.
↗ 02OData business data with SAP Data
Explore permitted SAP business-data questions and a read-only demo evaluation.
↗ 03SAP MCP pilot acceptance
Use the NeKuDos matrix to assess target-system selection, permission denial, correctness and failure behavior.
↗02 / USE CASES
Reading information, querying data and executing actions remain separate
Choose the scope that meets your business need. Information research, reading business data and changing records need different access and approval.
Access to documentation and context
Lets agents research, explain and draft content using SAP documentation and authorized knowledge sources.
- Knowledge access
- Context-grounded answers
- Documentation-focused
Permission-controlled SAP tasks
Lets agents invoke defined query or action tools in a target SAP system within user authorization and access-mode limits.
- Multiple SAP systems
- Per-user identity
- Read and action modes
Read-only SAP business data
Lets agents answer business-data questions through the OData services an admin enabled instead of free-form SQL. Functions that change data are never exposed.
- Enabled OData services only
- The user's own SAP identity
- Bounded data for the task
Turkish legal research
Researches court and regulatory decisions with source references. It can be used independently of SAP.
- Court of Cassation, Council of State and Constitutional Court decisions
- KİK, Competition Authority, KVKK, BDDK and GİB sources
- Product access suited to your use
03 / HOW IT WORKS
From a business question to a verifiable answer
Define your task
Start with an SAP question, a documentation need or permitted business data.
Prepare the access scope
Choose the appropriate user and test environment with your SAP and NeKu AI owners.
Evaluate the answer
Compare the result with SAP or the original document, and account for missing information.
04 / EXAMPLE TASK
An MCP demo that explains an ABAP object
Example read task: “Explain what my selected ABAP object does and identify its relevant sources.” Select the object, test system and permitted tools before the demo.
Choose the scope
Choose one ABAP object, an SAP test environment and read-only access. The task does not change code or business records.
Perform the permitted read
Ask for the selected object’s purpose and relevant documentation. The user’s SAP read permissions remain effective.
Compare the explanation with its sources
Check the answer against the object and documentation actually read. The answer identifies inaccessible objects, partial content and inferences.
Evaluate a failure case too
Check that an unauthorized object and a failed read preserve the access boundary. The call record, returned data scope and explanation to the user belong in the acceptance assessment.
05 / SAP DATA
Read-only business data through admin-enabled OData services
SAP Data answers business-data questions from the OData services your organization enables, within SAP user permissions. Read-only use does not change business records.
Data selected by your organization
Agree the information and service scope with your SAP owner.
SAP user permissions
Users can access only information they are authorized to view in SAP.
Information relevant to the question
Evaluate only the records and fields needed for the first task.
Result scope
Limited or incomplete information should not be presented as a review of every record.
Read-only use
SAP Data does not create or change SAP business records.
Product access
Prepare suitable licensing and connectivity with the NeKu AI team.
06 / CONTROL LAYERS
Context and boundaries on every tool call
Target system, user identity and access mode apply to every tool call.
Multi-system selection
ECC and S/4HANA environments are separated as named connections and each call identifies the target.
Per-user credentials
SAP connections are assigned to users and credentials are never exposed in client responses.
Access modes
Read-only use and separately permitted actions are bounded by the task’s requirements.
Audit and redaction
Tool calls are auditable, while sensitive fields and technical secrets can be removed from output.
07 / COMPATIBILITY
Designed around the environments SAP teams operate
SAP ECC EHP8
A supported connection target for bringing AI tools to established ECC environments.
SAP S/4HANA 1809
A supported release for S/4HANA transformation and operations scenarios.
SAP S/4HANA 2023
A supported connection target for S/4HANA 2023 environments; release-specific differences are handled with capability checks.
Cloud and on-premise NeKu AI
The MCP layer is positioned within the selected NeKu AI deployment and enterprise architecture.
08 / FREQUENTLY ASKED QUESTIONS
Short answers about SAP MCP
01What does MCP stand for?+
MCP stands for Model Context Protocol, a standard way for AI clients to work with tools and context sources.
02Which use cases does NeKu AI MCP support?+
SAP Docs supports documentation research, SAP Actions permitted SAP tasks and SAP Data read-only business data. Yargı MCP can be used for Turkish legal research independently of SAP.
03Can SAP Data change SAP data?+
No. SAP Data is read-only and does not create or change SAP records. Users can access only information enabled by their organization, within their SAP permissions.
04Does Yargı MCP need an SAP system?+
No. Yargı MCP is a Turkish legal research solution independent of SAP. Product access requires a suitable NeKu AI license.
05Which MCP clients does it work with?+
MCP-compatible clients connect to NeKu AI SAP MCP Server, and you can build your own SAP agents in Agent Builder. Connection preparation for your organization is shared with your authorized team.
06Are SAP MCP and the n8n SAP Connector the same?+
No. SAP MCP exposes context and tools to AI agents. The n8n SAP Connector links SAP data and actions to n8n workflows.
07Can SAP MCP connect to multiple SAP systems?+
Yes. Connections can be managed as named systems and each tool call explicitly selects its target system.
08Are SAP credentials sent to the AI model?+
No. SAP credentials stay in the connection layer and are not returned to the model or client.
09Is read-only use supported?+
Yes. Read-only use limits the connection to permitted information and data-reading tasks; it does not grant permission to change records.
10Are SAP MCP and SAP Integration Suite MCP Gateway the same?+
They use the same protocol family but are not the same product component. SAP Integration Suite can publish MCP Server artifacts through MCP Gateway; NeKu AI SAP MCP Server is a separate solution architecture that controls SAP Docs, SAP Actions and SAP Data for NeKu AI workflows.
11What should I verify in an SAP MCP demo?+
Start with one read-only task. Verify user and system access, rejection of unauthorized calls, output scope and failed tool-call behaviour.
12What do I need to connect?+
You need suitable product access, an approved client and the SAP user permissions required by the task. Prepare connectivity with your NeKu AI and SAP owners.
09 / RELATED SOLUTIONS AND SOURCES
Explore SAP MCP use cases
Ready-to-Run SAP AI Workflows
Explore ready-made tasks that can use SAP MCP tools.
↗ 02AI for Turkish Law
Explore the source-backed Turkish law research workflow and the Yargı MCP server.
↗ 03SAP AI
Review the complete SAP AI use-case and security approach.
↗ 04n8n SAP Connector
Explore the separate SAP connectivity solution for n8n automation.
↗ 05SAP Integration Suite MCP documentation
Read SAP's official explanation of MCP Server, MCP Gateway, tools, resources and prompts.
↗ 06SAP AI MCP servers directory
Review open-source and official MCP servers across the SAP ecosystem.
↗ 07Integration-layer decision guide
Evaluate your architecture by separating the roles of n8n, Integration Suite and MCP.
↗