convez.ai
MCP ServerIntegração & APIsAvançado
Nidhideep

ABAP ADT MCP Server

Nidhideep/sap-abap-rap-mcp

Desenvolvimento ABAP e RAP governado via agentes de IA

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP que fornece acesso controlado ao desenvolvimento ABAP via API REST ADT (ABAP Development Tools). Permite ler e escrever código-fonte, inspecionar o dicionário de dados, construir artefatos RAP e publicar serviços OData em sistemas SAP diretamente de clientes MCP como Claude.

Instalação

$npx convez-ai Nidhideep/sap-abap-rap-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
28%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Criar serviços OData completos (tabela → CDS → service binding → publicação) em uma conversa
  • Gerar programas ABAP, classes e interfaces automaticamente
  • Explorar e modificar objetos do dicionário de dados SAP (tabelas, estruturas, domínios)

Veredito

Ferramenta especializada para desenvolvimento SAP ABAP/RAP com bom isolamento de governança (dry-run, audit log). Demanda conhecimento técnico SAP e configuração segura de credenciais, mas oferece automação significativa em fluxos de desenvolvimento.

README

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

ABAP ADT MCP Server

An MCP server that gives AI agents governed access to SAP ABAP development via the ADT (ABAP Development Tools) REST API. Read and write source code, inspect the data dictionary, build RAP artifacts, and publish OData services — across SAP systems, from any MCP-capable client (Claude Code, Claude Desktop, Cursor, …).

Build a complete OData service — table → CDS views → service definition → service binding → published endpoint — in a single conversation. No SAP GUI, no hand-written ABAP.

Features

  • 45 tools across source code, DDIC, RAP, and service bindings
  • Read: programs, classes, interfaces, function modules, CDS views, tables, structures, data elements, domains — plus data previews and SQL
  • Write: create/change programs, classes, interfaces, CDS views, tables, domains, data elements; create/activate RAP service definitions and OData service bindings; publish
  • Governance built in: a policy layer with a DRY_RUN guard and an audit log on every write; reads and writes are clearly separated

Quick start

git clone <your-fork-url> abap-adt-mcp-server
cd abap-adt-mcp-server
npm install
npm run build
cp .env.example .env      # then fill in your SAP connection

Register it with your MCP client (user scope, available everywhere):

claude mcp add --scope user abap-adt node "$(pwd)/dist/src/index.js"

Or add to your client config manually:

{
  "mcpServers": {
    "abap-adt": { "command": "node", "args": ["/abs/path/dist/src/index.js"] }
  }
}

Configuration

Copy .env.example to .env and set:

VariableDescription
SAP_BASE_URLBase URL of the SAP system (e.g. https://host:44301)
SAP_CLIENTClient (e.g. 100)
AUTH_METHODbasic (recommended for ADT) or token
SAP_USERNAME / SAP_PASSWORDCredentials for basic auth
DRY_RUNtrue blocks all write tools (safe exploration)
DEFAULT_PACKAGEPackage for new objects ($TMP for local)

.env is gitignored — never commit credentials.

Tools

Source & DDIC (read): get_abap_program, get_class, get_interface, get_function_module, get_function_group, get_include, get_cds_view, get_cds_extension, get_structure, get_structure_fields, get_table, get_table_fields, get_data_element, get_domain, preview_cds_view, preview_table_data

Create / change: create_abap_program, change_abap_program, create_abap_class, change_abap_class, create_interface, change_interface, create_cds_view, change_cds_view, delete_cds_view, create_cds_extension, change_structure, create_domain, create_data_element, create_table

Execute: execute_program, execute_sql, fetch_st22_dumps, get_csrf_token

RAP & services: get_behavior_definition, create_behavior_definition, save_behavior_definition, delete_behavior_definition, get_service_definition, create_service_definition, save_service_definition, get_binding_details, create_service_binding, publish_service_binding, unpublish_service_binding

Example: an OData service in one prompt

Build an equipment-maintenance OData service in $TMP: a table with maintenance id, equipment, date, technician, status; an interface CDS view over it; a read-only consumption view; a service definition exposing it; an OData V2 UI binding; then publish.

The agent calls create_table → create_cds_view ×2 → create_service_definition → create_service_binding → publish_service_binding, and returns the live $metadata URL.

Status & limitations

  • OData V2, read-only services are fully supported end to end.
  • Transactional behavior (RAP managed BO + OData V4) needs an SAP system with the RAP generator (S/4HANA 2023+ / BTP ABAP).
  • Objects default to $TMP (local); set DEFAULT_TRANSPORT for transportable packages.

Security

This server can modify SAP objects. Use a development system, a dedicated technical user with least-privilege authorizations, and DRY_RUN=true while exploring. Review the audit log output. Do not point it at production without appropriate controls.

License

MIT

Ver o original no GitHub

Bom para

Relacionados