Marian Zeis
Entries
What adt-ls cannot do headless the maintainer puts out of scope, so a consumer that needs an ADT call the language server does not expose is back to speaking ADT itself. The README states the current runtime compatibility as verified on macOS arm64, against adt-ls 1.1.2 as the minimum and `1.1.2.202608131517` as the version tested. An Eclipse installation does not supply that runtime: SAP versions the two separately, so the VS Code extension has to be installed even where nobody opens VS Code.
TypeScript SDK over SAP's headless adt-ls language server
It stops at the `AuthInfo` and the raw bearer token, and the README lists what stays with the consuming server: rate limiting, the scope and tool policy, the MCP transport, the SAP HTTP client's headers, and helmet-style hardening. The one piece of hardening it constrains rather than defers is the cross-origin opener policy, which it deliberately leaves unset because popup-based OAuth breaks under it. It is ESM-only on Node 22 or later and shares the host's Express and MCP SDK instances as peer dependencies, so a server on Express 4 cannot take it.
XSUAA authentication stack for an MCP server on SAP BTP
The maintainer states it is unofficial, not endorsed by SAP, and that it automates authenticated SAP web endpoints and browser session cookies in ways SAP's terms of service or an organisation's own policies may restrict. Password login is confined to `accounts.sap.com` and the standard SAP Cloud Identity Services tenant domains: a custom IAS domain, or a login that conditional authentication delegates to a corporate identity provider, fails closed before the password is filled and has to be completed through an interactive login instead.
Browser login and session module for SAP MCP servers
No published releases; repository quiet for 52 months.
UI5 custom control formatting dates with Day.js
MCP server over the ADT REST API for ABAP objects
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.
Edition of ARC-1 that runs ADT calls through adt-ls
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 add-on enabling the ADT MCP server with read-only tools
Spreadsheet upload into a CDS entity, parsed on the server
It reads documentation, never a system: nothing in it opens a package.json, a CDS model or an ABAP client, so a question about what your own project does has to be answered elsewhere. The offline half is only as fresh as the submodules the last build pinned, and the index answers where something is written down rather than which of two packages fits a task.
MCP server searching seventeen SAP documentation repositories
The maintainer states 0.x is beta with no production SLA, and scopes support deliberately narrowly: direct application-server transport, classic serialization and password authentication on S/4HANA 2023 and NetWeaver 7.50. Anything outside that is untested rather than unsupported.
SDK-free TypeScript client for SAP synchronous RFC on Node.js
It says so itself, in bold, and the atlas repeats it: not legal advice and not a compliance decision. Only SAP, your contract, or SAP support can answer bindingly, and the skill routes legal, commercial and roadmap questions there rather than guessing at them. Treat the output as evidence gathered, not as a verdict.
Skill assessing API usage against the SAP API Policy
The maintainer states it is unofficial, not endorsed by SAP, and that it uses authenticated Hub web and catalogue endpoints and browser session cookies in ways SAP's terms of service, SAP account terms or an organisation's own policies may restrict. The same README asks the reader not to use it for production, broad distribution or shared access without explicit approval, and says that installing it grants no permission to automate SAP services.
Read-only MCP server over the SAP Business Accelerator Hub
A diagram of anything other than an SAP, BTP or on-premise landscape: the skill is tuned to the Horizon style and its 71 templates. It drafts rather than finishes, and its README budgets 15 to 30 minutes of edits in draw.io per diagram. Without Python the validator does not run.
Claude Code plugin and skill drawing validated BTP diagrams
It needs an S-user with SAP Support Portal access, so there is nothing to search without a support contract behind the login. The maintainer states it uses private SAP APIs behind authentication, asks the reader to check whether that use breaches SAP's terms of service, and disclaims both liability and any guarantee that it keeps working. MFA is handled only by typing the code into a visible browser, so a headless deployment cannot complete a login that demands one.
MCP server searching and fetching SAP Notes and KBAs
What it returns is planning material, not a commitment, and the monorepo labels the server's role "future/planned features (planning only)". The maintainer also states it is unofficial, not endorsed by SAP, and that it uses authenticated Road Map Explorer web endpoints and browser session cookies in ways SAP's terms of service or an organisation's policies may restrict, with production, broad distribution and shared access called out as needing explicit approval. An account that requires MFA has to be bootstrapped once through a visible browser.
MCP server over SAP Road Map Explorer
Quiet Release and repository quiet for 41 months.
Functional boundary The case it is written for is a document that has not been uploaded; anything already served from a URL is what the framework's own PDF control takes. Passing a document as a data URI means holding it in the page as a string first, which is a different cost from streaming it from a server.
UI5 custom control rendering a PDF from a base64 data URI
UI5 component adding a spreadsheet upload dialog to Fiori apps
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary It reports what the change log says, not what your application uses, so it cannot tell you which of the listed changes touches your code. The repository carries no licence file, which leaves the code itself with no grant attached even though the hosted app is open to use.
Hosted app listing changes between SAPUI5 or OpenUI5 versions
It records what the app actually asked for, so an entity no recorded journey touched is not in the dataset and replay will not answer for it. Its own README asks for `fiori-tools-appreload` to be disabled while recording, because a reload loop is what happens otherwise.
UI5 middleware recording OData traffic as mock server datasets
UI5 Tooling v4 extension that registers other extensions
UI5 Tooling task writing the service name into the importer manifest
Local desktop workspace for AI conversations with SAP connectors
Open SQL editor for ABAP with ALV output
The Markdown is a snapshot of whatever help.sap.com served when the pipeline last ran, and the Standard library is scraped from the `latest` index, so which release a page describes follows from the scrape date rather than from anything the corpus states. `package.json` states ISC and the repository carries no LICENSE file, so what the copied SAP documentation may be used for is not stated in it.
ABAP Keyword Documentation as Markdown with indexes
MCP server for SAP BTP and Cloud Foundry acting as the logged-in user
Neither the package manifest nor the repository tree declares a licence.
CAP sample drawing a material BOM as a UI5 network graph
Neither the package manifest nor the repository tree declares a licence.
Local chat client for SAP questions with a CAP LangGraph backend
Neither the package manifest nor the repository tree declares a licence.
CAP and UI5 app for in-place table maintenance with SmartTable
Benchmark of LLM ABAP code generation against a real SAP system
LibreChat fork with four SAP MCP servers preconfigured
Neither the package manifest nor the repository tree declares a licence.
UI5 apps calling CAP OData actions and functions from custom code
Neither the package manifest nor the repository tree declares a licence.
Two UI5 apps consuming one npm package in two ways
Neither the package manifest nor the repository tree declares a licence.
Ten exercises on the Fiori elements mock server middleware
Neither the package manifest nor the repository tree declares a licence.
Five MCP servers whose tools return a prebuilt UI
Neither the package manifest nor the repository tree declares a licence.
pnpm workspace running CAP, a local launchpad and two UI5 apps
Generates an MCP server from annotated CDS entities and actions
Fiori Elements mock server plugin taking a CDS file as metadata
UI5 Tooling command line for project setup, dev server and build
Static analysis tool for UI5 projects
Every skill that touches ABAP needs [arc-1](artifact:arc-mcp-arc-1) itself connected to a real system; nothing else is universal. `modernize-ui5-app` and `convert-ui5-to-fiori-elements` specifically need [the UI5 MCP server](artifact:ui5-mcp-server) for TypeScript conversion guidance and the linter, `convert-ui5-to-fiori-elements` also needs [the Fiori MCP server](artifact:sap-ux-fiori-mcp-server) for its LROP scaffold, and `modernize-ui5-app` needs a browser MCP (Claude in Chrome or Claude's own Preview) for its final render-verification step, since an HTTP 200 alone does not catch a blank page. A skill file alone, without the servers a given skill needs, has nothing to act on.
Twenty-two agent skills shipped with arc-1
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.
Sample arc-1 extension in TypeScript with ten custom tools
Archived The declared repository is archived.
Functional boundary With one SAP system the README says to point the client at that arc-1 directly. Version 1 exchanges tokens within a single subaccount, so backends spread across subaccounts are out; it keeps its session map in memory, so more than one instance needs sticky sessions or a shared store. It routes deterministically and runs no model, which is a different thing from an assistant that reasons across systems. The `/all` endpoint drops the per-connection isolation, and the maintainer's answer to that is a PROD backend set read-only at the SAP end rather than a tool surface that hides the writes.
Hub on SAP BTP putting several arc-1 instances behind one login
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.
VS Code bridge between arc-1 and ADT for VS Code
Neither the package manifest nor the repository tree declares a licence.
Simple CDS bookshop model used across CAP explanations
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.
Exposes S/4HANA or ECC OData services as MCP tools
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 for BW/4HANA modelling objects
MCP server with read tools over the SAP Cloud ALM APIs
Sources of capire, the CAP documentation
Sandbox launchpad for all SAPUI5 apps in a CAP workspace
For a deployed application's UI. The README adds it with `npm add cds-plugin-ui5 -D`, a development dependency of the CDS server, and states nothing about a build or a deployment.
UI5 CLI middlewares running inside the CDS server
npm initializer adding wdi5 testing to an existing UI5 app
Release and repository quiet for 33 months.
Yeoman generator for UI5 tooling-extension projects
Not for a single-application project with no deployment configuration: for that the README points to [generator-ui5-app](artifact:ui5-community-generator-ui5-app) instead.
Yeoman generator for UI5 projects holding several applications
Easy-UI5 generator scaffolding a TypeScript UI5 application
Generator for a TypeScript UI5 FlexibleColumnLayout app on OData
Easy-UI5 generator scaffolding a TypeScript UI5 library
LISA does the translation step only: it does not discover objects or manage transports, and its README pairs it with [an ADT MCP server](artifact:sap-adt-mcp-server) for those. Every write needs a transport request, and which object types it can write differs between public cloud or [the SAP BTP ABAP environment](artifact:btp-abap-environment) and on-premise or private cloud, and by release. Running it locally is meant for development and testing, not production.
MCP server for reading and writing ABAP object translations
CAP data model of many-to-many relationships on a Star Wars dataset
UI5 app template deploying the Spreadsheet Importer once to ABAP
Neither the package manifest nor the repository tree declares a licence.
Adaptation project adding spreadsheet upload to Manage Banks
Neither the package manifest nor the repository tree declares a licence.
Manage Banks adaptation updating existing records from a spreadsheet
CAP Risks and Mitigations project with a Spreadsheet Upload button
UI5 app opening the Spreadsheet Importer on on-premise OData services
Neither the package manifest nor the repository tree declares a licence.
UI5 app opening the Spreadsheet Importer on its own
UI5 app carrying 18 UI5 CLI extensions in one configuration
Release and repository quiet for 38 months.
UI5 custom control rendering Markdown to HTML
UI5 middleware syncing interactions across browsers over websocket
UI5 middleware serving a chosen welcome page at the root path
Live reload middleware for the UI5 dev server
UI5 middleware logging in with Playwright and reusing the session
UI5 middleware serving a locally built UI5 framework
UI5 middleware serving static resources from a path or npm package
Dev-server middleware proxying requests to a backend system
UI5 middleware including one UI5 application in another
UI5 middleware serving static resources from JAR files (WebJars)
UI5 builder task flattening library output for SAP NetWeaver
UI5 builder task checking XML views for missing i18n texts
UI5 builder task minifying XML views and fragments
UI5 builder task turning a UI5 app into a progressive web app
UI5 Tooling task transpiling TypeScript and ES modules
Build task packaging the UI5 build result as a zip archive
Command line running UI5 QUnit and OPA tests in parallel
UI5 tooling extensions loading npm packages as UI5 modules
TypeScript UI5 app consuming custom UI5 CLI extensions together
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.
ADT-to-MCP bridge in Go reaching past what ADT exposes
Where the login cannot be completed by configuration. Its authentication page states that multi-factor authentication is not supported, because a media break between browser and phone cannot be managed out of the box.
End-to-end testing for UI5 on WebdriverIO with UI5 control selectors
Writing and topics
IN TOPICS
onedevatlas is open for browsing. Find tools for SAP development, compare their documented capabilities, ask your AI assistant, and join a flight during TechEd week.
Details
History
- @marianfoo/sap-mcp-authRe-read against the README as it stands today. "No token endpoint" and "there is no client-credentials flow to use instead" were absence claims about SAP's portals that no source makes, so they are gone and the paragraph now says what the module does and whom it serves. The maintainer's own unofficial caveat, and the origins password login refuses, are in when_not_to_use. The package block states that it is imported into the caller's own program and installed from npm. The README names [Cloud Identity Services](artifact:btp-cloud-identity-services) as the tenant the login goes to, which is an edge rather than a phrase in a paragraph.
- ui5-fe-mockserver-tutorialform is tutorial, on the README's first line: "Tutorial for using `@sap-ux/ui5-middleware-fe-mockserver` in SAP Fiori development." The repository was published for Devtoberfest 2025 and the SAP Community post the README links calls it a tutorial from Devtoberfest, so workshop was considered and left out: form is one value, and what this presents itself as is a tutorial with exercise folders, not CodeJam material.
- ui5-fe-mockserver-tutorialThe README's Prerequisites tell the reader to clone and run that CAP project before starting, and the fact was already in what_it_solves with no edge under it. artifact:marianfoo-ui5-call-action was a pending draft when this entry was written and is published now, so the plain link in the prose became a graph link in the same pass, as did ui5-middleware-odata-recorder.
- WerkbankWhat Werkbank adds for ABAP, CAP and UI5 is its catalog of development skills; the workspace itself is not specific to any of those stacks. Agent workspaces is narrowed back to BTP.
- @arc-mcp/xsuaa-authThe BTP door now compares its authentication options on whether the signed-in identity reaches the next system. The README's sentence about the `./btp` entrypoint states it for this package, and it was read again on this date.
- sap-architecturecapability:agent-guidance declared the installs_into property on the BTP door. The README states the skill is portable and then names the instruction file for each tool in a table, so the statement is the portability sentence and each value carries the row that names it. The table also names Jules, Amp and Factory, which are outside the property's values and are left for the curation queue rather than entered as written.
- sap-architectureThe entry said other agents can run it and not what that costs. The README's own caveat, read on 2026-10-15, is that the auto-load is Claude's alone, which is the difference between this option and a Claude-only one.
- WerkbankThe project homepage describes "A small, curated shelf of MCP servers and SAP development skills." Its own catalog spans ABAP (ARC-1 and ABAP Cloud), CAP (CAP Upgrade), and UI5 skills; the workspace is not specific to one stack. This intake follows the maintainer’s explicit request after the September source sweep passed it over for lacking a workspace capability; that concern now exists as Agent workspaces. The served views describe which users the project-owned install catalog addresses. Werkbank provides the workspace; each selected connector or skill supplies the stack-specific behavior. No SAP implementation capability is attributed to Werkbank itself.
- arc-1The licensing side is its explicit SAP API Policy relation, sourced to its README; the rest restated what any server in front of ADT is. Removed at the atlas maintainer's request on 2026-10-14.
- arc-1Re-read against the README, the npm registry record, the extensions page and the release notes on 2026-10-04, with arc-1 at 1.5.0 published 2026-10-02. Every claim the entry already carried still holds word for word, so the checked dates move and the text does not, except where the documentation says something the entry did not. Two such things: `Custom_*` tools an operator registers without forking, which the corpus already recorded on [claude-sap-kit](artifact:silvius1996-claude-sap-kit) and not on the server those tools run in, and one agent plugin that installs the server together with [ARC-1 Skills](artifact:arc-mcp-arc-1-skills). The seven guardrails added were stated when the entry was written and left out of it; they are quoted, not counted. The `run_code` facet stays absent: the extensions page gates class and report execution behind two flags and a plugin the operator writes, which is not the server stating that it runs code.
- arc-1The connection is what the README states the server fronts (docs/concepts/design-roles-and-interfaces.md, P1), and it attaches the system's entry. The two BTP connections are stated under the README's Cloud Foundry deployment heading, so they carry that condition; the Destination service's sentence states identity forwarding and no data flow, and the ABAP environment's sentence names no protocol. The README's credits table names abaplint as what the linter uses. Two older defects go with it: a nested link that rendered its outer bracket as text, and abap-adt-api named in the same quoted sentence as the other two inspirations and carried by no edge.
- @marianfoo/sap-mcp-authEntered with the three servers of the same monorepo that name it. It publishes on its own and answers a question of its own — how a tool outside SAP gets an authenticated session against an SAP portal — so it is an entry rather than an implementation detail of the three.
- abap-docsEntered as the repository behind two sentences the corpus already rests on. capability:documentation's abap framing says "The ABAP keyword documentation, the cheat sheets and the RAP tutorials are public repositories", and for the keyword documentation the public repository is this one, not SAP's: mcp-sap-docs carries it as the `abap-docs` submodule (https://github.com/marianfoo/abap-docs.git in .gitmodules), which is where its `abap-docs-standard` and `abap-docs-cloud` offline sources come from. doc-source rather than a provider, because that same capability's abap note states publishing a corpus is not answering the concern. identity.license is the `license` field of package.json; the GitHub API reports no licence for the repository, which is the second sentence of when_not_to_use.
- cap-materialbom-graphDrafted from the repository's own files, because its README is the unedited `cds init` template and the only sentence the maintainer wrote about it is the repository description, "This is a sample to show the Material as Network Graph in a Fiori elements app": db/schema.cds for the model and the GraphNetwork pseudo-entity, srv/service.js for the READ handler that walks the bill of materials, app/material/webapp/manifest.json for the list report and object page generated from `@sap/generator-fiori:lrop` and the custom section, the graph fragment for `sap.suite.ui.commons.networkgraph`, and package.json for `@sap/cds` ^8 and `@cap-js/sqlite`. artifact_type sample and use_as starting-point are a placement: one commit, a local SQLite run and no deployment described. domain ui-and-frontend-bridge follows the half of it the sample is about, as on cap-sflight. No licence is recorded: the repository has no LICENSE file and package.json carries the `cds init` defaults "license": "UNLICENSED" and "private": true.
- ui5-errorhandler-sampleIts own README states the subject: "This sample shows how to use npm packages", with "How to consume a UI5 AMD style module" and "How to consume a classic js class" as the two examples. That places it on capability:ui5-build-tooling, where artifact:ui5-community-ui5-tooling-modules already sits, rather than anywhere near error handling: the error handler is the payload being consumed and not what the sample teaches. demonstrates rather than provides, because a sample is evidence. compat.runtimes is package.json's @ui5/cli devDependency. The last description sentence is the README's `"@marianfoo/ui5-errorhandler": "^0.0.4"` set against package.json's `"@marianfoo/ui5-cc-errorhandler": "^0.0.1"` on main, both read on 2026-09-25. The library itself, marianfoo/ui5-errorhandler, was read in the same batch and not drafted; see the manifest note. GitHub reported this repository as a fork on 2026-09-25 and its README credits easy-ui5 rather than an upstream repository, so no lineage is written here: the fork flag is crawled and lineage needs the maintainer's own sentence.
- ui5-fe-mockserver-tutorialSample with use_as reference, following artifact:sap-samples-manage-apis-codejam: a repository of exercises is evidence that something works and never an option to depend on. It demonstrates capability:ui5-testing because that capability's core coverage already names "an OData V2 mock server for a backend stand-in" as what SAP ships, and capability:ui5-build-tooling because the mockserver is registered as UI5 Tooling custom middleware in ui5-mock.yaml. compat.runtimes is the README's Required Tools, "**Node.js** (20 LTS or higher)". @sap-ux/ui5-middleware-fe-mockserver, the middleware being taught, has no entry of its own, so it stands in the prose as a code span and the README's own pointer to SAP/open-ux-odata is linked out. No licence is stated anywhere in the repository, so identity is absent.
- ui5-plugin-loaderbuild-tool and capability:ui5-build-tooling for the same reason its four named neighbours carry them: it is registered in the customMiddleware and customTasks blocks of ui5.yaml and does its work inside `ui5 serve` and `ui5 build`. compat.runtimes is the README's Requirements section, "**Node.js v18.0.0 or higher**"; identity.license is the README's License section and the npm record, both MIT. No flavors: the README states no UI5 flavor, and absent is not a claim. One discrepancy for an editor rather than the entry: the npm record for ui5-plugin-loader 0.2.0, published 2025-07-23, gives its repository as git+https://github.com/marianzeis/ui5-plugin-loader.git, while the source read here is github.com/marianfoo/ui5-plugin-loader; the npm description, "Auto-mounts UI5 tooling extensions based on manifest JSON files", and the 0.2.x version line both match this README.
- btp-cf-mcpRead out of the marianfoo account listing. Entered as a starting-point, since the maintainer's own status line calls it "a working proof-of-concept", so its boundaries sit in description.to_build_on_it rather than in a warning. capability:mcp-servers already reads core-only on the BTP door because every provider there is SAP-published; this is an independent one, which is a reading the capability will have to move.
- SAP API Policy Evidence SkillThe entry described the skill as gathering evidence "through MCP servers" without naming one, because four of the five were not in the corpus. Three entered in the same batch as their own packages, and mcp-sap-docs and arc-1 were already here, so the README's own prerequisites table becomes edges. Conditional rather than required: the README states the skill degrades gracefully when one is missing and names which two raise confidence to high.
- sap-api-hub-mcp[The SAP API Policy Evidence Skill](artifact:marianfoo-sap-api-policy-skill) was entered on 2026-09-10 naming this server as what proves an API's Published-API status, and the server itself was not in the corpus. Entered as its own package, from its own README, because the monorepo publishes each server to npm independently.
- sap-note-search-mcpThe decline recorded for candidate:marianfoo/mcp-sap-notes on 2026-09-10 named this as the successor and as an open gap: "SAP Notes search is a real gap in the corpus and the thing that fills it has to be found some other way." Entered from the monorepo package rather than the archived repository, and from the package's own README.
- sap-roadmap-mcpNamed in [the SAP API Policy Evidence Skill](artifact:marianfoo-sap-api-policy-skill)'s prerequisites as the source for replacement APIs, and absent from the corpus. Entered as its own package, from its own README, because the monorepo publishes each server to npm independently.
- ui5-cc-pdfviewerRead out of the marianfoo account listing. No lineage edge: the README states the fork of lemaiwo/UI5LabLibraryPDFViewer, and that repository is not in the corpus, so the fact is carried in the description rather than pointed at an id that does not resolve.
- ui5-lib-diffRead out of the marianfoo account listing. capability:documentation reads core-only on the UI5 door on the grounds that every provider there is SAP-published; this is an independent one, so that reading needs reassessing rather than carrying over.
- ui5-middleware-odata-recorderRead out of the marianfoo account listing. Two provides edges because the two halves are different claims: it is a UI5 server middleware, and what it produces is the mock-server dataset that capability:ui5-testing's core coverage already names as the framework's backend stand-in.
- arc-1Corrected against the README, which documents a shared-credential mode (technical user) beside per-user identity.
- arc1-adt-abap-mcp-extThe cited sentence is no longer in the README: from 0.5.1 the plugin only contributes tools to SAP's supported server; waking the dormant one was 0.3.x.
- mcp-sap-docsCorrected against the README: its offline-sources table lists seventeen repositories, abap-docs-standard through wdi5.
- arc-1-lspTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
- arc1-adt-abap-mcp-extTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
- open-rfcA Node.js RFC client serves whoever calls a function module, and that is a CAP or Node developer; an ABAP developer exposes the module and never installs this. It was listed behind the ABAP door with no concern there to answer.
- SAP API Policy Evidence SkillTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.
- arc-1docs/NEIGHBOURS.md §2 assigns ARC-1 the posture ingest — as an entry — and §3.1 names its author, but nothing in data/artifacts held it. Entered as the artifact the posture calls for, and it is the first provider of capability:abap-agent-tooling in the corpus.
- arc-1abap-agent-tooling generalised into agent-code-access: the same concern exists in CAP, and the ABAP framing keeps the local name.
- mcp-sap-docsNamed in docs/NEIGHBOURS.md §3.1 as a project of the bestofcapjs author but never entered. It is a documentation retrieval server, not an index of options — the complement posture the same section assigns ARC-1, and hard rule 5 makes it exist here only as an attached entry.
- First entry seenDiscovered via GitHub API · arc-mcp, GitHub organisations and accounts · marianfoo, GitHub API · marianfoo, sap-ai-mcp-servers, The discovery pass · npm, GitHub API, The maintainer, claiming it, Added by hand, Added by hand · spreadsheetimporter organisation repositories, GitHub organisations and accounts · github-orgs:marianfoo.
Profile
For your agent
- Ref
actor:marianfoo- JSON
- /actors/marianfoo.json
- MCP
- Connecting an agent