convez.ai
MCP ServerDevOps & InfraestruturaAvançado
Nidhideep

SAP Transport MCP

Nidhideep/sap-transport-mcp

Acesso governado e auditável ao SAP CTS via Claude

Ver no GitHub
InicialPluginScore · de 0 a 100

MCP server que conecta Claude ao SAP Change and Transport System (CTS) para gerenciamento auditável de transports. Permite listar, inspecionar, criar, liberar e deletar requisições de transporte com governança integrada, validação obrigatória e confirmação do usuário.

Instalação

$npx convez-ai Nidhideep/sap-transport-mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Automatizar liberação de transports SAP com validação de objetos
  • Consultar fila de import em sistemas QA/PRD diretamente do Claude
  • Criar requisições de transporte com descrições validadas por governance
  • Auditar e rastrear mudanças entre ambientes DEV/QA/PRD
  • Deletar transports não liberados com segurança

Veredito

Ferramenta sólida para times SAP que precisam de controle auditável sobre transports. Requer NetWeaver 7.56+, credenciais SAP bem configuradas e conhecimento de CTS. Muito útil em ambientes corporativos com governança rigorosa.

README

A tradução para o português deste README ainda está na fila.

SAP Transport MCP

MCP server for SAP Change and Transport System (CTS). Gives Claude governed, auditable access to transport requests — list, inspect, create, release, and delete — via the SAP ADT REST API.

Built on sap-mcp-server-template.


What It Does

  • Lists open and released transport requests
  • Inspects transport contents (tasks, ABAP objects)
  • Checks import queue on target systems (QA, PRD)
  • Creates new transport requests with governance-validated descriptions
  • Releases transports for import — with mandatory object verification and user confirmation
  • Deletes unreleased transports — blocked if already released
  • Supports multi-system DEV/QA/PRD in a single server instance

Tech Stack

  • TypeScript + Node.js ≥18
  • @modelcontextprotocol/sdk — MCP server
  • axios — HTTP client (supports mTLS for X.509 cert auth)
  • fast-xml-parser — SAP ADT XML response handling
  • zod — runtime schema validation
  • SAP ADT REST API (/sap/bc/adt/cts/) over HTTPS

Prerequisites

RequirementDetails
Node.jsv18 or later — node --version to check
SAP NetWeaver7.56 or later (or a patched 7.40/7.50/7.52 SP with the CTS ADT node backport) — the /sap/bc/adt/cts/ ICF node was introduced in NetWeaver 7.56. Earlier releases do not expose the transportrequests REST endpoint and will return unexpected results. Ask your Basis admin to confirm your NetWeaver release and SP level.
SAP userS_ADT_RES authorization, role SAP_BC_DWB_ABAPDEVELOPER (ask your Basis admin if unsure)
ICF service/sap/bc/adt/ and /sap/bc/adt/cts/ activated — run transaction SICF in SAP GUI, navigate to default_host → sap → bc → adt → cts and activate. Ask Basis admin if not active.
NetworkHTTPS access to SAP host — VPN required for most on-prem systems
Claude CodeCLI or desktop app installed

Finding your SAP connection details

Open SAP Logon Pad (or ask your Basis team):

.env variableWhere to find it
SAP_HOSTNAMESAP Logon → right-click system → Properties → Application Server
SAP_SYSNRSAP Logon → right-click system → Properties → System Number (2 digits, e.g. 00)
SAP_CLIENTThe 3-digit number on the SAP login screen (e.g. 100)
SAP_USERNAMEYour SAP user ID (same as you type to log in)

Setup

1. Clone and install

git clone https://github.com/Nidhideep/sap-transport-mcp
cd sap-transport-mcp
npm install

2. Run setup

npm run setup

This creates .env from .env.example and generates .mcp.json with the absolute path to dist/src/index.js already filled in. Safe to re-run — never overwrites an existing .env.

3. Fill in your SAP credentials

Open .env and replace the placeholder values:

SAP_HOSTNAME=your-sap-host.example.com   # → your real hostname
SAP_SYSNR=00                              # → 2-digit system number
SAP_CLIENT=100                            # → 3-digit client number
SAP_USERNAME=your_user                    # → your SAP user ID
SAP_PASSWORD=your_password                # → your SAP password

Not sure where to find these? Open SAP Logon Pad → right-click your system → Properties. SAP_CLIENT is the 3-digit number on the SAP login screen.

4. Build

npm run build

5. Run preflight check

npm run preflight

This validates every variable, detects any remaining placeholder values, and tests a live HTTPS connection to your SAP system — before you register with Claude Code.

Example output when everything is ready:

  ✓ SAP_HOSTNAME = dev.sap.company.com
  ✓ SAP_USERNAME is set
  ✓ dist/src/index.js exists
  ✓ SAP ADT responded HTTP 200 — connection OK

All checks passed. You are ready to connect to Claude Code.

If any check fails, the script tells you exactly what to fix.

6. Register with Claude Code

.mcp.json was created by npm run setup and is ready to use as a project-level config (active when Claude Code is opened in this folder).

For user-level registration (active in all sessions), copy the server entry into ~/.claude/mcp.json.

Restart Claude Code after registering — MCP servers load at startup.

7. Confirm tools are available

In Claude Code, ask:

What SAP transport tools do you have available?

Claude should list all 8 tools. If not, see troubleshooting.md.

8. First test with DRY_RUN

Set DRY_RUN=true in .env, rebuild, and try the tools — read tools work normally, write tools are blocked safely:

# .env → DRY_RUN=true
npm run build

Set back to false when ready for live writes.


Available Tools

Read Tools

ToolDescription
transport_list_systemsList configured SAP systems
transport_list_requestsList transport requests (filter by owner/status)
transport_get_requestFull transport details: tasks, objects, status
transport_list_objectsABAP objects in a transport
transport_check_import_queuePending imports on a target system

Write Tools

ToolDescriptionRisk
transport_create_requestCreate a new transport requestLow
transport_release_requestRelease transport for importHigh — irreversible
transport_delete_requestDelete an unreleased transportHigh

Standard Workflow

1. transport_list_systems       → confirm systemId values
2. transport_list_requests      → find open transports
3. transport_get_request        → inspect contents
4. transport_list_objects       → verify ABAP objects
5. transport_check_import_queue → check target system queue
6. [user confirms]
7. transport_release_request    → release with policy checks + verify

See examples/release-workflow.md for a full walkthrough.


Multi-System Setup (DEV / QA / PRD)

Set SYSTEMS_CONFIG in .env:

SYSTEMS_CONFIG=[
  {"id":"DEV","hostname":"dev.sap.co","sysnr":"00","client":"100","language":"EN","isDefault":true},
  {"id":"QA","hostname":"qa.sap.co","sysnr":"01","client":"200","language":"EN","isDefault":false}
]

Every tool accepts an optional systemId parameter. Omit it to use the default system.


Governance Rules

  • Release is irreversible — Claude requires explicit user confirmation + shows full object list
  • Empty transports (0 objects) cannot be released
  • Released transports cannot be deleted
  • Transport description must be ≥10 characters
  • All writes are audit-logged (stderr JSON with timestamp, transport number, object count)
  • DRY_RUN=true blocks all write tools — use for testing

See docs/governance.md for full policy details.


Troubleshooting

See docs/troubleshooting.md for:

  • Auth failures (Basic/certificate)
  • Connection errors (VPN, port, ICF activation)
  • CSRF token issues
  • Policy violation errors

Reference

Ver o original no GitHub

Bom para

Relacionados