MCP serverMCP servertypeExposes tools to a coding agent over MCP.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

sap-security-mcp

An entirely read-only security analysis surface: nineteen tools, five resources and eight prompts for audits, SOX and segregation-of-duties review, behind OAuth 2.0 with PKCE. The vendor hosts an endpoint, and the README documents running it yourself.

Everything else pointed at an SAP system in this corpus can change something; this one cannot, and says so as a feature. Nineteen tools across user management, security analysis, compliance auditing and role and authorisation review, all read-only; five resources describing the system, its security posture, the compliance frameworks and the controls; and eight prepared prompts for the workflows an auditor actually runs, SOX and segregation of duties among them. Authentication is full RFC 8414 and 9728 OAuth with PKCE and dynamic client registration, which is more than most hosted endpoints in this corner attempt.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Provides
Agent access to your systemsABAPAgent access to your systemscapabilityGiving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. [Serving your application over MCP](capability:mcp-servers) exposes your own service contract; system access reaches the systems behind it, and one implementation may do both. Development assistance belongs to [agent access to your code](capability:agent-code-access).

Who is behind it

SYNTAAISYNTAAIOrganisationMaintains this
In the atlas: maintains 1
@SYNTAAI
maintainermohanjani79PersonContributes to this
In the atlas: contributes to 1
@mohanjani79
1 contributor

Before choosing this

Conditions

PracticalFunctional boundary

Read-only does not mean low-stakes: a complete picture of who can do what in an SAP system is exactly what an attacker would want, and the ready-made endpoint is the vendor's rather than yours — the README also documents running the server yourself. The authentication is careful; the question of what leaves your landscape is still yours.

PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2from Agent access to your systemsAn MCP server uses SAP APIs to supply tools, resources or data to an agent.
  • § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
  • § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
  • § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.

MCP does not replace the API's documented-use boundary. Check that every endpoint is published for the intended use and whether the policy's AI-call or extraction provisions apply to the design.

SAP API Policy 4.2026a →

What it declares

Every artifact

Type
MCP server
Origin
Independently maintained

As an MCP server

Runs as
vendor's endpointcentral server
Authentication
OAuth / OIDC
Tools
19
Read-only
yesstates it is
Guardrails
2 quoted from README show all
  • Supports Dynamic Client Registration (RFC 7591) and token revocation (RFC 7009).

  • MCPNOAUTH=1 python server.py # without OAuth (development)

Connections1

README

quoted from SYNTAAI/sap-security-mcp under Apache-2.0, read
SYNTAAI/sap-security-mcp/README.mdOn GitHub

SyntaAI ERP Security MCP Server

AI-powered security analysis for SAP systems via the Model Context Protocol (MCP).

Server URL: https://mcp.syntaai.com/mcp

Features

  • 19 Tools — User management, security analysis, compliance auditing, role & authorization review (all read-only)
  • 5 Resources — System info, security overview, compliance frameworks, security controls, user summary
  • 8 Prompts — Pre-built workflows for security audits, SOX compliance, SoD analysis, and more
  • OAuth 2.0 — Full RFC 8414/9728 compliant authentication with PKCE and Dynamic Client Registration

Example Interactions

Example 1: Security Audit

User prompt: "Are there any users with SAP_ALL profile?"

What happens:

  • Server scans all user profiles for dangerous authorizations
  • Returns list of users with SAP_ALL, SAP_NEW, S_A.SYSTEM
  • Provides risk assessment and remediation recommendations

Tool used: check_critical_authorizations


Example 2: Compliance Check

User prompt: "Generate a SOX compliance report"

What happens:

  • Server runs SOX assessment across access controls, SoD, password policy
  • Returns overall compliance score with findings
  • Lists critical gaps with specific framework control references

Tool used: generate_compliance_report


Example 3: User Access Review

User prompt: "Find all users who haven't logged in for 90 days and check if any have critical roles"

What happens:

  • Server identifies inactive users past the threshold
  • Cross-references with privileged access and role assignments
  • Recommends lock/disable actions prioritized by risk

Tools used: find_inactive_users, list_privileged_users

Tools Reference

User Management
ToolDescriptionAnnotations
list_usersList SAP users with status/type filteringRead-only
get_user_detailsGet detailed user info including roles and login historyRead-only
list_user_rolesList roles and profiles for a userRead-only
find_inactive_usersFind users inactive for N daysRead-only
Security Analysis
ToolDescriptionAnnotations
get_security_parametersSAP security parameters vs best practicesRead-only
check_critical_authorizationsFind users with SAP_ALL/SAP_NEW/S_A.SYSTEMRead-only
get_audit_logRetrieve security audit log entriesRead-only
check_default_passwordsCheck for default/initial passwordsRead-only
get_rfc_connectionsAnalyze RFC destinations for credential risksRead-only
Compliance & Audit
ToolDescriptionAnnotations
run_sod_checkCheck Segregation of Duties violationsRead-only
generate_compliance_reportGenerate SOX/GDPR/ISO27001/NIST reportRead-only
list_privileged_usersList users with elevated privilegesRead-only
check_password_policyAnalyze password policy vs best practicesRead-only
get_transport_logTransport request log for change managementRead-only
Role & Authorization
ToolDescriptionAnnotations
list_rolesList security roles with searchRead-only
get_role_detailsGet role details including authorizationsRead-only
compare_user_accessCompare access rights between two usersRead-only
find_users_with_roleFind all users assigned a specific roleRead-only
get_authorization_traceGet authorization check trace entriesRead-only

Authentication

OAuth 2.0 with PKCE. Discovery endpoints:

  • GET /.well-known/oauth-authorization-server (RFC 8414)
  • GET /.well-known/oauth-protected-resource (RFC 9728)

Supports Dynamic Client Registration (RFC 7591) and token revocation (RFC 7009).

Deployment

# Install
cd /opt/mcp-server
python -m venv venv
source venv/bin/activate
pip install -r requirements.txt

# Run
python server.py                    # with OAuth (production)
MCP_NO_AUTH=1 python server.py      # without OAuth (development)

License

Apache License 2.0 — see LICENSE for details.

Apache-2.0, read
Agent access to your systems
  1. @abap2ui5/mcp-serverMCP server for the abap2UI5 check, deploy and run loop
  2. abap2UI5 for VS CodeVS Code extension to preview, activate and lint abap2UI5 apps
  3. abapsmithABAP MCP server over ADT with a local journal that can undo writes
  4. btp-sap-odata-to-mcp-serverExposes S/4HANA or ECC OData services as MCP tools
  5. midasol/sap-mcp-serverPython MCP server for SAP Gateway OData operations
  6. odata_mcp_goGo binary bridging any OData v2 or v4 service to MCP
  7. odata_mcpPython bridge generating MCP tools from OData v2 metadata
  8. sap-mcp-serverReads SAP ECC and S/4HANA for an agent over Gateway OData and RFC, with a Node bridge that speaks the RFC protocol without the proprietary SAP NetWeaver RFC SDK.
  9. Skybuffer AI MCP serverABAP add-on serving business data and transactions as MCP tools
  10. KlystronMCP server in ABAP inside the application server, with agent skills
  11. pyrfc-mcpMCP server calling RFC-enabled function modules behind an allowlist

Details

Sources3
sap-ai-mcp-serversdiscovered herechecked
github.com/SYNTAAI/sap-security-mcptree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viasap-ai-mcp-servers
first seen in the atlas
ecosystem and domainabap, security-and-compliance
Contributors1

From the repository’s contributor list, .

History in the atlas4
  1. The concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
  2. corrected against the README
  3. Triaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README. Filed on the BTP door because there is no door for the SAP product it fronts and hard rule 9 allows one — the same strain recorded on the LeanIX entries.
  4. First seen.
For your agent
Ref
artifact:syntaai-sap-security-mcp
JSON
/artifacts/syntaai-sap-security-mcp.json
MCP
Connecting an agent