原型 · 预览版：收录官方注册中心里的全部服务器，每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚
☰ 菜单中文 设置
新手模式 开
配色跟随系统浅色纯白深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch

abap2UI5

作者：abap2UI5版本 1.0.0i★ 1i在你的电脑上运行
注册名称io.github.abap2UI5/mcp-server

安装方法

What it does

abap2UI5 dev loop for AI agents: validate views, screenshot, deploy and run apps - no SAP system

  • Connects 在你的电脑上运行
  • Account or key Needs A2UI5_MCP_SYSTEM_PASSWORD, A2UI5_MCP_SYSTEM_PASSWORD_CMD
  • Category 网页与浏览器

安装

选择你使用的 AI 应用，然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步：你用哪个 AI？

选择你用的应用，步骤会显示在下方。

可连接 Claude，但需要先准备

需要 abap2UI5 的密钥（在开发者网站创建） · 需要先在电脑上安装 Node.js（只需一次） · 仅限电脑上的 Claude 应用（Windows 或 Mac），网页和手机不可用

  1. 安装 Node.js

    只需一次，所有需要 Node.js 的服务器都能用

    打开 Node.js 下载页 ↗

  2. 注册并创建 abap2UI5 的密钥

    打开开发者网站，注册账户并创建 API 密钥，下一步要用。价格和免费方案请看开发者网站。

    打开 abap2UI5 网站 ↗

  3. 打开电脑版 Claude 应用的设置文件

    SettingsDeveloperEdit Config

  4. 粘贴这些设置并保存文件

    正在检查命令 · 通过后才会显示复制按钮

    只把密钥粘贴到应用的输入框里，不要粘贴到聊天中或发给任何人

  5. 退出 Claude 再重新打开

  6. 试一试

    用 abap2UI5 告诉我你能帮我做什么，然后做一件给我看

    ✓ 如果 Claude 说正在使用 abap2UI5，或回答中出现 abap2UI5 的工具名称，就表示连接成功

35 项可选设置（不填也能用）

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • AI_VIEW_CHECK_HOME Checkout or install of @abap2ui5/linter (validate_view, fix_view, screenshot_view). Default: the peer npm installs beside the server. A set value is authoritative.
  • A2UI5_HOME abap2UI5 framework checkout (app_guide, api_reference, pitfalls; backend when present). Default: ../abap2UI5, else the GitHub mirror and the npm runtime.
  • SAMPLES_CONTROLS_HOME samples-controls checkout (capabilities, examples, generation_rules, scope_of, UI5 for screenshots). Default: ../samples-controls, else the GitHub mirror.
  • SAMPLES_HOME abap2UI5/samples checkout, one of the catalogues examples searches. Default: ../samples, else the GitHub mirror.
  • SAMPLES_STACK_HOME abap2UI5/samples-stack checkout (OData, RAP, APC, launchpad samples). Default: ../samples-stack, else the GitHub mirror.
  • APP_TEMPLATE_HOME abap2UI5/app-template checkout that scaffold_app serves and add_agent_setup executes. Default: ../app-template, else the GitHub mirror.
  • DOCS_HOME abap2UI5/docs checkout that docs_search reads. Default: ../docs, else the GitHub mirror.
  • ABAP_CLOUD_GUI_HOME abap2UI5-addons/abap-cloud-gui checkout (with npm ci done) whose report2cloud converter migrate_report runs. Default: ../abap-cloud-gui; no mirror.
  • POPUPS_HOME abap2UI5-addons/popups checkout whose popups migrate_report with deploy: true writes into the dev sandbox beside the converted class. Default: .deps/popups of the abap-cloud-gui checkout, ../popups b…
  • OPENUI5_SRC OpenUI5 source checkout scope_of reads the JSDoc from (via samples-controls). Default: ../fork-openui5 next to samples-controls.
  • A2UI5_MCP_WORKSPACE Where the npm backend installs, the dev sandbox lives and a framework clone lands. Default: ~/.abap2ui5-mcp.
  • A2UI5_MCP_BACKEND Which backend runs the apps: npm (the @abap2ui5/node-runtime package, even beside a checkout) or clone (clone the framework). Default: decided per call.
  • A2UI5_MCP_RUNTIME_VERSION Pin the @abap2ui5/node-runtime release (X.Y.Z) the npm backend installs. Default: the registry's latest.
  • A2UI5_MCP_PORT Port of the local backend run_app boots against. Default: 3000.
  • A2UI5_MCP_UI Whether app_start/app_describe/app_act declare their MCP Apps screen (ui://abap2ui5/app-screen): auto (default - when the client advertises the io.modelcontextprotocol/ui extension), on, off.
  • A2UI5_MCP_APP_FORMAT The default answer format of the app tools: snapshot (default) or adaptive-card (the snapshot plus an Adaptive Card 1.5 as an embedded resource, for card-rendering hosts).
  • A2UI5_MCP_OFFLINE Set to 1 for no network: no UI5 CDN fallback, no GitHub mirror, no registry lookup.
  • A2UI5_MCP_REMOTE Set to 0 to switch off the read-only GitHub mirror used when no checkout is found.
  • A2UI5_MCP_REMOTE_DIR Cache directory of the GitHub mirror. Default: /abap2ui5-mcp-remote.
  • A2UI5_MCP_REMOTE_TTL_MS How long a mirrored copy is used before it is refreshed, in milliseconds. Default: one day.
  • A2UI5_MCP_UI5_CACHE_MB How many MB of UI5 answers from the CDN (sdk.openui5.org) run_app and interact_app keep in memory across calls, so a second boot does not download them again. 0 switches the cache off. Default: 64.
  • A2UI5_MCP_RENDER_PAGES Pages (Chromium tabs) of validate_view's warm render gate, which concurrent calls queue on. Default: 2 (1 to 8).
  • A2UI5_MCP_CHROMIUM Chromium binary for run_app and interact_app. Default: CHROMIUM_BIN, Playwright's managed browser, then a system chromium.
  • A2UI5_MCP_SCREENSHOT_DIR Where run_app and interact_app write their PNGs (the newest 50 are kept) and build_backend its log. Default: /abap2ui5-mcp-screenshots.
  • A2UI5_MCP_PREBUILT_URL Where build_backend mode prebuilt downloads the backend from. Default: the framework's release asset.
  • A2UI5_MCP_LINT_WORKER Set to 0 to run every lint as a fresh abaplint process. Default: a long-lived worker keeps @abaplint/core with the framework parsed and lints a deploy in milliseconds (the CLI runs whenever the worke…
  • A2UI5_MCP_LINT_IDLE_MS How long the warm lint worker (about 300 MB with the framework parsed) is kept without a request before it exits, in milliseconds; the next lint starts a fresh one. 0 keeps it for the server's life.…
  • A2UI5_MCP_LINT_TIMEOUT_MS Hard timeout of the abaplint run, in milliseconds. Default: 5 minutes.
  • A2UI5_MCP_SCOPE_TIMEOUT_MS Hard timeout of scope_of, in milliseconds. Default: 5 minutes.
  • A2UI5_MCP_BUILD_TIMEOUT_MS Hard timeout of a build, the prebuilt download and the npm install, in milliseconds. Default: 30 minutes.
  • A2UI5_MCP_UNIT_TIMEOUT_MS Hard timeout of the ABAP Unit runner, in milliseconds. Default: 10 minutes.
  • A2UI5_MCP_SYSTEM_URL Switches on the SYSTEM MODE: the app tools against this real SAP system instead of the sandbox loop. The launch URL, e.g. https://host:44300/sap/bc/z2ui5?app_start={class}&sap-client=100.
  • A2UI5_MCP_SYSTEM_USER System mode: the SAP user the app tools log on with (Basic authentication).
  • A2UI5_MCP_SYSTEM_INSECURE_TLS System mode: set to 1 to accept a certificate that cannot be verified. NODE_EXTRA_CA_CERTS with the CA is the better fix.
  • GITHUB_TOKEN Optional token sent to api.github.com only, to raise the rate limit of the docs tree listing (GH_TOKEN is read too).

说明仍为英文原文。

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 abap2UI5

abap2UI5 需要安装在你的电脑上，而 ChatGPT 只能连接在网上运行的服务器

你可以改用这些方式

A · 使用能连接 abap2UI5 的应用

  • 需要 abap2UI5 的密钥（在开发者网站创建） · 需要先在电脑上安装 Node.js（只需一次） · 仅限电脑上的 Claude 应用（Windows 或 Mac），网页和手机不可用
  • 需要 abap2UI5 的密钥（在开发者网站创建） · 需要先在电脑上安装 Node.js（只需一次）
  • 需要 abap2UI5 的密钥（在开发者网站创建） · 需要先在电脑上安装 Node.js（只需一次）
  • 需要 abap2UI5 的密钥（在开发者网站创建） · 需要先在电脑上安装 Node.js（只需一次）

B · 网页与浏览器 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选，仅限用地址即可连接、无需密钥的

可连接 Claude Code，但需要先准备

需要 abap2UI5 的密钥（在开发者网站创建） · 需要先在电脑上安装 Node.js（只需一次）

  1. 安装 Node.js

    只需一次，所有需要 Node.js 的服务器都能用

    打开 Node.js 下载页 ↗

  2. 注册并创建 abap2UI5 的密钥

    打开开发者网站，注册账户并创建 API 密钥，下一步要用。价格和免费方案请看开发者网站。

    打开 abap2UI5 网站 ↗

  3. 打开终端

    Mac：按 Command+空格，输入 Terminal · Windows：打开 PowerShell

  4. 粘贴这条命令并按 Enter

    正在检查命令 · 通过后才会显示复制按钮

    按 Enter 前，把“your-value”改成你的密钥

    只把密钥粘贴到应用的输入框里，不要粘贴到聊天中或发给任何人

  5. 在 Claude Code 中输入 /mcp

    应能看到 abap2UI5 在列表中并显示已连接

  6. 试一试

    用 abap2UI5 告诉我你能帮我做什么，然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 abap2UI5，或回答中出现 abap2UI5 的工具名称，就表示连接成功

35 项可选设置（不填也能用）

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • AI_VIEW_CHECK_HOME Checkout or install of @abap2ui5/linter (validate_view, fix_view, screenshot_view). Default: the peer npm installs beside the server. A set value is authoritative.
  • A2UI5_HOME abap2UI5 framework checkout (app_guide, api_reference, pitfalls; backend when present). Default: ../abap2UI5, else the GitHub mirror and the npm runtime.
  • SAMPLES_CONTROLS_HOME samples-controls checkout (capabilities, examples, generation_rules, scope_of, UI5 for screenshots). Default: ../samples-controls, else the GitHub mirror.
  • SAMPLES_HOME abap2UI5/samples checkout, one of the catalogues examples searches. Default: ../samples, else the GitHub mirror.
  • SAMPLES_STACK_HOME abap2UI5/samples-stack checkout (OData, RAP, APC, launchpad samples). Default: ../samples-stack, else the GitHub mirror.
  • APP_TEMPLATE_HOME abap2UI5/app-template checkout that scaffold_app serves and add_agent_setup executes. Default: ../app-template, else the GitHub mirror.
  • DOCS_HOME abap2UI5/docs checkout that docs_search reads. Default: ../docs, else the GitHub mirror.
  • ABAP_CLOUD_GUI_HOME abap2UI5-addons/abap-cloud-gui checkout (with npm ci done) whose report2cloud converter migrate_report runs. Default: ../abap-cloud-gui; no mirror.
  • POPUPS_HOME abap2UI5-addons/popups checkout whose popups migrate_report with deploy: true writes into the dev sandbox beside the converted class. Default: .deps/popups of the abap-cloud-gui checkout, ../popups b…
  • OPENUI5_SRC OpenUI5 source checkout scope_of reads the JSDoc from (via samples-controls). Default: ../fork-openui5 next to samples-controls.
  • A2UI5_MCP_WORKSPACE Where the npm backend installs, the dev sandbox lives and a framework clone lands. Default: ~/.abap2ui5-mcp.
  • A2UI5_MCP_BACKEND Which backend runs the apps: npm (the @abap2ui5/node-runtime package, even beside a checkout) or clone (clone the framework). Default: decided per call.
  • A2UI5_MCP_RUNTIME_VERSION Pin the @abap2ui5/node-runtime release (X.Y.Z) the npm backend installs. Default: the registry's latest.
  • A2UI5_MCP_PORT Port of the local backend run_app boots against. Default: 3000.
  • A2UI5_MCP_UI Whether app_start/app_describe/app_act declare their MCP Apps screen (ui://abap2ui5/app-screen): auto (default - when the client advertises the io.modelcontextprotocol/ui extension), on, off.
  • A2UI5_MCP_APP_FORMAT The default answer format of the app tools: snapshot (default) or adaptive-card (the snapshot plus an Adaptive Card 1.5 as an embedded resource, for card-rendering hosts).
  • A2UI5_MCP_OFFLINE Set to 1 for no network: no UI5 CDN fallback, no GitHub mirror, no registry lookup.
  • A2UI5_MCP_REMOTE Set to 0 to switch off the read-only GitHub mirror used when no checkout is found.
  • A2UI5_MCP_REMOTE_DIR Cache directory of the GitHub mirror. Default: /abap2ui5-mcp-remote.
  • A2UI5_MCP_REMOTE_TTL_MS How long a mirrored copy is used before it is refreshed, in milliseconds. Default: one day.
  • A2UI5_MCP_UI5_CACHE_MB How many MB of UI5 answers from the CDN (sdk.openui5.org) run_app and interact_app keep in memory across calls, so a second boot does not download them again. 0 switches the cache off. Default: 64.
  • A2UI5_MCP_RENDER_PAGES Pages (Chromium tabs) of validate_view's warm render gate, which concurrent calls queue on. Default: 2 (1 to 8).
  • A2UI5_MCP_CHROMIUM Chromium binary for run_app and interact_app. Default: CHROMIUM_BIN, Playwright's managed browser, then a system chromium.
  • A2UI5_MCP_SCREENSHOT_DIR Where run_app and interact_app write their PNGs (the newest 50 are kept) and build_backend its log. Default: /abap2ui5-mcp-screenshots.
  • A2UI5_MCP_PREBUILT_URL Where build_backend mode prebuilt downloads the backend from. Default: the framework's release asset.
  • A2UI5_MCP_LINT_WORKER Set to 0 to run every lint as a fresh abaplint process. Default: a long-lived worker keeps @abaplint/core with the framework parsed and lints a deploy in milliseconds (the CLI runs whenever the worke…
  • A2UI5_MCP_LINT_IDLE_MS How long the warm lint worker (about 300 MB with the framework parsed) is kept without a request before it exits, in milliseconds; the next lint starts a fresh one. 0 keeps it for the server's life.…
  • A2UI5_MCP_LINT_TIMEOUT_MS Hard timeout of the abaplint run, in milliseconds. Default: 5 minutes.
  • A2UI5_MCP_SCOPE_TIMEOUT_MS Hard timeout of scope_of, in milliseconds. Default: 5 minutes.
  • A2UI5_MCP_BUILD_TIMEOUT_MS Hard timeout of a build, the prebuilt download and the npm install, in milliseconds. Default: 30 minutes.
  • A2UI5_MCP_UNIT_TIMEOUT_MS Hard timeout of the ABAP Unit runner, in milliseconds. Default: 10 minutes.
  • A2UI5_MCP_SYSTEM_URL Switches on the SYSTEM MODE: the app tools against this real SAP system instead of the sandbox loop. The launch URL, e.g. https://host:44300/sap/bc/z2ui5?app_start={class}&sap-client=100.
  • A2UI5_MCP_SYSTEM_USER System mode: the SAP user the app tools log on with (Basic authentication).
  • A2UI5_MCP_SYSTEM_INSECURE_TLS System mode: set to 1 to accept a certificate that cannot be verified. NODE_EXTRA_CA_CERTS with the CA is the better fix.
  • GITHUB_TOKEN Optional token sent to api.github.com only, to raise the rate limit of the docs tree listing (GH_TOKEN is read too).

说明仍为英文原文。

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor，但需要先准备

需要 abap2UI5 的密钥（在开发者网站创建） · 需要先在电脑上安装 Node.js（只需一次）

  1. 安装 Node.js

    只需一次，所有需要 Node.js 的服务器都能用

    打开 Node.js 下载页 ↗

  2. 注册并创建 abap2UI5 的密钥

    打开开发者网站，注册账户并创建 API 密钥，下一步要用。价格和免费方案请看开发者网站。

    打开 abap2UI5 网站 ↗

  3. 点击这个按钮打开 Cursor

    正在检查命令 · 通过后才会显示复制按钮

  4. 填写你的密钥

    在 abap2UI5 的设置中，A2UI5_MCP_SYSTEM_PASSWORD, A2UI5_MCP_SYSTEM_PASSWORD_CMD 还是空的，填入你的密钥并保存

    只把密钥粘贴到应用的输入框里，不要粘贴到聊天中或发给任何人

  5. 在 Cursor 中以 Agent 模式打开 AI 聊天

  6. 试一试

    用 abap2UI5 告诉我你能帮我做什么，然后做一件给我看

    ✓ 如果 Cursor 说正在使用 abap2UI5，或回答中出现 abap2UI5 的工具名称，就表示连接成功

35 项可选设置（不填也能用）

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • AI_VIEW_CHECK_HOME Checkout or install of @abap2ui5/linter (validate_view, fix_view, screenshot_view). Default: the peer npm installs beside the server. A set value is authoritative.
  • A2UI5_HOME abap2UI5 framework checkout (app_guide, api_reference, pitfalls; backend when present). Default: ../abap2UI5, else the GitHub mirror and the npm runtime.
  • SAMPLES_CONTROLS_HOME samples-controls checkout (capabilities, examples, generation_rules, scope_of, UI5 for screenshots). Default: ../samples-controls, else the GitHub mirror.
  • SAMPLES_HOME abap2UI5/samples checkout, one of the catalogues examples searches. Default: ../samples, else the GitHub mirror.
  • SAMPLES_STACK_HOME abap2UI5/samples-stack checkout (OData, RAP, APC, launchpad samples). Default: ../samples-stack, else the GitHub mirror.
  • APP_TEMPLATE_HOME abap2UI5/app-template checkout that scaffold_app serves and add_agent_setup executes. Default: ../app-template, else the GitHub mirror.
  • DOCS_HOME abap2UI5/docs checkout that docs_search reads. Default: ../docs, else the GitHub mirror.
  • ABAP_CLOUD_GUI_HOME abap2UI5-addons/abap-cloud-gui checkout (with npm ci done) whose report2cloud converter migrate_report runs. Default: ../abap-cloud-gui; no mirror.
  • POPUPS_HOME abap2UI5-addons/popups checkout whose popups migrate_report with deploy: true writes into the dev sandbox beside the converted class. Default: .deps/popups of the abap-cloud-gui checkout, ../popups b…
  • OPENUI5_SRC OpenUI5 source checkout scope_of reads the JSDoc from (via samples-controls). Default: ../fork-openui5 next to samples-controls.
  • A2UI5_MCP_WORKSPACE Where the npm backend installs, the dev sandbox lives and a framework clone lands. Default: ~/.abap2ui5-mcp.
  • A2UI5_MCP_BACKEND Which backend runs the apps: npm (the @abap2ui5/node-runtime package, even beside a checkout) or clone (clone the framework). Default: decided per call.
  • A2UI5_MCP_RUNTIME_VERSION Pin the @abap2ui5/node-runtime release (X.Y.Z) the npm backend installs. Default: the registry's latest.
  • A2UI5_MCP_PORT Port of the local backend run_app boots against. Default: 3000.
  • A2UI5_MCP_UI Whether app_start/app_describe/app_act declare their MCP Apps screen (ui://abap2ui5/app-screen): auto (default - when the client advertises the io.modelcontextprotocol/ui extension), on, off.
  • A2UI5_MCP_APP_FORMAT The default answer format of the app tools: snapshot (default) or adaptive-card (the snapshot plus an Adaptive Card 1.5 as an embedded resource, for card-rendering hosts).
  • A2UI5_MCP_OFFLINE Set to 1 for no network: no UI5 CDN fallback, no GitHub mirror, no registry lookup.
  • A2UI5_MCP_REMOTE Set to 0 to switch off the read-only GitHub mirror used when no checkout is found.
  • A2UI5_MCP_REMOTE_DIR Cache directory of the GitHub mirror. Default: /abap2ui5-mcp-remote.
  • A2UI5_MCP_REMOTE_TTL_MS How long a mirrored copy is used before it is refreshed, in milliseconds. Default: one day.
  • A2UI5_MCP_UI5_CACHE_MB How many MB of UI5 answers from the CDN (sdk.openui5.org) run_app and interact_app keep in memory across calls, so a second boot does not download them again. 0 switches the cache off. Default: 64.
  • A2UI5_MCP_RENDER_PAGES Pages (Chromium tabs) of validate_view's warm render gate, which concurrent calls queue on. Default: 2 (1 to 8).
  • A2UI5_MCP_CHROMIUM Chromium binary for run_app and interact_app. Default: CHROMIUM_BIN, Playwright's managed browser, then a system chromium.
  • A2UI5_MCP_SCREENSHOT_DIR Where run_app and interact_app write their PNGs (the newest 50 are kept) and build_backend its log. Default: /abap2ui5-mcp-screenshots.
  • A2UI5_MCP_PREBUILT_URL Where build_backend mode prebuilt downloads the backend from. Default: the framework's release asset.
  • A2UI5_MCP_LINT_WORKER Set to 0 to run every lint as a fresh abaplint process. Default: a long-lived worker keeps @abaplint/core with the framework parsed and lints a deploy in milliseconds (the CLI runs whenever the worke…
  • A2UI5_MCP_LINT_IDLE_MS How long the warm lint worker (about 300 MB with the framework parsed) is kept without a request before it exits, in milliseconds; the next lint starts a fresh one. 0 keeps it for the server's life.…
  • A2UI5_MCP_LINT_TIMEOUT_MS Hard timeout of the abaplint run, in milliseconds. Default: 5 minutes.
  • A2UI5_MCP_SCOPE_TIMEOUT_MS Hard timeout of scope_of, in milliseconds. Default: 5 minutes.
  • A2UI5_MCP_BUILD_TIMEOUT_MS Hard timeout of a build, the prebuilt download and the npm install, in milliseconds. Default: 30 minutes.
  • A2UI5_MCP_UNIT_TIMEOUT_MS Hard timeout of the ABAP Unit runner, in milliseconds. Default: 10 minutes.
  • A2UI5_MCP_SYSTEM_URL Switches on the SYSTEM MODE: the app tools against this real SAP system instead of the sandbox loop. The launch URL, e.g. https://host:44300/sap/bc/z2ui5?app_start={class}&sap-client=100.
  • A2UI5_MCP_SYSTEM_USER System mode: the SAP user the app tools log on with (Basic authentication).
  • A2UI5_MCP_SYSTEM_INSECURE_TLS System mode: set to 1 to accept a certificate that cannot be verified. NODE_EXTRA_CA_CERTS with the CA is the better fix.
  • GITHUB_TOKEN Optional token sent to api.github.com only, to raise the rate limit of the docs tree listing (GH_TOKEN is read too).

说明仍为英文原文。

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code，但需要先准备

需要 abap2UI5 的密钥（在开发者网站创建） · 需要先在电脑上安装 Node.js（只需一次）

  1. 安装 Node.js

    只需一次，所有需要 Node.js 的服务器都能用

    打开 Node.js 下载页 ↗

  2. 注册并创建 abap2UI5 的密钥

    打开开发者网站，注册账户并创建 API 密钥，下一步要用。价格和免费方案请看开发者网站。

    打开 abap2UI5 网站 ↗

  3. 点击这个按钮打开 VS Code

    正在检查命令 · 通过后才会显示复制按钮

  4. 填写你的密钥

    在 abap2UI5 的设置中，A2UI5_MCP_SYSTEM_PASSWORD, A2UI5_MCP_SYSTEM_PASSWORD_CMD 还是空的，填入你的密钥并保存

    只把密钥粘贴到应用的输入框里，不要粘贴到聊天中或发给任何人

  5. 在 VS Code 中以 Agent 模式打开 AI 聊天

  6. 试一试

    用 abap2UI5 告诉我你能帮我做什么，然后做一件给我看

    ✓ 如果 VS Code 说正在使用 abap2UI5，或回答中出现 abap2UI5 的工具名称，就表示连接成功

35 项可选设置（不填也能用）

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • AI_VIEW_CHECK_HOME Checkout or install of @abap2ui5/linter (validate_view, fix_view, screenshot_view). Default: the peer npm installs beside the server. A set value is authoritative.
  • A2UI5_HOME abap2UI5 framework checkout (app_guide, api_reference, pitfalls; backend when present). Default: ../abap2UI5, else the GitHub mirror and the npm runtime.
  • SAMPLES_CONTROLS_HOME samples-controls checkout (capabilities, examples, generation_rules, scope_of, UI5 for screenshots). Default: ../samples-controls, else the GitHub mirror.
  • SAMPLES_HOME abap2UI5/samples checkout, one of the catalogues examples searches. Default: ../samples, else the GitHub mirror.
  • SAMPLES_STACK_HOME abap2UI5/samples-stack checkout (OData, RAP, APC, launchpad samples). Default: ../samples-stack, else the GitHub mirror.
  • APP_TEMPLATE_HOME abap2UI5/app-template checkout that scaffold_app serves and add_agent_setup executes. Default: ../app-template, else the GitHub mirror.
  • DOCS_HOME abap2UI5/docs checkout that docs_search reads. Default: ../docs, else the GitHub mirror.
  • ABAP_CLOUD_GUI_HOME abap2UI5-addons/abap-cloud-gui checkout (with npm ci done) whose report2cloud converter migrate_report runs. Default: ../abap-cloud-gui; no mirror.
  • POPUPS_HOME abap2UI5-addons/popups checkout whose popups migrate_report with deploy: true writes into the dev sandbox beside the converted class. Default: .deps/popups of the abap-cloud-gui checkout, ../popups b…
  • OPENUI5_SRC OpenUI5 source checkout scope_of reads the JSDoc from (via samples-controls). Default: ../fork-openui5 next to samples-controls.
  • A2UI5_MCP_WORKSPACE Where the npm backend installs, the dev sandbox lives and a framework clone lands. Default: ~/.abap2ui5-mcp.
  • A2UI5_MCP_BACKEND Which backend runs the apps: npm (the @abap2ui5/node-runtime package, even beside a checkout) or clone (clone the framework). Default: decided per call.
  • A2UI5_MCP_RUNTIME_VERSION Pin the @abap2ui5/node-runtime release (X.Y.Z) the npm backend installs. Default: the registry's latest.
  • A2UI5_MCP_PORT Port of the local backend run_app boots against. Default: 3000.
  • A2UI5_MCP_UI Whether app_start/app_describe/app_act declare their MCP Apps screen (ui://abap2ui5/app-screen): auto (default - when the client advertises the io.modelcontextprotocol/ui extension), on, off.
  • A2UI5_MCP_APP_FORMAT The default answer format of the app tools: snapshot (default) or adaptive-card (the snapshot plus an Adaptive Card 1.5 as an embedded resource, for card-rendering hosts).
  • A2UI5_MCP_OFFLINE Set to 1 for no network: no UI5 CDN fallback, no GitHub mirror, no registry lookup.
  • A2UI5_MCP_REMOTE Set to 0 to switch off the read-only GitHub mirror used when no checkout is found.
  • A2UI5_MCP_REMOTE_DIR Cache directory of the GitHub mirror. Default: /abap2ui5-mcp-remote.
  • A2UI5_MCP_REMOTE_TTL_MS How long a mirrored copy is used before it is refreshed, in milliseconds. Default: one day.
  • A2UI5_MCP_UI5_CACHE_MB How many MB of UI5 answers from the CDN (sdk.openui5.org) run_app and interact_app keep in memory across calls, so a second boot does not download them again. 0 switches the cache off. Default: 64.
  • A2UI5_MCP_RENDER_PAGES Pages (Chromium tabs) of validate_view's warm render gate, which concurrent calls queue on. Default: 2 (1 to 8).
  • A2UI5_MCP_CHROMIUM Chromium binary for run_app and interact_app. Default: CHROMIUM_BIN, Playwright's managed browser, then a system chromium.
  • A2UI5_MCP_SCREENSHOT_DIR Where run_app and interact_app write their PNGs (the newest 50 are kept) and build_backend its log. Default: /abap2ui5-mcp-screenshots.
  • A2UI5_MCP_PREBUILT_URL Where build_backend mode prebuilt downloads the backend from. Default: the framework's release asset.
  • A2UI5_MCP_LINT_WORKER Set to 0 to run every lint as a fresh abaplint process. Default: a long-lived worker keeps @abaplint/core with the framework parsed and lints a deploy in milliseconds (the CLI runs whenever the worke…
  • A2UI5_MCP_LINT_IDLE_MS How long the warm lint worker (about 300 MB with the framework parsed) is kept without a request before it exits, in milliseconds; the next lint starts a fresh one. 0 keeps it for the server's life.…
  • A2UI5_MCP_LINT_TIMEOUT_MS Hard timeout of the abaplint run, in milliseconds. Default: 5 minutes.
  • A2UI5_MCP_SCOPE_TIMEOUT_MS Hard timeout of scope_of, in milliseconds. Default: 5 minutes.
  • A2UI5_MCP_BUILD_TIMEOUT_MS Hard timeout of a build, the prebuilt download and the npm install, in milliseconds. Default: 30 minutes.
  • A2UI5_MCP_UNIT_TIMEOUT_MS Hard timeout of the ABAP Unit runner, in milliseconds. Default: 10 minutes.
  • A2UI5_MCP_SYSTEM_URL Switches on the SYSTEM MODE: the app tools against this real SAP system instead of the sandbox loop. The launch URL, e.g. https://host:44300/sap/bc/z2ui5?app_start={class}&sap-client=100.
  • A2UI5_MCP_SYSTEM_USER System mode: the SAP user the app tools log on with (Basic authentication).
  • A2UI5_MCP_SYSTEM_INSECURE_TLS System mode: set to 1 to accept a certificate that cannot be verified. NODE_EXTRA_CA_CERTS with the CA is the better fix.
  • GITHUB_TOKEN Optional token sent to api.github.com only, to raise the rate limit of the docs tree listing (GH_TOKEN is read too).

说明仍为英文原文。

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用（如 Windsurf、Zed、Gemini CLI）添加方式各不相同，请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了？问问正在用 abap2UI5 的人💬 讨论 →
开发者专用：终端命令和 JSON 设置

安装在电脑上

Claude Code

正在检查命令 · 通过后才会显示复制按钮

Claude Desktop (claude_desktop_config.json)

正在检查命令 · 通过后才会显示复制按钮

Cursor (~/.cursor/mcp.json)

正在检查命令 · 通过后才会显示复制按钮

VS Code (mcp.json)

正在检查命令 · 通过后才会显示复制按钮

需要你填写的值

  • AI_VIEW_CHECK_HOME env
    Checkout or install of @abap2ui5/linter (validate_view, fix_view, screenshot_view). Default: the peer npm installs beside the server. A set value is authoritative.
  • A2UI5_HOME env
    abap2UI5 framework checkout (app_guide, api_reference, pitfalls; backend when present). Default: ../abap2UI5, else the GitHub mirror and the npm runtime.
  • SAMPLES_CONTROLS_HOME env
    samples-controls checkout (capabilities, examples, generation_rules, scope_of, UI5 for screenshots). Default: ../samples-controls, else the GitHub mirror.
  • SAMPLES_HOME env
    abap2UI5/samples checkout, one of the catalogues examples searches. Default: ../samples, else the GitHub mirror.
  • SAMPLES_STACK_HOME env
    abap2UI5/samples-stack checkout (OData, RAP, APC, launchpad samples). Default: ../samples-stack, else the GitHub mirror.
  • APP_TEMPLATE_HOME env
    abap2UI5/app-template checkout that scaffold_app serves and add_agent_setup executes. Default: ../app-template, else the GitHub mirror.
  • DOCS_HOME env
    abap2UI5/docs checkout that docs_search reads. Default: ../docs, else the GitHub mirror.
  • ABAP_CLOUD_GUI_HOME env
    abap2UI5-addons/abap-cloud-gui checkout (with npm ci done) whose report2cloud converter migrate_report runs. Default: ../abap-cloud-gui; no mirror.
  • POPUPS_HOME env
    abap2UI5-addons/popups checkout whose popups migrate_report with deploy: true writes into the dev sandbox beside the converted class. Default: .deps/popups of the abap-cloud-gui checkout, ../popups b…
  • OPENUI5_SRC env
    OpenUI5 source checkout scope_of reads the JSDoc from (via samples-controls). Default: ../fork-openui5 next to samples-controls.
  • A2UI5_MCP_WORKSPACE env
    Where the npm backend installs, the dev sandbox lives and a framework clone lands. Default: ~/.abap2ui5-mcp.
  • A2UI5_MCP_BACKEND env
    Which backend runs the apps: npm (the @abap2ui5/node-runtime package, even beside a checkout) or clone (clone the framework). Default: decided per call.
  • A2UI5_MCP_RUNTIME_VERSION env
    Pin the @abap2ui5/node-runtime release (X.Y.Z) the npm backend installs. Default: the registry's latest.
  • A2UI5_MCP_PORT env
    Port of the local backend run_app boots against. Default: 3000.
  • A2UI5_MCP_UI env
    Whether app_start/app_describe/app_act declare their MCP Apps screen (ui://abap2ui5/app-screen): auto (default - when the client advertises the io.modelcontextprotocol/ui extension), on, off.
  • A2UI5_MCP_APP_FORMAT env
    The default answer format of the app tools: snapshot (default) or adaptive-card (the snapshot plus an Adaptive Card 1.5 as an embedded resource, for card-rendering hosts).
  • A2UI5_MCP_OFFLINE env
    Set to 1 for no network: no UI5 CDN fallback, no GitHub mirror, no registry lookup.
  • A2UI5_MCP_REMOTE env
    Set to 0 to switch off the read-only GitHub mirror used when no checkout is found.
  • A2UI5_MCP_REMOTE_DIR env
    Cache directory of the GitHub mirror. Default: /abap2ui5-mcp-remote.
  • A2UI5_MCP_REMOTE_TTL_MS env
    How long a mirrored copy is used before it is refreshed, in milliseconds. Default: one day.
  • A2UI5_MCP_UI5_CACHE_MB env
    How many MB of UI5 answers from the CDN (sdk.openui5.org) run_app and interact_app keep in memory across calls, so a second boot does not download them again. 0 switches the cache off. Default: 64.
  • A2UI5_MCP_RENDER_PAGES env
    Pages (Chromium tabs) of validate_view's warm render gate, which concurrent calls queue on. Default: 2 (1 to 8).
  • A2UI5_MCP_CHROMIUM env
    Chromium binary for run_app and interact_app. Default: CHROMIUM_BIN, Playwright's managed browser, then a system chromium.
  • A2UI5_MCP_SCREENSHOT_DIR env
    Where run_app and interact_app write their PNGs (the newest 50 are kept) and build_backend its log. Default: /abap2ui5-mcp-screenshots.
  • A2UI5_MCP_PREBUILT_URL env
    Where build_backend mode prebuilt downloads the backend from. Default: the framework's release asset.
  • A2UI5_MCP_LINT_WORKER env
    Set to 0 to run every lint as a fresh abaplint process. Default: a long-lived worker keeps @abaplint/core with the framework parsed and lints a deploy in milliseconds (the CLI runs whenever the worke…
  • A2UI5_MCP_LINT_IDLE_MS env
    How long the warm lint worker (about 300 MB with the framework parsed) is kept without a request before it exits, in milliseconds; the next lint starts a fresh one. 0 keeps it for the server's life.…
  • A2UI5_MCP_LINT_TIMEOUT_MS env
    Hard timeout of the abaplint run, in milliseconds. Default: 5 minutes.
  • A2UI5_MCP_SCOPE_TIMEOUT_MS env
    Hard timeout of scope_of, in milliseconds. Default: 5 minutes.
  • A2UI5_MCP_BUILD_TIMEOUT_MS env
    Hard timeout of a build, the prebuilt download and the npm install, in milliseconds. Default: 30 minutes.
  • A2UI5_MCP_UNIT_TIMEOUT_MS env
    Hard timeout of the ABAP Unit runner, in milliseconds. Default: 10 minutes.
  • A2UI5_MCP_SYSTEM_URL env
    Switches on the SYSTEM MODE: the app tools against this real SAP system instead of the sandbox loop. The launch URL, e.g. https://host:44300/sap/bc/z2ui5?app_start={class}&sap-client=100.
  • A2UI5_MCP_SYSTEM_USER env
    System mode: the SAP user the app tools log on with (Basic authentication).
  • A2UI5_MCP_SYSTEM_PASSWORD 机密 必填 env
    System mode: the password of A2UI5_MCP_SYSTEM_USER. Or A2UI5_MCP_SYSTEM_PASSWORD_CMD, to keep it out of the configuration.
  • A2UI5_MCP_SYSTEM_PASSWORD_CMD 机密 必填 env
    System mode: a shell command that prints the password (a keychain lookup) - instead of A2UI5_MCP_SYSTEM_PASSWORD.
  • A2UI5_MCP_SYSTEM_INSECURE_TLS env
    System mode: set to 1 to accept a certificate that cannot be verified. NODE_EXTRA_CA_CERTS with the CA is the better fix.
  • GITHUB_TOKEN 机密 env
    Optional token sent to api.github.com only, to raise the rate limit of the docs tree listing (GH_TOKEN is read too).

说明仍为英文原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

一览

每周下载量i
61/周
连接方式
在你的电脑上运行
最新版本i
1.0.0
发布到注册中心i
2026年10月14日
代码最后更新i
2026年11月13日
作者
abap2UI5
软件包
npm: @abap2ui5/mcp-server
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档，检查于 2026年11月10日。

在你的电脑上运行，适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月14日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 abap2UI5 验证，该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

    它在你的电脑上运行，没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行，改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行；我们只能读取互联网端点的工具列表

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子，欢迎第一个提问或分享。

此处内容由用户撰写，不代表 PopNx 团队。

使用 Google 登录后发帖

用户评价

还没有评价

用 Google 登录后写评价

与“网页与浏览器”中的其他服务器比较i

  • 星标数多于此分类中其他 1511 个服务器的 78%
  • 发布到注册中心的时间比此分类中其他 1511 个服务器的 50% 更新
  • 基础检查结果等于或优于此分类中其他 1511 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

abap2UI5 安全吗？

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：A2UI5_MCP_SYSTEM_PASSWORD, A2UI5_MCP_SYSTEM_PASSWORD_CMD

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于昨天，最新版本（1.0.0）于31天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Browser Use, Scrapling MCP Server, Chrome DevTools MCP

同类别的其他选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Browser Use

Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.

作者：browser-use广泛使用↓ 167.3万/周★ 12.1万24天前更新

电脑或云端✓ 服务方 · browser-use.com
安装

Scrapling MCP Server

Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.

作者：D4Vinci广泛使用↓ 39.7万/周★ 10.2万9天前更新

在你的电脑上运行
安装

Chrome DevTools MCP

MCP server for Chrome DevTools

作者：ChromeDevTools广泛使用↓ 186.9万/周★ 5.5万3天前更新

在你的电脑上运行
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

mcp-server

The MCP server for abap2UI5 — gives any AI coding agent (Claude Code, Cursor, VS Code Copilot, or any MCP client) the full abap2UI5 development loop, without an SAP system:

examples -> app_guide -> validate_view + screenshot_view -> deploy_app -> build_backend -> run_app -> pitfalls

(has somebody (how an app (SECONDS, no system: (write ABAP, (transpile (boot headless, (what a green built it is built) is the view legal, lint) to Node) errors + run still already?) and what does it LOOK like) SCREENSHOT) does not prove)

The agent writes an ABAP class, validates the view and looks at a picture of it in seconds, deploys it, boots it in a real browser and looks at the running app — then iterates. Everything runs locally on infrastructure that already guards the abap2UI5 ecosystem in CI: the abaplint transpiler + open-abap runtime, the framework's express shim, the samples-controls build and boot gates, and the linter validation core.

Documentation

→ [The MCP server, in full](https://abap2ui5.github.io/docs/advanced/mcp_server.html) — what MCP means here, the three setup levels and what each one buys, how to register the server with your client, every tool with what the agent gets from it, and the loop they are meant to be used in.

→ [Building with AI](https://abap2ui5.github.io/docs/get_started/ai.html) — the whole AI setup in rising order of effort. This server is the top rung; the cheaper ones matter first.

Quick start

One-click install

Every button registers the same stdio server, named abap2ui5:

{"command":"npx","args":["--yes","-p","@abap2ui5/mcp-server","abap2ui5-mcp"]}

The badges go through a web redirect because GitHub does not render links to an editor's own URL scheme; the direct links, to paste into a browser or xdg-open/open, are:

vscode:mcp/install?%7B%22name%22%3A%22abap2ui5%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22--yes%22%2C%22-p%22%2C%22%40abap2ui5%2Fmcp-server%22%2C%22abap2ui5-mcp%22%5D%7D

cursor://anysphere.cursor-deeplink/mcp/install?name=abap2ui5&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyItLXllcyIsIi1wIiwiQGFiYXAydWk1L21jcC1zZXJ2ZXIiLCJhYmFwMnVpNS1tY3AiXX0%3D

(vscode-insiders: in place of vscode: for Insiders.) Claude Code:

claude mcp add abap2ui5 -- npx --yes -p @abap2ui5/mcp-server abap2ui5-mcp

Claude Code plugin. The abap2UI5 plugin bundles the framework's agent skills (building an app, the ABAP and UI5 pitfall catalogues, the view-chain layout, ...) together with this server, registered the same way as above — one install for both:

/plugin marketplace add abap2UI5/abap2UI5

/plugin install abap2ui5@abap2ui5

Releases from 1.0.0 on are also listed in the official MCP Registry as io.github.abap2UI5/mcp-server (server.json), for clients that install from the registry. The same command is what the Smithery (smithery.yaml) and Glama (glama.json) directories list: one npm package, one version, whichever catalogue a client reads.

That is level 1 below: validate_view and fix_view work out of the box, and setup_status tells the agent what else works on this machine and what is missing.

What each install brings

Level 1 — validate_view, fix_view and screenshot_view, the tools most work happens at. They need the linter, which the server declares as a peer dependency (@abap2ui5/linter, >=0.8.0 <0.10.0 — the range this server is built against). npm 7+ installs a non-optional peer by itself, so the one-liner below brings the linter along and validate_view/fix_view work out of the box. The render gate behind screenshot_view needs the UI5 libraries and Playwright on top (@abap2ui5/linter-render, declared as an optional peer: the compatible range is stated, the package is NOT installed for you — plan on ~150–200 MB and a few minutes the first time you add it):

claude mcp add abap2ui5 -- npx --yes -p @abap2ui5/mcp-server abap2ui5-mcp                            # validate_view, fix_view

claude mcp add abap2ui5 -- npx --yes -p @abap2ui5/mcp-server -p @abap2ui5/linter-render abap2ui5-mcp # + screenshot_view

The server looks for the linter, in this order: AI_VIEW_CHECK_HOME; a linter checkout next to the server (which is also where npm puts the peer for an npx run: node_modules/@abap2ui5/{mcp-server,linter}); the project it is started in (node_modules/@abap2ui5/linter — app-template has it as a devDependency, so npm install there is all it takes); the server's own node_modules; whatever Node's module resolution finds from the server's location. A set env var decides alone. Or work from a checkout:

git clone https://github.com/abap2UI5/linter        # AI_VIEW_CHECK_HOME

cd linter && npm ci

The server itself is on npm, so it needs no checkout; the registration above is the whole install. (With npm 6 or --legacy-peer-deps, add -p @abap2ui5/linter yourself.)

(-p … abap2ui5-mcp names the bin explicitly, which every published version answers. The shorter npx --yes @abap2ui5/mcp-server needs a bin named after the package, which 0.2.0 and earlier do not have — npx stops there with "could not determine executable to run".)

(The install is ~47 MB: 19 MB of it a Playwright driver only run_app uses, 2 MB the linter — paid on the first start, cached after. From a checkout instead: git clone https://github.com/abap2UI5/mcp-server && cd mcp-server && npm ci, then claude mcp add abap2ui5 -- node /path/to/mcp-server/server.mjs.)

Cursor, VS Code and Claude Desktop take the standard stdio shape — the documentation has the JSON, and the two further levels (the sample catalogues and deploying, then the headless build-and-boot loop). A tool whose prerequisites are missing answers with a message naming what it needs; the server starts either way.

The abap2UI5 VS Code extension registers this server for you, and adds a second one of its own for the tools that need a real SAP system.

Everything in one command — for a machine (or Codespace) dedicated to the full build-and-boot loop, setup.sh clones the framework, corpus and linter checkouts next to this repo, installs their dependencies and the headless browser (existing checkouts are reused, safe to re-run):

git clone https://github.com/abap2UI5/mcp-server && ./mcp-server/setup.sh

setup.sh --no-corpus clones the framework and the linter only, which is the whole loop for an app of your own since the framework sandbox exists; the corpus is for scope_of, the full build and the locally served UI5.

A Claude Code started inside the checkout picks the server up automatically via the committed .mcp.json; the devcontainer runs the same setup on create.

Level 0 — no checkout at all. The knowledge tools (app_guide, api_reference, pitfalls, capabilities, examples, read_example, docs_search, scaffold_app, generation_rules) read committed files, so when no checkout resolves and no env var is set they read them from GitHub instead: the files land in a per-user cache ( /abap2ui5-mcp-remote, a day at a time - used only while it is a directory of the user's own, created 0700; A2UI5_MCP_REMOTE_DIR moves it) that the server treats as a read-only checkout; add_agent_setup reads the template from there too, and writes only into the project it is given. And the expensive half runs on the npm package @abap2ui5/node-runtime (below), so npx --yes -p @abap2ui5/mcp-server abap2ui5-mcp in a fresh project covers deploy_app, build_backend, run_app, interact_app, run_unit_tests and verify_app too, with no clone of anything. What still needs a checkout is the corpus' part (scope_of, build_backend mode full, the locally served UI5). A2UI5_MCP_REMOTE=0 or A2UI5_MCP_OFFLINE=1 switches the mirror off. The docs mirror lists its pages through GitHub's API, which allows 60 unauthenticated requests an hour per address; a GITHUB_TOKEN (or GH_TOKEN) in the environment raises that and is sent to api.github.com only.

The backend without a framework checkout: `@abap2ui5/node-runtime`. The framework is published on npm already transpiled, with the ABAP sources of the same release commit to transpile apps against. With no abap2UI5 checkout (and none configured), build_backend installs that package once per release into ~/.abap2ui5-mcp/runtime/ — with the transpiler it names, express, and app-template's abaplint for the lint, at exact versions with a lockfile, --ignore-scripts — fetches open-abap-core at the commit the release was built with, and then transpiles only the deployed apps against it: seconds, never the framework. deploy_app writes into ~/.abap2ui5-mcp/sandbox (and lints with app-template's own config against the package's sources), run_app boots the package's server with the apps registered, run_unit_tests runs the apps' own tests. The release is the registry's latest (asked through npm, cached a day) unless A2UI5_MCP_RUNTIME_VERSION pins one. Measured here with a cold npm cache: the first install about 10 s, open-abap-core about 1 s, then 7–8 s per build and about a second for the unit tests. setup_status shows the release, the workspace and what the next build would do.

With a framework checkout (A2UI5_HOME or a sibling) everything works as before: build_backend downloads the release's prebuilt backend (backend- .tar.gz) into the checkout the first time and re-transpiles the deployed apps from its node/zz_dev afterwards. A2UI5_MCP_BACKEND=npm runs on the package beside a checkout; build_backend mode prebuilt (or A2UI5_MCP_BACKEND=clone) clones the release into ~/.abap2ui5-mcp/abap2UI5 instead — the path this server took without a checkout until the package existed. The full corpus build stays available as mode: "full" for a checkout on an unreleased commit.

Tools

Every tool reads live from a sibling checkout, and each one needs a specific sibling — there is no "optional" repository, only tools you do or do not use. The Needs column says which checkout a tool is dead without: the linter alone carries validate_view, fix_view and screenshot_view (the fast loop, where most iterations happen — and the one dependency npm installs with the server, as its declared peer), the framework checkout carries the guide, the pitfalls and the inte

只显示了开头部分；其余内容请在仓库中阅读