rfc-mcp
Related Servers
Alternatives to rfc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude to read SAP ECC and S/4HANA data through OData and RFC/BAPI calls, with writes gated behind a human confirmation step and every call written to an audit log. No proprietary SAP NetWeaver RFC SDK is required.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to securely read and write SAP ABAP development objects via the ADT REST API, enforcing policy-based guardrails such as package/namespace allow-lists, read-only mode, human approvals, and audit logging.82MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to integrate with SAP systems via OData REST APIs for querying entity sets, performing CRUD operations, and executing function imports. It features automatic service discovery, CSRF token management, and smart connection handling without requiring the SAP RFC SDK.1112-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants and n8n workflows to interact with SAP S/4HANA and ECC systems via OData, IDoc, and RFC/BAPI, with governed read-only-by-default access and multiple authentication types.3ISC
- AlicenseAqualityDmaintenanceEnables AI agents to read, write, activate, and transport ABAP code in SAP systems via ABAP ADT REST API, without needing SAP GUI.24386 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to securely connect with SAP ABAP and BTP services, allowing execution of function modules, BAPIs, table reads, and various BTP operations through MCP.1Apache 2.0
TDQS
Scored across 6 tools
Each tool targets a distinct phase: search_rfc_functions discovers, get_rfc_function_interface inspects the signature, call_rfc_function executes, commit/rollback manage the transaction, and read_abap_source reads source. The descriptions reinforce the ordering (call search first, then get interface, then call), leaving no realistic basis for misselection.
All six names follow a consistent snake_case verb_noun pattern (search_, get_, call_, commit_, rollback_, read_). No camelCase or stylistic mixing; the shared 'rfc' token further groups the related operations.
Six tools is well-scoped for a single-domain RFC client, and each one earns its place by covering a distinct step of the discover-inspect-execute-commit lifecycle. Nothing redundant or trivial is present.
The surface covers the core lifecycle from discovery through read/write execution and transaction commit/rollback, plus ABAP source inspection. Minor gaps exist, such as no bulk/atomic multi-function call or dedicated structure/schema explorer, but agents can work around these via the interface tool.