Oleksii Kyslytsia

Embedded ABAP ADT MCP server tailored for the Cloud LLM Hub stack

SAP ABAP ADT MCP server with full CRUD for on-prem and ABAP Cloud (BTP), plus JWT/XSUAA and service-key destination auth

ABAP connection layer for MCP ABAP ADT server

JWT authentication broker for MCP ABAP ADT - manages tokens based on destination headers

Core components for building Smart LLM agents, plus a default MCP-orchestrated OpenAI-compatible server implementation.

Shared interfaces for MCP ABAP ADT packages

ADT clients for SAP ABAP systems - AdtClient and AdtRuntimeClient

Token providers for MCP ABAP ADT auth-broker

MCP client configurator for mcp-abap-adt and mcp-abap-adt-proxy

MCP proxy server for SAP ABAP ADT - proxies local requests to cloud-llm-hub with JWT authentication

Header validator for MCP ABAP ADT - validates and prioritizes authentication headers

Logger interface and implementations for MCP ABAP ADT packages

The compact MCP server for SAP ABAP ADT: one tool per operation with the object in the arguments — 22 tools instead of 370, for a host that cannot build a retrieval pipeline of its own.

QdrantRag vector store and QdrantRagProvider for @mcp-abap-adt/llm-agent.

MCP client wrapper, adapter, factory, and connection strategies for the SmartAgent runtime.

Ollama LLM provider (ILlm, extends OpenAIProvider — Ollama's OpenAI-compatible /v1 API) for @mcp-abap-adt/llm-agent.

Anthropic (Claude) LLM provider (ILlm) for @mcp-abap-adt/llm-agent.

Ollama embedding provider and OllamaRag convenience class for @mcp-abap-adt/llm-agent.

HanaVectorRag vector store (SAP HANA Cloud Vector Engine) and HanaVectorRagProvider for @mcp-abap-adt/llm-agent.

PgVectorRag (PostgreSQL + pgvector) and PgVectorRagProvider for @mcp-abap-adt/llm-agent.

The SmartServer composition runtime as an **importable library**. It sits between the binary `@mcp-abap-adt/llm-agent-server` and the core `@mcp-abap-adt/llm-agent-libs`, so the SmartServer/coordinator composition can be reused in other projects without d

ADT tool handlers and an embeddable MCP server for SAP ABAP. The standalone server is @mcp-abap-adt/core.

The compact ABAP ADT tools that write, lock, activate or execute: one tool per operation, the object in the arguments.

The compact ABAP ADT tools that change nothing: one tool per read operation, the object in the arguments. A tool list a consumer can hand out knowing it carries no write route.

The HTTP+SSE transport of the MCP ABAP ADT server: an Express app serving the ADT tools of @mcp-abap-adt/lib over the MCP HTTP+SSE transport, with DNS rebinding protection and TLS.

The read-only MCP server for SAP ABAP ADT over HTTP+SSE: the readonly tools (with system and search), no high, debugger, background-run or leftover-session tool; credentials only from the x-sap-* headers of the request that opens each SSE connection. No a

The Streamable HTTP transport of the MCP ABAP ADT server: an Express app serving the ADT tools of @mcp-abap-adt/lib over MCP Streamable HTTP, with DNS rebinding protection and TLS.

The read-only compact MCP server for SAP ABAP ADT over HTTP+SSE: the 17 compact tools that change nothing, with credentials only from the x-sap-* headers of the request that opens each SSE connection. No auth broker, no stores.

The compact MCP server for SAP ABAP ADT over Streamable HTTP: one tool per operation with the object in the arguments — 28 tools instead of 370 — with credentials only from the x-sap-* headers of each request. No auth broker, no stores.

The read-only compact MCP server for SAP ABAP ADT over stdio: the 17 compact tools that change nothing, one per operation with the object in the arguments, and the leftover-session list and logoff. Configured as @mcp-abap-adt/core; connects over HTTP, RFC

The read-only MCP server for SAP ABAP ADT over Streamable HTTP: the readonly tools (with system and search), no high, debugger, background-run or leftover-session tool; credentials only from each request's x-sap-* headers. No auth broker, no stores.

The compact MCP server for SAP ABAP ADT over HTTP+SSE: one tool per operation with the object in the arguments — 28 tools instead of 370 — with credentials only from the x-sap-* headers of the request that opens each SSE connection. No auth broker, no sto

The read-only MCP server for SAP ABAP ADT over stdio: the readonly tools (with system and search) and the leftover-session list and logoff, no high, debugger, background-run or resume tool. One destination through the auth broker, as @mcp-abap-adt/core; c

The read-only compact MCP server for SAP ABAP ADT over Streamable HTTP: the 17 compact tools that change nothing, with credentials only from the x-sap-* headers of each request. No auth broker, no stores.

Protocol-faithful mock authorization servers (UAA/OAuth2, OIDC, SAML IdP) for testing @mcp-abap-adt packages

SAP Cloud ALM OData/REST client library for MCP ABAP ADT ecosystem

MCP server + reusable tool primitives for SAP Cloud ALM, backed by @mcp-abap-adt/calm-client.

RAG and embedder composition for the SmartAgent runtime.

Core SmartAgent composition runtime. Builder, agent runtime, pipeline, sessions, history, resilience, observability, plugins, skills.

OpenAI LLM provider (ILlm) for @mcp-abap-adt/llm-agent.

DeepSeek LLM provider (ILlm, extends OpenAIProvider) for @mcp-abap-adt/llm-agent.

SAP AI Core LLM provider (ILlm) for @mcp-abap-adt/llm-agent.

OpenAI embedding provider (IEmbedderBatch) for @mcp-abap-adt/llm-agent.

SAP AI Core embedding provider (IEmbedder) for @mcp-abap-adt/llm-agent.

Default SmartAgent implementation with LLM providers, MCP client, HTTP server, and CLI.

SAP AI Core service-key token exchange (TokenProvider, parseServiceKey, serviceKeyCredential).

TypeSafe AI (Jev) decision-model provider (IDecisionModel) for @mcp-abap-adt/llm-agent.

Replaceable in-process signal bus and emitter composition helpers.

Usage analytics recorder, transports, sinks and readers.

SQLITE usage analytics sink and reader.

The in-memory store of the MCP ABAP ADT server's background runs: an IBackgroundRuns of @mcp-abap-adt/lib keeping each caller's runs and their answers in the process's memory, 16 per caller, until discarded or the process ends.

The rules of the MCP ABAP ADT servers that name a call's responsible, user and system: a SystemContextRules of @mcp-abap-adt/lib making each connection's parameters from its systeminformation by the system kind, and the system type the transports require.

The compact ABAP ADT tools that change nothing: one tool per read operation, the object in the arguments. A tool list a consumer can hand out knowing it carries no write route.

The launch code of the MCP ABAP ADT servers: the stdio launcher and server with the destination layer (the auth broker per destination), the Streamable HTTP launcher and server, and the HTTP+SSE launcher and server. No command of its own — each server pac

The mcp-auth and mcp-sso commands: log in to a SAP BTP or ABAP destination and write it — its means and the secret the login obtained — through @mcp-abap-adt/auth-broker

The runtime half of the MCP ABAP ADT authentication error contract: builders, renderers, allowlist guards and classification for IAuthProviderError

Stores for MCP ABAP ADT auth-broker - BTP, ABAP, and XSUAA implementations

ADT backup CLI for SAP ABAP objects (recursive package backups and restores)

Default result and failure strategies for @mcp-abap-adt/adt-clients, derived from recorded ADT answers

ADT contracts, the ABAP and Cloud ALM connections, and SAP/BTP configuration and authentication contracts

Credential and access contracts shared across MCP ABAP ADT package families

Transport contracts, generic HTTP and MCP header names and network error codes for MCP ABAP ADT packages

Logging contracts and system-independent shapes for MCP ABAP ADT packages

Contracts for SAP Cloud ALM HTTP APIs

SAP and BTP authorization contracts: service keys, destinations, UAA, SAP connection configuration

The ABAP connection contract: IAbapConnection, its capability atoms, the wire response and the session error codes

The broker's port: the destination (IConnectionConfig, DestinationGrant, IConfig) and the stores that hold it

Lightweight Node.js bindings for SAP NW RFC SDK