Everything in the atlas
Type
Domain: 3
Origin: Independent
Signals
More
Group by: Capability
MCP server with forty-five tools across a Datasphere tenant
It writes and it administers — ETL extraction and database user management are not read operations, and the same connection that profiles a column can move data out of the tenant. Masking is only as good as the configuration naming the fields, so an unlisted sensitive column is an unmasked one.
MCP server for BW/4HANA modelling objects
Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.
Metadata viewer for SAP BW, SAP BPC and SAP BW/4HANA object models
Eighteen Datasphere skills over a bundled MCP server
It reaches a data warehouse, so what an agent can see is business data by definition — the SQL sanitisation and PII filtering in the server are there because of that, not instead of a decision about it. And the guidance is Datasphere-shaped: nothing here transfers to a HANA Cloud database used directly.
MCP server for the SAP Analytics Cloud REST API
Ninety tools is a large surface to put in front of a model at once, and client-credentials OAuth means the tenant sees one identity rather than the person asking. Content transport and user management sit in the same tool list as reading a story.
Fiori overview page comparing aggregated and plain donut-chart cards
Neither the package manifest nor the repository tree declares a licence.
Analytical List Page over a CAP OData V4 service
Neither the package manifest nor the repository tree declares a licence.
sflight example extended with hierarchy support
Neither the package manifest nor the repository tree declares a licence.
CAP Node.js attachments plugin with Object Store and malware scanning
ABAP OData service for attachments and comments via GOS
No published releases; repository quiet for 66 months.
CAP Node.js attachments plugin with database or cloud storage
CAP Node.js plugin mapping CDS entities to SAP Document Management
Archived The declared repository is archived.
Functional boundary For versioned or thumbnail-enabled repositories, or bulk upload and download, the [README](https://raw.githubusercontent.com/vneecious/sap-cap-sdm-plugin/d9f036b16542e5c5b9b6dc704e0ba5f880193212/README.md) labels this an “early release” and lists those features as unsupported.
UI5 control library for file upload and download in front of CAP
Fiori Elements page embedding upload controls on @cap-js/attachments
Neither the package manifest nor the repository tree declares a licence.
Media handling in core CDS with a UI5 UploadSet
Neither the package manifest nor the repository tree declares a licence.
Generates singleton ABAP cache classes from a macro call
No published releases; repository quiet for 26 months.
CAP caching plugin for query results and remote service responses
When user-dependent responses are cached without user-aware or explicit operation keys, or translated responses share keys across locales. These cases require key isolation; locale-aware keys are off by default.
Data federation for CAP via delegation, caching and replication
MCP server with forty-five tools across a Datasphere tenant
It writes and it administers — ETL extraction and database user management are not read operations, and the same connection that profiles a column can move data out of the tenant. Masking is only as good as the configuration naming the fields, so an unlisted sensitive column is an unmasked one.
Read-only MCP server for exploring SAP Datasphere
Business Source License 1.1, which is source-available rather than open source: reading and evaluating are fine, and production use is restricted until the licence's change date. That is a procurement question, not a technical one, and it is the thing to settle first. Read-only also means read-only — no modelling, no loads.
Eighteen Datasphere skills over a bundled MCP server
It reaches a data warehouse, so what an agent can see is business data by definition — the SQL sanitisation and PII filtering in the server are there because of that, not instead of a decision about it. And the guidance is Datasphere-shaped: nothing here transfers to a HANA Cloud database used directly.
MCP tooling for SAP Business Data Cloud discovery and contracts
Business Source License 1.1: source-available, with production use restricted until the change date — settle that before anything technical. And the governed execution path in v0.2 does act on data, which is a different grant from the discovery the v0.1 baseline offered.
MCP server managing Delta shares in SAP Business Data Cloud
Collaborative draft support for CAP Node.js services
The maintainer marks this under active development; public APIs, annotation names and OData contracts may still change.
Data federation for CAP via delegation, caching and replication
Scheduled READ, MAP, WRITE pipelines between CAP services
Replication between systems with CAP
Neither the package manifest nor the repository tree declares a licence.
User details and quickview links for createdBy and modifiedBy
Maps classic dictionary tables and fields to CDS entities and fields
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary Marked BETA and called a first prototype on its own page, which names where it is wrong: when fields are mapped with CAST, CASE, ABS and other CDS functions there may still be errors in the fields, so a mapping that goes through one of those needs checking against the view it came from.
Fills a CDS element from a database-backed number range
Maps database tables and fields to the CDS views exposing them
Not on the [SAP BTP ABAP environment](artifact:btp-abap-environment) or another cloud ABAP system: the maintainer states the tool is not cloud ready, because the data sources and system tables it reads CDS metadata from are not released for cloud development. It is designed for SAP S/4HANA on-premise or private cloud, and the shipped Fiori application is configured for A4H and developer systems.
abapconf 2026 talk materials on RAP custom entities
Neither the package manifest nor the repository tree declares a licence.
CLI for DROP and RENAME schema changes beside @cap-js/postgres
CAP plugin casting read values back to CDS model types
DB2 adapter for CDS
The README is one line and the package carries no licence field. Last released July 2023. The repository the package declares has been deleted — verified against the GitHub API, not just a failed fetch. The package is still on npm, so it installs; the source it was published from is no longer readable, which is a harder thing to discover than a stale version number.
Tunnels CAP Node.js to a private PostgreSQL via Cloud Connector
CAP database adapter for Snowflake with OData V4 support
The maintainer marks this early development; expect the contract to move.
MongoDB as a CAP database service through Mongoose
It declares no peer range on [@sap/cds](artifact:sap-cds) and publishes no repository, so there is nothing to read but the package itself and no CI to look at.
MySQL and MariaDB database adapter for CAP
The repository the package declares has been deleted — verified against the GitHub API, not just a failed fetch. The package is still on npm, so it installs; the source it was published from is no longer readable, which is a harder thing to discover than a stale version number.
PostgreSQL adapter for SAP CDS from the SAP Mentors community
The declared repository is archived.
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
CAP and Fiori app showing BTP Application Vulnerability Report data
Neither the package manifest nor the repository tree declares a licence.
CAP services reading each other's HANA tables across HDI containers
Neither the package manifest nor the repository tree declares a licence.
CAP beershop on PostgreSQL, predating an official adapter
CAP service reading and writing MongoDB from custom handlers
Neither the package manifest nor the repository tree declares a licence.
Upload, edit and download ABAP table content as JSON, CSV or XLSX
Not an end-user app: it reads from any table the user names and writes into tables of the Z/Y namespace, with no authorisation check of its own, so the README asks a project to add its own checks on `S_TABU_DIS`/`S_TABU_NAM` and to restrict who may run it before it is used beyond a development system. XLSX upload and download are not ready for ABAP Cloud yet, and of the upload apps only the JSON one writes the file's rows back to the database.
Maps clipboard, Excel or text data onto a declared ABAP structure
Exports and imports ABAP table content as zipped JSON
Helper methods over abap2xlsx for Excel, JSON and tables
Reader for Excel spreadsheets in OpenXML format from ABAP
No published releases; repository quiet for 81 months.
MCP server with forty-five tools across a Datasphere tenant
It writes and it administers — ETL extraction and database user management are not read operations, and the same connection that profiles a column can move data out of the tenant. Masking is only as good as the configuration naming the fields, so an unlisted sensitive column is an unmasked one.
MCP server for BW/4HANA modelling objects
Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.
DuckDB extension reading SAP ERP tables, CDS views and BW queries
DataZoo GmbH calls the extension experimental and states that minimal testing and benchmarking were done. The Business Source License 1.1 it carries restricts offering the software to third parties on a hosted or embedded basis, so an embedding product needs a commercial licence. Telemetry is on by default and is switched off per session with `SET erpl_telemetry_enabled = false` or for the machine with `DATAZOO_DISABLE_TELEMETRY=1`.
ABAP class stripping invalid characters in BW end routines
No published releases; repository quiet for 24 months.
Framework for BW transformation start routines from a table
No published releases; repository quiet for 72 months.
MCP server for the SAP Analytics Cloud REST API
Ninety tools is a large surface to put in front of a model at once, and client-credentials OAuth means the tenant sees one identity rather than the person asking. Content transport and user management sit in the same tool list as reading a story.
Annotation-driven geocoding, address correction and routing for CAP
Nothing about it is readable from outside the package: there is no repository, no issue tracker, and the npm page carries no readme, so the README, the examples and the changelog can be read only from the tarball or a CDN mirror, and a bug has nowhere to be filed. Provider URLs are called from the plugin with API keys taken from environment variables in a .env file, so on BTP no call resolves through a destination and the keys live in the environment. The npm line stops at 1.0.1 on 3 November 2025; the changelog shipped inside that version is headed v2.1, so the version npm shows and the version the author counts are not the same.
Custom Table Editor editing table rows in an editable ALV grid
Release and repository quiet for 80 months.
Browser-based table maintenance UI built on abap2UI5
The app writes to whatever table is passed in the URL parameter `table` and carries no authorisation check of its own, so past a development system it needs authorisation checks added and a restriction on who may run it.
Generic ABAP table editor writing its own change documents
CAP services reading each other's HANA tables across HDI containers
Neither the package manifest nor the repository tree declares a licence.
Fork of cds-dbm with deploy, load, diff and drop tasks
Release and repository quiet for 39 months.
Delta deployment and migrations for CAP database adapters
Archived The declared repository is archived.
Functional boundary The repository is archived, so nothing here will move again. Fine to keep where it already runs; anything new should start from what the current cds deploy leaves open rather than from this.
CDS annotation vocabulary for entity search with schema discovery
The metadata is inconsistent: the declared repository is github.com/acme/search-vocab and the README installs @acme/search-vocab, neither of which matches the published name. One release, November 2025.
ABAP, Python and C code for similarity search over field descriptions
CAP Java plugin for soft delete with a softdelete aspect
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The Maven coordinate its README gives, io.github.miyasuta:cds-feature-softdelete:1.0.0, does not resolve on Maven Central as of 2026-09-07 — you build and install it from source.
CAP plugin turning DELETE into a flag on annotated entities
It changes what DELETE means for every client of the annotated projection, so anything that must actually remove a row — an erasure request, a retention job — has to go around it.
ABAP class for descriptive statistics over an internal table
Utility for update task database changes and internal tables in ABAP
Task tracker on a BOPF-backed CDS view with a Fiori list report
abapconf 2026 talk materials on RAP custom entities
Neither the package manifest nor the repository tree declares a licence.
Practice repository for the unmanaged RAP scenario
Practice repository for managed RAP with unmanaged save
CAP plugin stripping whitespace from strings on write via @cds.trim
CAP plugin uppercasing strings on write via @cds.uppercase
ABAP ADT MCP server published as an npm scope and plugin
A descendant rather than a distinct idea: if what you need is the ADT surface itself, its ancestors are entered here too and one of them may already be in your stack.
Agentic coding assistant in ABAP that runs as an SAP GUI report
VS Code extension editing ABAP systems over ADT as a filesystem
CLI that pulls and pushes ABAP packages as local files over ADT
A Python 3.10+ CLI, installed with pipx rather than through any SAP-provided package manager. Its own README lists what it does not do yet: where-used, syntax check and unit test runs — for those it says to reach for [ADT/Eclipse](external:eclipse) or an MCP server. First release, v0.1.0, and no standalone LICENSE file in the repository — the MIT grant is in the README and in pyproject.toml's project metadata rather than its own file.
abapGit package adding create, modify and delete tools to ABAP AI Code
MCP server turning a transport request into a WRICEF specification
Neither the package manifest nor the repository tree declares a licence.
MCP connector for ECC and on-premise S/4HANA with a licensed SAP side
Commercial Its maker offers it commercially.
Functional boundary The MIT licence covers the connector only: connecting to SAP needs a licensed ABAPilot backend installed in your system, so this is a commercial decision wearing an open-source badge on one half. Its own published checks did not cover writes, activation, transports or authorisation boundaries.
ABAP MCP server over ADT with a local journal that can undo writes
A system that reports itself productive, or whose role the probe cannot prove non-productive, is write-locked with no override, so changing code in production is not something this does. The permission ladder constrains the package, object name and transport request the server itself passes on a write, and is not a sandbox around ABAP it executes: `abap_run`, `abap_test` and the opt-in `core.eval` run under the connected technical user's SAP authorisations, which is where the boundary actually sits. Data preview, dump variable contents and driving a transaction by batch input stay off in every mode, `admin` included, until each is named explicitly.
Go MCP server that writes, activates and runs ABAP classes via ADT
Not reachable Not reachable since 2026-10-20.
Functional boundary `run_class` executes code in your system — that is the point and it is also the risk.
MCP server over the ADT REST API for ABAP objects
arc-1 extension for reading and maintaining BOPF enhancements
Classic BOPF only: business objects of the ABAP Programming Model for SAP Fiori are not handled, and on [the BTP ABAP environment](artifact:btp-abap-environment) or S/4HANA Public Cloud classic BOPF enhancements do not exist. It is version 0.1.0, verified on S/4HANA 2025 (SAP_BASIS 816) on-premise only, and [arc-1](artifact:arc-mcp-arc-1) still marks the plugin API it is built on as experimental. ARC-1 loads no extensions on its multi-target routes and offers none of these tools in its `hyperfocused` tool mode.
Edition of ARC-1 that runs ADT calls through adt-ls
Single-tenant today, one technical user, with per-user principal propagation on the roadmap — so a shared deployment cannot yet act as the developer who asked. The sibling edition [ARC-1](artifact:arc-mcp-arc-1) speaks ADT directly if you would rather not depend on the language server.
VS Code bridge between arc-1 and ADT for VS Code
The diff holds only while the object is inactive, since after activation the previous version is gone and a watched journal directory is what the maintainer points to instead. It adds no write path of its own: the IDE writes through SAP's extension, and the README states arc-1 can stay on `SAP_ALLOW_WRITES=false`. DDIC metadata files are skipped, because SAP's own stub for them says they are not supported in ABAP development tools for VS Code.
Eclipse add-on enabling the ADT MCP server with read-only tools
It lives inside Eclipse and inherits everything that implies — the session is a developer's, not a pipeline's. And it is version-bound: ADT 3.60 or newer for 0.5.1, with 0.3.x the path for ADT 3.58 and 3.59.
Eclipse plugin bringing Claude into ABAP Development Tools
MCP server for BW/4HANA modelling objects
Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.
MCP server scaffolding CAP and CDS checked by cds compile
ABAP MCP server with ADT tools and five authentication strategies
Built and last touched in the same week of March 2026, so the maintenance reading is what it is — the authentication work is the reason to look, and a stalled repository is the reason to read it before depending on it.
Claude Code plugin adding Custom_* tools to arc-1
Not for S/4HANA Public Cloud or [the BTP ABAP environment](artifact:btp-abap-environment), where the README states there is no `SUBMIT`, NAST or SOAP-RFC; the floor elsewhere is SAP_BASIS 7.50, the `/sap/bc/soap/rfc` service active, and an SAP user with `S_RFC` on the kit's function group as well as the authorizations for the reports and the spool. Print output is NAST messages only, so S/4 Output Management through BRF+ or APOC is outside it, and editing covers SmartForms alone, with Adobe Forms and SAPscript previewable but not editable. A report that opens a popup, calls a screen or is a dialog transaction cannot be run at all.
Fork of mcp-abap-abap-adt-api with 25 tools and session recovery
Freestyle SQL and `abap_run` mean an agent can read data and execute code, which is well past reading source. Neither is something to grant on a system where the distinction between development tooling and business data matters.
MCP server for ABAP on the ADT session, in Eclipse or standalone
In the Eclipse mode the server lives in a developer's IDE, binds to 127.0.0.1 and answers any request carrying an `Origin` header with HTTP 403, so a pipeline or a remote agent has nothing to reach; the standalone mode on the runtime of the ADT for VS Code extension is the documented route with no IDE open. A new connection starts in write mode, so the 11 write tools are live against a connected system until someone presses Toggle Read-Only. The dropins route for the two bundles is documented as untested.
C++ binary speaking the ADT REST API as a CLI and MCP server
A compiled binary rather than an npm package, shipped prebuilt per platform and through pip and uvx. It collects anonymous usage telemetry by default, switched off with `--no-telemetry` or `DATAZOO_DISABLE_TELEMETRY=1`. And the BW reach is what distinguishes it — if the work is plain ABAP, that half is weight you are not using.
Neither the package manifest nor the repository tree declares a licence.
ABAP MCP server with full CRUD on on-premise and ABAP Cloud
Two licences, by which package you install: the standalone server, `@mcp-abap-adt/core`, is AGPL-3.0-only, a licence to read before shipping anything built around it; the library, `@mcp-abap-adt/lib`, is Apache-2.0. The destination model also expects service keys sitting in a local directory, which is a secrets decision to make deliberately.
Native macOS code editor for ABAP and CDS
It runs on macOS only. Hammer Core Services, the part installed into the SAP system, needs that system on ABAP Platform 2023 or newer with SAP_BASIS 758 or newer, and installing it needs a user who can create development objects and run background jobs in that system.
MCP server in ABAP inside the application server, with agent skills
Its maker offers it commercially.
Policy-checked MCP server for ABAP development over ADT
Development and sandbox systems only: the README warns against pointing it at production. Transport release is never executed, since the tool exists to show the policy stopping it, and separation of duties is checked against the `identity.approvers` list in the policy file rather than against SAP authorisations, so it holds as far as that file does and no further. The write path has been tested with ABAP classes and other object types may need adjustments, there is deliberately no tool that creates or deletes an object, and one server instance serves one SAP system.
Write-oriented MCP server over abap-adt-api
Its own README opens by calling the server experimental. It also writes: locking, editing and activating in a system an agent can reach is a permissions decision before it is a tooling one.
Read-oriented MCP server fetching ABAP programs, classes, tables
Every tool its README lists reads — Get and Search, nothing that writes. Locking, editing, activation and transports are the other server, [mcp-abap-abap-adt-api](artifact:mario-andreschak-mcp-abap-adt-api), and mixing the two is how you end up with two MCP servers pointed at one system.
MCP server calling RFC-enabled function modules behind an allowlist
Real SAP calls need the proprietary [SAP NetWeaver RFC SDK](external:sap-nw-rfc-sdk) and the `pyrfc==3.3.1` release the README calls archived and yanked, on Python 3.11, so without those only the demo backend answers. Not over HTTP as it stands: credentials are read from the environment for stdio, and the README says not to expose the server over HTTP without implementing the MCP authorization specification and deployment-level rate limiting. Multi-tenant auth and RBAC beyond the one server-wide policy, rate limiting, metrics and tracing, and deployment packaging are listed as not built. The result limits protect the client and not the system, since the README states they cannot reduce work already performed inside SAP, and the MCP tool annotations that describe read and write risk are advisory metadata rather than an authorisation boundary, so the service account's `S_RFC` and table authorisations are still what decides.
Windows desktop manager handing SAP connections to assistants over MCP
MCP proxy pinning an agent's ABAP tools to one SAP system
MCP server reading ABAP short dumps over ADT
ABAP add-on serving business data and transactions as MCP tools
Its maker offers it commercially.
ADT extension for Eclipse and VS Code showing three SAP GUI tools
ADT-to-MCP bridge in Go reaching past what ADT exposes
Reach is the reason to use it and the reason to be careful: reading cluster tables and spool output goes well past what a development tool is normally pointed at. Decide what an agent may reach before granting it, not after.
Light MCP adapter for ABAP over ADT, documented in Korean
Read-only in practice, and the documentation is Korean; the tool names are English but the guidance around them is not.
arc-1 extension for SAPscript and Smart Forms objects
Smart Form content cannot be read or written, and HR Forms (`PE51`) are not implemented. Installing it needs SAP GUI or WebGUI once, to register the OData services in `/IWFND/MAINT_SERVICE` and to redefine the write service in `SEGW`, and the extension is built against a locally linked ARC-1.
Sample arc-1 extension in TypeScript with ten custom tools
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary It consumes the `@experimental` public API, which the README says may break in any release. The RFC tool dials as one shared technical user with its own credentials, so SAP's log records that user and not the person behind the agent.
LibreChat fork with four SAP MCP servers preconfigured
MCP server with forty-five tools across a Datasphere tenant
It writes and it administers — ETL extraction and database user management are not read operations, and the same connection that profiles a column can move data out of the tenant. Masking is only as good as the configuration naming the fields, so an unlisted sensitive column is an unmasked one.
ABAP MCP server over ADT with a local journal that can undo writes
A system that reports itself productive, or whose role the probe cannot prove non-productive, is write-locked with no override, so changing code in production is not something this does. The permission ladder constrains the package, object name and transport request the server itself passes on a write, and is not a sandbox around ABAP it executes: `abap_run`, `abap_test` and the opt-in `core.eval` run under the connected technical user's SAP authorisations, which is where the boundary actually sits. Data preview, dump variable contents and driving a transaction by batch input stay off in every mode, `admin` included, until each is named explicitly.
SAP AI Core APIs as MCP tools from one JSON config file
Configuration over an API you must already have entitled and provisioned; and the smallest of these repositories, so what it covers is what its config file happens to name.
Cloud Foundry V3 API on SAP BTP as MCP tools
It administers a live Cloud Foundry landscape: `Apps`, `Organizations`, `Spaces`, `ServiceInstances` and `SecurityGroups` all carry create, update and delete alongside list and get. What a caller can reach is set by the role they hold, and the three templates in `xs-security.json` are MCPViewer for read, MCPEditor for read and write, and MCPAdmin for full administrative access.
BTP Core Services as MCP tools with in-chat dashboards
It administers a real account through Core Services, so what it can change is what the caller can change. And the UI half depends on hosts that render mcp-ui or MCP Apps resources; elsewhere those five tools return markup nobody displays.
Exposes S/4HANA or ECC OData services as MCP tools
It puts create, update and delete on business entities behind natural language. Whatever the destination's principal may change, an agent may change — and "create a new customer" is a sentence, not a form somebody signed off.
MCP server with read tools over the SAP Cloud ALM APIs
MCP server generating tools from a CAP or OData V4 service's metadata
SAP Cloud Integration OData APIs as MCP tools
A thin declaration over CPI's APIs: it reaches what those APIs expose and nothing else, and it inherits whatever the tenant's own authorisations allow.
MCP server querying installations via the SAP Cloud ALM ITSM API
Neither the package manifest nor the repository tree declares a licence.
Python MCP server fetching sales orders from SAP's business data graph
Go MCP server over Cloud Integration packages and integration flows
Design-time only: no message monitoring, no deployment, no runtime status. That is a different server in this same section, and the two do not overlap.
MCP server for schema discovery and guarded SQL on SAP HANA
This is the database, not an application in front of it, so what an agent can read is whatever the connection user can read — the guardrails bound the shape of a query, not the sensitivity of what it returns. Grant the connection the rights you would grant a person.
Read-only MCP server over a local SAP Commerce Cloud's HAC
Not for production: the README states local and development instances only, and the server refuses a HAC URL whose host is not private unless `HAC_ALLOW_REMOTE=true` overrides that guard. Masking applies to `config_get` only, so `logs_tail` and `monitoring_info` output, thread dumps included, is unmasked and may carry sensitive data, and whatever a tool returns goes to the MCP client and its model. Certificate checks are disabled whenever `HAC_INSECURE_TLS=true` is set, which the README names as typical for local HAC.
MCP server in ABAP inside the application server, with agent skills
Its maker offers it commercially.
MCP server for the general Integration Suite functions
Neither the package manifest nor the repository tree declares a licence.
Java MCP server for Integration Suite Trading Partner Management
Neither the package manifest nor the repository tree declares a licence.
MCP server for Cloud Integration runtime: messages, logs, deployment
It deploys and undeploys, and it enumerates credentials, keystores and OAuth2 configurations. Listing security material is a read, and it is still a read of the thing that protects everything else the tenant talks to.
Read-only MCP server for exploring SAP Datasphere
Business Source License 1.1, which is source-available rather than open source: reading and evaluating are fine, and production use is restricted until the licence's change date. That is a procurement question, not a technical one, and it is the thing to settle first. Read-only also means read-only — no modelling, no loads.
MCP tools over SAP Focused Run's Landscape Management Database
It reads the landscape inventory, not the systems in it — nothing here reaches a running application, and nothing here changes anything. A landscape description is also commercially sensitive in its own right: versions and hosts are what a targeting exercise starts from.
Python MCP server for SAP Gateway OData operations
Python bridge generating MCP tools from OData v2 metadata
OData v2 only, and untouched since August 2025 — the same author's [Go port](artifact:oisee-odata-mcp-go) is where v4 support and the tool-explosion work went.
Go binary bridging any OData v2 or v4 service to MCP
Universal mode trades discoverability for size: one generic tool is harder for a model to pick correctly than a named one, which is why it is not the default. On a small service, standard mode is the better answer.
Config-driven proxy turning OData and REST endpoints into MCP tools
It fronts APIs you already have; nothing here reads a system's source or model, and a config file is only as good as the entity sets somebody wrote into it. OData V2 is the query surface it names.
MCP server calling RFC-enabled function modules behind an allowlist
Real SAP calls need the proprietary [SAP NetWeaver RFC SDK](external:sap-nw-rfc-sdk) and the `pyrfc==3.3.1` release the README calls archived and yanked, on Python 3.11, so without those only the demo backend answers. Not over HTTP as it stands: credentials are read from the environment for stdio, and the README says not to expose the server over HTTP without implementing the MCP authorization specification and deployment-level rate limiting. Multi-tenant auth and RBAC beyond the one server-wide policy, rate limiting, metrics and tracing, and deployment packaging are listed as not built. The result limits protect the client and not the system, since the README states they cannot reduce work already performed inside SAP, and the MCP tool annotations that describe read and write risk are advisory metadata rather than an authorisation boundary, so the service account's `S_RFC` and table authorisations are still what decides.
MCP server for the SAP Analytics Cloud REST API
Ninety tools is a large surface to put in front of a model at once, and client-credentials OAuth means the tenant sees one identity rather than the person asking. Content transport and user management sit in the same tool list as reading a story.
MCP tooling for SAP Business Data Cloud discovery and contracts
Business Source License 1.1: source-available, with production use restricted until the change date — settle that before anything technical. And the governed execution path in v0.2 does act on data, which is a different grant from the discovery the v0.1 baseline offered.
MCP server managing Delta shares in SAP Business Data Cloud
On ECC the S/4HANA `API_*` services that the three convenience readers default to do not exist, so each one has to be pointed at a Z service of your own or replaced by the RFC tools. `read_table` inherits `RFC_READ_TABLE`'s 512-byte row, so a wide table needs an explicit field list and some fields cannot be selected at all, and the bridge starts a Node process and a fresh logon per call, with no pooling. The audit log is one line per call that includes the call arguments, so every filter and WHERE clause sent to SAP is written to a file that then has to be handled as sensitive.
MCP server for SAP PI and PO monitoring and directory metadata
Inspection only, and it takes a host, a user and a password from the environment rather than a managed credential. PI and PO are also on their own end-of-maintenance path, which is the context any investment here sits in.
Read-only security analysis MCP server for SAP audits and SoD review
Read-only does not mean low-stakes: a complete picture of who can do what in an SAP system is exactly what an attacker would want, and the ready-made endpoint is the vendor's rather than yours — the README also documents running the server yourself. The authentication is careful; the question of what leaves your landscape is still yours.
MCP server with 62 tools over SAP SuccessFactors OData APIs
This is HR data — the most regulated business data most organisations hold — reached through a connection that sees whatever its principal sees. Employee records under natural-language query is a decision for whoever owns that data, not a configuration choice.
ABAP add-on serving business data and transactions as MCP tools
Its maker offers it commercially.