mcp-rap-migrator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAP_URL | Yes | The SAP system URL (e.g., https://your-sap.com:8000) | |
| SAP_CLIENT | Yes | The SAP client (e.g., 100) | |
| SAP_PASSWORD | Yes | The SAP password | |
| SAP_USERNAME | Yes | The SAP username |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_module_poolA | STEP 1 — Analyzes Module Pool source code fetched by mcp-abap-adt. IMPORTANT: First use mcp-abap-adt GetProgram to get program source, then GetInclude for each include, then pass combined source here. Returns structured JSON: screens, PAI/PBO modules, tables, LLM business analysis, PAI-to-RAP mapping. |
| check_released_cdsA | STEP 1b — MANDATORY before generate_rap_skeleton. Checks if SAP has released CDS views for the tables found in the Module Pool. Clean Core: always SELECT from released CDS instead of raw tables. Returns cds_source_mapping to pass into generate_rap_skeleton. |
| generate_rap_skeletonA | STEP 2 — Given the analysis JSON from step 1, generates the full RAP migration plan: CDS view, Behavior Definition, Behavior Implementation class, metadata extensions. Returns ABAP code as strings — does NOT write to SAP yet. Human must approve. |
| human_checkpointA | MANDATORY between every step — shows the human: WHAT WAS DONE, ANALYSIS SUMMARY, and NEXT PROPOSED ACTION. Human must type YES/MODIFY/ABORT to proceed. Always call this before write_abap_object or validate_and_activate. |
| write_abap_objectA | STEP 3 — Writes a single ABAP object to SAP via ADT REST. CRITICAL: Always follow this exact order: 1st=CDS Root View (DDLS), 2nd=CDS Child Views (DDLS), 3rd=Behavior Definition (BDEF), 4th=Implementation Class (CLAS), 5th=Metadata Extension (DDLS). NEVER write BDEF before CDS views. NEVER write CLAS before BDEF. One object at a time only. |
| validate_and_activateA | STEP 4 — Activates one or more ABAP objects via ADT REST. Runs syntax check first, returns errors for agent to fix before activation. Call human_checkpoint with results. |
| create_transportA | Creates a Workbench Transport Request in SAP. Do this before write_abap_object. Returns transport number. |
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 7 tools
Each tool targets a distinct step in the migration workflow: analysis, CDS checking, transport creation, skeleton generation, human checkpoint, writing objects, and validation. No overlap or ambiguity.
Most tool names follow a verb_noun pattern (analyze_module_pool, check_released_cds, create_transport, generate_rap_skeleton, write_abap_object). However, 'human_checkpoint' is noun_noun and 'validate_and_activate' uses two verbs, breaking the pattern slightly.
7 tools cover the entire migration pipeline without being excessive. Each tool serves a necessary function, and the count is appropriate for the domain's complexity.
The tool set covers all essential steps from analysis through activation, including mandatory checkpoints. No obvious gaps for a migration workflow.