MCP tool that generates structured ABAP Technical Specification documents from SAP Transport Requests. Connects to any SAP system via ADT REST API and produces ready-to-review Markdown specs covering all WRICEF object types.

GenerateWricefTechSpec is an MCP (Model Context Protocol) tool that:

1. Reads one or more Transport Request numbers from your SAP system
2. Fetches the transport objects and their source code via ADT
3. Analyses the source for DB tables, function module calls, authorisation objects, error handling patterns, and performance anti-patterns
4. Produces a fully structured Markdown Technical Specification with up to 32 configurable sections
5. Includes a Mermaid object-relationship diagram with colour-coded code objects grouped by transport

One WRICEF can span multiple transport requests and contain mixed object types — all are handled in a single spec.

• Go 1.21+ (build from source) or use a pre-built binary
• SAP system with ADT enabled (/sap/bc/adt/ ICF services active)

git clone https://github.com/SaurabhVC/ABAPDocMCP.git
cd ABAPDocMCP
go build -o abapdocmcp ./cmd/vsp/main.go

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "abapdocmcp": {
      "command": "/path/to/abapdocmcp",
      "env": {
        "SAP_URL": "https://your-sap-host:44300",
        "SAP_USER": "your-username",
        "SAP_PASSWORD": "your-password",
        "SAP_CLIENT": "100"
      }
    }
  }
}

Self-signed certificates: Add "SAP_INSECURE": "true" to the env block.

Add .mcp.json to your project root:

{
  "mcpServers": {
    "abapdocmcp": {
      "command": "/path/to/abapdocmcp",
      "env": {
        "SAP_URL": "https://your-sap-host:44300",
        "SAP_USER": "your-username",
        "SAP_PASSWORD": "your-password",
        "SAP_CLIENT": "100"
      }
    }
  }
}

Minimal — just a transport number:

GenerateWricefTechSpec(
  transport_numbers = "DEVK900123"
)

Full Report spec:

GenerateWricefTechSpec(
  transport_numbers  = "DEVK900123,DEVK900124",
  wricef_type        = "REPORT",
  wricef_id          = "ZSD-R-001",
  complexity         = "M",
  cr_number          = "CHG0012345",
  module             = "SD",
  developer_name     = "John Smith",
  developer_user_id  = "JSMITH",
  reviewer_name      = "Mary Johnson",
  system_id          = "DEV",
  client             = "100"
)

Enhancement spec:

GenerateWricefTechSpec(
  transport_numbers  = "DEVK900145",
  wricef_type        = "ENHANCEMENT",
  wricef_id          = "ZFI-E-001",
  complexity         = "S",
  module             = "FI",
  enhancement_type   = "BAdI",
  enhancement_name   = "BADI_ACC_DOCUMENT",
  original_program   = "SAPLGL_ACCOUNT_ASSIGNMENT"
)

Interface spec:

GenerateWricefTechSpec(
  transport_numbers      = "DEVK900130",
  wricef_type            = "INTERFACE",
  wricef_id              = "ZMM-I-001",
  complexity             = "L",
  module                 = "MM",
  interface_direction    = "Outbound",
  interface_protocol     = "IDoc",
  interface_frequency    = "Event-driven"
)

All sections are controlled by tech-spec-config.json. The default set (in order):

The diagram is automatically generated from transport objects and — when source code is fetched — enriched with edges for:

• INCLUDE statements → includes edge
• CALL FUNCTION / CALL METHOD → calls FM / calls method edge
• CREATE OBJECT / NEW → instantiates edge

Code object types displayed (tables, structures, domains etc. are excluded):

When a WRICEF spans multiple transport requests, each TR appears as a labelled subgraph.

Place tech-spec-config.json in the same directory as the binary (or the working directory) to customise which sections appear and in what order:

{
  "sections": [
    "documentInfo",
    "developerInfo",
    "changeRequest",
    "wricefClassification",
    "transportDetails",
    "transportContents",
    "businessRequirement",
    "scopeAssumptions",
    "technicalDesign",
    "objectRelationDiagram",
    "reportDetails",
    "interfaceDetails",
    "messageMapping",
    "enhancementDetails",
    "formDetails",
    "workflowDetails",
    "odataDetails",
    "pseudocode",
    "databaseObjects",
    "calledFunctions",
    "authorizationObjects",
    "errorHandling",
    "performanceConsiderations",
    "testScenarios",
    "additionalNotes",
    "changeHistory",
    "signOff"
  ],
  "sectionTitles": {
    "documentInfo": "Document Information",
    "objectRelationDiagram": "Object Relationship Diagram",
    "reportDetails": "Selection Screen / Input Parameters"
  }
}

• sections — ordered list of section IDs to include; omit any ID to suppress that section
• sectionTitles — override any heading text; only specify sections whose titles you want to change

The full list of 32 section IDs and their default titles is in the tech-spec-config.json file at the project root.

See SAMPLE_WRICEF_TECH_SPEC.md for a complete example showing:

• R — Report spec (ZSD-R-001) with selection screen, ALV layout, pseudocode, DB tables, FM calls, ATC, auth objects
• I — Interface spec (ZMM-I-001) with field mapping table
• E — Enhancement spec (ZFI-E-001) with BAdI details and pseudocode

ABAPDocMCP/
├── cmd/vsp/main.go                   # Entry point (CLI + MCP server)
├── internal/
│   ├── mcp/
│   │   ├── server.go                 # Tool registration
│   │   └── handlers_techspec.go      # GenerateWricefTechSpec handler
│   └── techspec/
│       ├── config.go                 # Section config loader (tech-spec-config.json)
│       ├── mermaid.go                # Mermaid diagram generator
│       └── generator.go             # 32-section spec renderer
├── pkg/adt/                          # SAP ADT REST API client
│   ├── client.go
│   ├── transport.go                  # GetTransport, ListTransports
│   └── workflows.go                  # GetSource (PROG, CLAS, FUNC, INCL …)
├── tech-spec-config.json             # Default section order & titles
└── SAMPLE_WRICEF_TECH_SPEC.md        # Sample generated output

# Current platform
go build -o abapdocmcp ./cmd/vsp/main.go

# All platforms (requires make)
make build-all

MIT