能力标签

🔌 MCP 🤖 Agent 🔄 工作流 🐳 Docker 💻 CLI 📚 RAG 🧠 Claude

🔌

MCP工具

开源MCP工具：ABAP ADT

基于 TypeScript · 让 AI 助手直接操作你的系统与工具

英文名：mcp-abap-adt

⭐ 53 Stars 🍴 16 Forks 💻 TypeScript 📄 MIT 🏷 AI 7.5分

7.5AI 综合评分

mcpabapabap-cloudadtbtpcrudtypescript

⬇ 下载源码 ZIP ⚙️ 配置说明

✦ AI Skill Hub 推荐

AI Skill Hub 推荐使用：开源MCP工具：ABAP ADT 是一款优质的MCP工具。AI 综合评分 7.5 分，在同类工具中表现稳健。如果你正在寻找可靠的MCP工具解决方案，这是一个值得深入了解的选择。

📚 深度解析

开源MCP工具：ABAP ADT 是一款基于 MCP（Model Context Protocol）标准协议的 AI 工具扩展。MCP 协议由 Anthropic 开发并开源，旨在建立 AI 模型与外部工具之间的标准化通信接口，目前已被 Claude Desktop、Claude Code、Cursor 等主流 AI 工具采纳。

通过安装开源MCP工具：ABAP ADT，你的 AI 助手将获得额外的工具调用能力，可以用自然语言直接操控该工具的功能，无需学习复杂的命令行语法。MCP 工具的核心价值在于"一次配置，永久增强"——配置完成后，每次与 AI 对话时都可以无缝调用这些工具。

在技术实现上，MCP 工具通过标准的 JSON-RPC 协议与 AI 客户端通信，工具的功能以"工具列表"的形式暴露给 AI 模型，AI 可以按需调用。开源MCP工具：ABAP ADT 提供了结构化的工具调用接口，使 AI 模型能够精确地理解和使用每个功能点，显著降低 AI 在工具使用上的错误率。

与传统的 API 集成相比，MCP 工具的优势在于无需编写代码——用户只需在配置文件中添加几行 JSON，即可让 AI 获得全新能力。AI Skill Hub 将开源MCP工具：ABAP ADT 评为 AI 评分 7.5 分，属于同类工具中的优质选择。

📋 工具概览

开源MCP工具：ABAP ADT 是一款遵循 MCP（Model Context Protocol）标准协议的 AI 工具扩展。通过 MCP 协议，它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务，实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用，都可以通过自然语言在 AI 对话中直接触发，极大提升生产效率。

GitHub Stars

⭐ 53

开发语言

TypeScript

支持平台

Windows / macOS / Linux

维护状态

轻量级项目，按需更新

开源协议

MIT

AI 综合评分

7.5 分

工具类型

MCP工具

Forks

📖 中文文档

以下内容由 AI Skill Hub 根据项目信息自动整理，如需查看完整原始文档请访问底部「原始来源」。

📌 核心特色

通过标准 MCP 协议与 Claude、Cursor 等主流 AI 客户端深度集成
提供结构化工具调用接口，显著降低 AI 集成复杂度
支持 Claude Desktop 和 Claude Code 无缝接入，开箱即用
可与其他 MCP 工具组合叠加，构建完整 AI 工作站
轻量无侵入设计，不影响现有系统架构

🎯 主要使用场景

在 Claude Desktop 对话中直接调用本地工具，实现 AI 与系统的深度联动
通过自然语言驱动复杂的多步骤自动化任务，代替繁琐手动操作
将多个 MCP 工具组合使用，构建个人专属 AI 工作站

以下安装命令基于项目开发语言和类型自动生成，实际以官方 README 为准。

安装命令

# 方式一：通过 Claude Code CLI 一键安装
claude skill install https://github.com/fr0ster/mcp-abap-adt

# 方式二：手动配置 claude_desktop_config.json
{
  "mcpServers": {
    "--mcp---abap-adt": {
      "command": "npx",
      "args": ["-y", "mcp-abap-adt"]
    }
  }
}

# 配置文件位置
# macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
# Windows: %APPDATA%/Claude/claude_desktop_config.json

📋 安装步骤说明

确认已安装 Node.js（v18 或以上版本）
打开 Claude Desktop 或 Claude Code 的 MCP 配置文件
按「交给 Agent 安装 → Claude Desktop」标签中的 JSON 配置填入 mcpServers 字段
保存配置文件并重启 Claude 客户端
重启后，在对话中即可使用本工具

以下用法示例由 AI Skill Hub 整理，涵盖最常见的使用场景。

常用命令 / 代码示例

# 安装后在 Claude 对话中直接使用
# 示例：
用户: 请帮我用 开源MCP工具：ABAP ADT 执行以下任务...
Claude: [自动调用 开源MCP工具：ABAP ADT MCP 工具处理请求]

# 查看可用工具列表
# 在 Claude 中输入："列出所有可用的 MCP 工具"

以下配置示例基于典型使用场景生成，具体参数请参照官方文档调整。

配置示例

// claude_desktop_config.json 配置示例
{
  "mcpServers": {
    "__mcp___abap_adt": {
      "command": "npx",
      "args": ["-y", "mcp-abap-adt"],
      "env": {
        // "API_KEY": "your-api-key-here"
      }
    }
  }
}

// 保存后重启 Claude Desktop 生效

📑 README 深度解析真实文档完整度 75/100 查看 GitHub 原文 →

以下内容由系统直接从 GitHub README 解析整理，保留代码块、表格与列表结构。

<img src="logo.png" alt="mcp-abap-adt logo" width="36" align="absmiddle" /> mcp-abap-adt: Your Gateway to ABAP Development Tools (ADT)

mcp-abap-adt is an MCP server for ABAP ADT in SAP ECC/S/4HANA (on-premise) and SAP BTP ABAP Cloud systems. It gives agents controlled access to real ABAP repositories through ADT, so analysis and changes are grounded in system data instead of assumptions. It is built for AI-assisted pair programming (AIPNV: AI Pairing, Not Vibing), not autopilot vibe coding.

Primary workflows: - Deep ABAP analysis: where-used, object metadata, repository navigation, object structure, semantic analysis, dependency and impact exploration. - High-level ABAP development: rapid CRUD and iterative updates for RAP and classic ABAP artifacts (classes, interfaces, function groups/modules, programs, DDIC, CDS/view/service artifacts), validated through ADT flows.

Why teams use it: - Full CRUD (not read-only): create, read, update, and delete ABAP artifacts - Works with On-Premise (ECC/S/4HANA), ABAP Cloud (BTP), and Legacy systems (BASIS < 7.50) - JWT/XSUAA, service key (destination-based), and RFC authorization - Multiple transports: stdio, HTTP, SSE - Rich tool surface for ABAP objects, metadata, transports, and search

Authorization & Destinations (Important): A destination is the filename of a service key stored locally. You place service keys in the service-keys directory, and use --mcp=<destination> to select which one to use. This is the primary auth model for on‑prem and BTP systems. See Authentication & Destinations.

You can configure MCP clients either manually (JSON/TOML) or via the configurator CLI (@mcp-abap-adt/configurator, repo: mcp-abap-adt-conf).

Capabilities (High-Level Focus)

Key examples of high-value workflows and tools:

Repository and impact analysis: GetWhereUsed, DescribeByList, GetObjectStructure, GetObjectInfo, SearchObject, GetPackageTree, GetPackageContents
Code and semantic introspection: GetAbapAST, GetAbapSemanticAnalysis, GetIncludesList, GetProgFullCode
RAP development: CreateBehaviorDefinition, UpdateBehaviorDefinition, CreateBehaviorImplementation, UpdateBehaviorImplementation, CreateServiceDefinition, UpdateServiceDefinition, CreateMetadataExtension, UpdateMetadataExtension
CDS/View development: CreateView, UpdateView, GetView, DeleteView
ABAP OO CRUD: CreateClass, UpdateClass, GetClass, DeleteClass, CreateInterface, UpdateInterface, GetInterface, DeleteInterface
Function module/group CRUD: CreateFunctionGroup, UpdateFunctionGroup, GetFunctionGroup, DeleteFunctionGroup, CreateFunctionModule, UpdateFunctionModule, GetFunctionModule, DeleteFunctionModule
Transport and activation support: CreateTransport, GetTransport, ActivateObject

Features

🏗️ Domain Management: GetDomain, CreateDomain, UpdateDomain - Create, retrieve, and update ABAP domains
📊 Data Element Management: GetDataElement, CreateDataElement, UpdateDataElement - Create, retrieve, and update ABAP data elements
📦 Table Management: GetTable, CreateTable, GetTableContents - Create and retrieve ABAP database tables with data preview
🏛️ Structure Management: GetStructure, CreateStructure - Create and retrieve ABAP structures
👁️ View Management: GetView, CreateView, UpdateView - Create and manage CDS Views and Classic Views
🎓 Class Management: GetClass, CreateClass, UpdateClass - Create, retrieve, and update ABAP classes
📝 Program Management: GetProgram, CreateProgram, UpdateProgram - Create, retrieve, and update ABAP programs
🔧 Behavior Definition (BDEF) Management: GetBehaviorDefinition, CreateBehaviorDefinition, UpdateBehaviorDefinition - Create and manage ABAP Behavior Definitions with support for Managed, Unmanaged, Abstract, and Projection types
📋 Metadata Extension (DDLX) Management: CreateMetadataExtension, UpdateMetadataExtension - Create and manage ABAP Metadata Extensions
⚡ Activation: ActivateObject - Universal activation for any ABAP object
🚚 Transport Management: CreateTransport, GetTransport - Create and retrieve transport requests
🔍 Enhancement Analysis: GetEnhancements, GetEnhancementImpl, GetEnhancementSpot - Enhancement discovery and analysis
📋 Include Management: GetIncludesList - Recursive include discovery
🔍 System Tools: GetInactiveObjects - Monitor inactive objects waiting for activation
🧪 Runtime Diagnostics: RuntimeCreateProfilerTraceParameters, RuntimeListProfilerTraceFiles, RuntimeGetProfilerTraceData, RuntimeGetDumpById - Profiling and dump analysis with JSON payloads
📡 Runtime Feeds: RuntimeListFeeds, RuntimeListSystemMessages, RuntimeGetGatewayErrorLog - Feed reader (dumps, system messages, gateway errors), SM02 system messages, Gateway error log
🚀 SAP BTP Support: JWT/XSUAA authentication with browser-based token helper
🔑 Destination-Based Authentication: Service key-based authentication with automatic token management (see Client Configuration)
💾 Freestyle SQL: GetSqlQuery - Execute custom SQL queries via ADT Data Preview API

ℹ️ ABAP Cloud limitation: Direct ADT data preview of database tables is blocked by SAP BTP backend policies. The server returns a descriptive error when attempting such operations. On-premise systems continue to support data preview.

Dependencies

This project uses two npm packages:

@mcp-abap-adt/connection – connection/auth/session layer
@mcp-abap-adt/adt-clients – Builder-first ADT clients

These packages are automatically installed via npm install and are published to npm.

---

Use stdio mode (for MCP clients, requires .env file or --mcp parameter)

mcp-abap-adt --transport=stdio

SSE mode (requires .env file or --mcp parameter)

mcp-abap-adt --transport=sse --sse-port=3001

Getting Started

Install the server and configure your client using the configurator:

```bash npm install -g @mcp-abap-adt/core npm install -g @mcp-abap-adt/configurator

Global Installation (Recommended)

After installing globally with npm install -g, you can run from any directory:

```bash

Build and run locally

npm run build npm start

Install the connection package globally (one-time setup)

npm install -g @mcp-abap-adt/connection

Building

npm run build

Quick Start

1. Install server: See Installation Guide 2. Configure client (auto): Use mcp-conf from @mcp-abap-adt/configurator (repo: mcp-abap-adt-conf, docs: CLIENT_INSTALLERS.md) 3. Configure client (manual): See Client Configuration 4. Use: - Read-Only Tools - High-Level Tools - Low-Level Tools - Legacy System Tools

Use Cases

Impact analysis / where-used before changes: map object usage and probable blast radius.
Dependency audit: inspect links across classes, interfaces, DDIC, CDS/views, and RAP artifacts.
Migration and cleanup prep: extract repository facts to plan refactoring or cloud-readiness work.
RAP and ABAP iterative development: create/update artifacts quickly with ADT-backed operations.
Automated documentation and RAG ingestion: pull structured facts from ABAP systems for downstream tooling.

SAP_KERBEROS_SPN=HTTP@mysaphost.corp.example

Default HTTP mode (works without .env file)

mcp-abap-adt

Use env destination from platform sessions store

mcp-abap-adt --env=trial

Use explicit .env file path

mcp-abap-adt --env-path=/path/to/my.env

Environment Configuration

Env resolution: 1. --env-path=<path|file> (or MCP_ENV_PATH) for explicit .env file. - Absolute path: used as-is. - Relative path or file name only (e.g. my.env): resolved from current working directory. 2. --env=<destination> for destination file in standard sessions store: - Unix: ~/.config/mcp-abap-adt/sessions/<destination>.env - Windows: %USERPROFILE%\\Documents\\mcp-abap-adt\\sessions\\<destination>.env 3. Fallback to .env in current working directory.

Example .env file:

SAP_URL=https://your-sap-system.com
SAP_CLIENT=100
SAP_AUTH_TYPE=basic
SAP_USERNAME=your-username
SAP_PASSWORD=your-password

For JWT authentication (SAP BTP):

SAP_URL=https://your-btp-system.com
SAP_CLIENT=100
SAP_AUTH_TYPE=jwt
SAP_JWT_TOKEN=your-jwt-token

For RFC connection:

SAP_URL=https://your-legacy-system.com
SAP_CLIENT=100
SAP_AUTH_TYPE=basic
SAP_USERNAME=your-username
SAP_PASSWORD=your-password
SAP_CONNECTION_TYPE=rfc

See RFC Setup Guide for prerequisites (SAP NW RFC SDK).

For client certificate (mTLS) authentication — on-prem HTTP only: ```bash SAP_URL=https://your-sap-system.com SAP_AUTH_TYPE=certificate

Optional: explicit SPN (default: HTTP@<host>)

Optional: service class used to derive the SPN when SAP_KERBEROS_SPN is unset (default: HTTP)

Generate .env file from service key JSON

mcp-auth auth -k path/to/service-key.json ```

This will automatically create/update .env file with JWT tokens and connection details.

.env comments rule: only full-line comments are supported (lines that start with #). Inline comments are not parsed, so keep comments on separate lines.

Claude recommendation: place the service key in the service-keys directory and use --mcp=<destination> (avoid manual JWT tokens).

Command-Line Options

Authentication: - --auth-broker - Force use of auth-broker (service keys), ignore .env file - --auth-broker-path=<path> - Custom path for auth-broker service keys and sessions - --browser-auth-port=<port> - Override OAuth browser callback port (default: 5000 for HTTP, 4000 for SSE, 4001 for stdio) - --connection-type=<http|rfc> - SAP connection transport: http (default) or rfc - --unsafe - Enable file-based session storage (persists tokens to disk). By default, sessions are stored in-memory (secure, lost on restart)

When --mcp=<destination> is specified, automatic fallback loading of ./.env is skipped.

Examples: ```bash

2. Embeddable Server (For Integration)

Embed MCP server into existing applications (e.g., SAP CAP/CDS, Express):

import {
  EmbeddableMcpServer,
  ReadVsGetDedupStrategy, // optional: hide Read<X> when Get<X> also exposed
} from '@mcp-abap-adt/core/server';

const server = new EmbeddableMcpServer({
  connection,              // Your AbapConnection instance
  logger,                  // Optional logger
  exposition: ['readonly', 'high'],  // Handler groups to expose
  // Optional; default: no dedup — existing consumers see no change.
  readOnlyDedupStrategy: new ReadVsGetDedupStrategy(),
});
await server.connect(transport);

See Handlers Management → EmbeddableMcpServer dedup strategies for opt-in dedup of readonly tools against high/low/compact, including how to plug a custom IReadOnlyDedupStrategy for role-based rules.