Skip to content

Latest commit

 

History

History
40 lines (30 loc) · 2.73 KB

index.md

File metadata and controls

40 lines (30 loc) · 2.73 KB

LISA documentation

LISA (Localization & Internationalization Service for ABAP) is an MCP server that lets AI assistants read, write and compare SAP object translations. It has two halves:

  • an ABAP HTTP service (ZCL_I18N_SERVICE) you install in your SAP system, and
  • this Node.js MCP server, which authenticates callers and forwards their requests to that service.

Start here

  1. Quickstart — the fastest path to a working setup.
  2. ABAP service setup — import the class and publish/enable the HTTP service.
  3. MCP tools usage — the 3 tools, with examples.
  4. Text tables (text_table) — translating delivery-class C/S tables (e.g. T005T).

Reference

  • Configuration reference — every environment variable.
  • Authentication — the auth model and the supported methods.
  • Architecture — how the components fit together.
  • Using the ABAP API (agent skill) — how to drive zi18n_service: the six actions, the JSON wire contract, target types, and pitfalls. Auth-agnostic — a BTP destination or the MCP server carries it.
  • OpenAPI spec — the zi18n_service contract as OpenAPI 3.0, ready to import into Joule Studio (actions), SAP API Management, or Postman.
  • Wire-contract evolution & platform divergence — why one MCP serves every platform, the per-platform ABAP split, and how to grow the contract / add a target_type or parameter as the XCO APIs diverge.

Operations

At a glance

Tools TranslateListLanguages, TranslateGetTexts, TranslateSetTexts
Object types data elements, domains, CDS views (+ merged cds_entity), CDS metadata extensions, message classes, class/FG text pools, text tables, application log objects, business configuration objects
Transports http-streamable (default) and stdio
Auth none (stdio/local), API key, OIDC/JWT, XSUAA (BTP)
Built like ARC-1