rfc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_rfc_functionsA | Search SAP for remote-enabled function modules (BAPIs/RFCs) by name pattern (supports '' wildcards, e.g. 'BAPI_CUSTOMER_'). Call this first to discover available functions before get_rfc_function_interface or call_rfc_function. |
| get_rfc_function_interfaceA | Return the full IMPORT/EXPORT/TABLES/CHANGING parameter interface (including resolved structure fields) and documented exceptions for a function module. Always call this before call_rfc_function to know exactly what parameters are required and how they're shaped. |
| call_rfc_functionA | Invoke a SAP RFC-enabled function module with JSON parameters. Call get_rfc_function_interface first to know what parameters are required. mode='write' is required for functions classified as mutating and is rejected unless the server's policy explicitly allows writes for that function. A write returns a transaction_id tied to its SAP connection; reuse it for related writes, then pass it to commit_rfc_transaction or rollback_rfc_transaction. Writes are never auto-committed. |
| commit_rfc_transactionA | Persist changes staged by prior write call_rfc_function calls in the identified SAP transaction (BAPI_TRANSACTION_COMMIT). Only available when the server policy mode is read_write. |
| rollback_rfc_transactionA | Discard changes staged by prior write call_rfc_function calls in the identified SAP transaction (BAPI_TRANSACTION_ROLLBACK). Only available when the server policy mode is read_write. |
| read_abap_sourceA | Read the full ABAP source of a program, class, or function module.
Automatically uses ADT (one call, most reliable — especially for
classes, which need several RFC calls otherwise) when it's enabled and
reachable, and transparently falls back to RFC (RPY_PROGRAM_READ /
RPY_FUNCTIONMODULE_READ) otherwise — including on a live ADT failure,
not just when it's disabled. You never need to choose the transport
yourself; check the returned |
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 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.