2026-10-15@sap-ai-sdk/foundation-modelsprovides[llm-integration].facets, what_it_does, sources → the stream method named, the foundation-models chat-completion page cited, and both properties the capability declarescapability:llm-integration declared model_access and response_streaming on 2026-10-15. The package's own chat-completion page, read the same day, states that its chat client streams over server-sent events, which is the fact that decides whether a chat surface can show an answer as it is written; the edge rested on the repository README alone before.
2026-10-15@sap-ai-sdk/orchestrationprovides[llm-integration].facets, what_it_does, sources → the model choice and the stream method named, two further sources, and both properties the capability declarescapability:llm-integration declared model_access and response_streaming on 2026-10-15. The orchestration chat-completion page, read the same day, states that the model is the name property of the promptTemplating configuration and that the harmonised API behind it lets a different model be used without the client code changing, and that the client streams over server-sent events. Both facts decide something for a reader and neither was on the edge.
2026-10-15@sap-ux/telemetryprovides → what it does for telemetry, from its own READMETelemetry curation for the CAP door. The entry stood among the options a reader compares for observing a running CAP service, and its own README places it elsewhere: a library SAP Fiori tools use to collect anonymous usage data. The sentence is recorded so the page states what it is; whether the edge, the cds-plugin type and the CAP door are right is left for review rather than changed here.
2026-10-15@sap/joule-studio-clidescription, provides, links.docs → both joule and jl in the published packageCurrent npm README for 2.0.4, published 2026-10-07, says "Installing `@sap/joule-studio-cli` gives you two commands:" and lists joule and jl. SAP Help now installs this package for the new Studio workflow. The historical alpha package stays separately indexed; no unverified rename or lineage relationship is inferred.
2026-10-15Joule Studioecosystem → umbrellaThe product overview describes "Workflows and integrations for both SAP and non-SAP systems." It also names CAP development; RA0029 places customer agents on BTP. These establish served views, while the new SAP-managed environment has no separate BTP catalogue listing established by this intake.
2026-10-15Joule Studioartifact_type, links.docs, provides → web-tool; product tutorial; MCP and A2A statedThe browser builder and managed runtime do not establish a separately subscribed and bound BTP service. Keep CAP and BTP as served views: the product overview names CAP development, and the current SAP Help tutorial requires "An SAP S/4HANA system configured with an SAP BTP destination." The architecture chapter is titled "Building AI Agents with SAP Joule Studio on SAP BTP" while distinguishing the SAP-managed runtime from Bring Your Own Agent in a customer subaccount. The CLI link is backed by the current npm README, which now ships both joule and jl; its atlas record is revised in the same batch. The positive basis for web-tool is SAP’s description of a visual browser-based builder with no local setup. It identifies the hosted development interface, including provisioned access; it does not classify the runtime as an unbound or customer-hosted service.
2026-10-12API Managementprovides[mcp-servers].facets and what_it_does → [{"key":"mcp_exposure_source","value":"Integration Cell OData/REST API artifact, classic API proxy, HTTP OpenAPI 3.0.0–3.0.3 or selected RFC backend"},{"key":"mcp_operations","value":"Selected source-API operations become tools; retrieval/create/update/delete depend on that API contract"},{"key":"mcp_context","value":"Resource URI/MIME schemas, prompt templates and API-operation tool input/output schemas"},{"key":"mcp_execution_path","value":"MCP gateway routes backend API calls; MCP server deployment is Integration Cell-only even when the source proxy uses the classic runtime"},{"key":"mcp_exposure_control","value":"Select API operations/resources for tools and configure resources/prompts; HTTP-endpoint configuration requires Authentication and Authorization policies"}]The comparison distinguishes execution and surface selection at the stated runtime, retaining conditional operations and target restrictions.
2026-10-12API Managementprovides.mcp-servers.facets.mcp_exposure_source.value → API artifact; API proxy; HTTP/OpenAPI endpoint; RFC backendConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
2026-10-12API Managementprovides.mcp-servers.facets.mcp_context.value → MCP resources; MCP prompts; Tool input/output schemasConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
2026-10-12API Managementprovides.mcp-servers.facets.mcp_execution_path.value → Remote backend callsConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
2026-10-12API Managementprovides.mcp-servers.facets.mcp_exposure_control.value → API operation selectionConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
2026-10-12API Managementdescription.when_not_to_use → A deployment with a hard tool-count requirement needs its limit confirmed: the API-artifact and HTTP-endpoint creation guides state 30 tools, while the HTTP-endpoint configuration guide states 50.Preserves the documented 30/50 tool-limit conflict as a condition for selecting a deployment; the HTTP creation-guide quotation is now attached explicitly alongside the API-artifact and configuration citations.
2026-10-12API Managementprovides[mcp-servers].what_it_does → Creates an MCP server from an Integration Cell OData/REST API artifact, a classic API proxy, an HTTP OpenAPI endpoint or an RFC backend, with selected operations exposed through the MCP gateway. MCP deployment requires Integration Cell even when a source proxy runs on the classic runtime; API-artifact sources must use OAuth and the HTTP specification must be OpenAPI 3.0.0–3.0.3. The gateway routes backend API calls, and selected API operations become tools with input/output schemas. Resources have URI/MIME schemas and prompts use templates. HTTP-endpoint configuration requires Authentication and Authorization policies.Resolves the requested review findings while preserving the structured comparison values, runtime scopes and implementation restrictions.
2026-10-12API Managementdescription.when_not_to_use → Removed; the documented 30/50 MCP tool-limit discrepancy is retained on provides[mcp-servers].what_it_does.Independent review found that the MCP-specific uncertainty does not describe a situation in which the whole API gateway service is the wrong choice.
2026-10-12API Managementprovides[mcp-servers].what_it_does → Creates an MCP server from an Integration Cell OData/REST API artifact, a classic API proxy, an HTTP OpenAPI endpoint or an RFC backend, with selected operations exposed through the MCP gateway. MCP deployment requires Integration Cell even when a source proxy runs on the classic runtime; API-artifact sources must use OAuth and the HTTP specification must be OpenAPI 3.0.0–3.0.3. The gateway routes backend API calls, and selected API operations become tools with input/output schemas. Resources have URI/MIME schemas, prompts guide agent interactions with tools, and HTTP-endpoint configuration requires Authentication and Authorization policies. The API-artifact and HTTP-endpoint creation guides state a limit of 30 tools per MCP server, while the HTTP-endpoint configuration guide states 50.Independent source review supports prompts guiding agent interaction rather than templates; retains both sourced tool-count limits as an explicit MCP-specific discrepancy.
2026-09-27@sap_oss/vscode-mta-toolslinks.repo → https://github.com/SAP/app-studio-toolkit/tree/main/projects/vscode-mta-toolsThe old repository's README says it has moved to the app-studio-toolkit monorepo; the edge now cites the README at the new address.
2026-09-20API Managementprovides → capability:mcp-servers, capability:tool-governanceMoved here from SAP Integration Suite. SAP files MCP Server under API Management in its documentation, and every creation path read lists the activated API Management capability as a prerequisite.
2026-09-17SAP Document Management service, integration optionserves_ecosystems → ui5, capAdd CAP to served ecosystems from documented CAP integration; preserve the existing BTP/UI5 contribution and source dates. CAP plugin restrictions do not apply to the service itself.
2026-09-14@sap-ai-sdk/orchestrationprovides → capability:llm-integration, capability:prompt-management, capability:data-masking, capability:content-filteringPrompt management, data masking and content filtering entered as capabilities on 2026-09-14, each an orchestration module in SAP AI Core; this package is the client for all three and carried only the broader LLM integration edge.
2026-09-14@sap-ai-sdk/prompt-registryprovides → capability:llm-integration, capability:prompt-managementPrompt management entered as a capability on 2026-09-14 with SAP AI Core's Prompt Registry as the core answer; this package is that registry's client and had only the broader LLM integration edge.
2026-09-09@sap-ux/fiori-mcp-serverprovides → capability:agent-code-accessMCP is how this is delivered, not what it answers — artifact_type carries the transport. It helps an agent work on real code rather than exposing a running service to one, which is a different capability.
2026-09-09@sap-ux/fiori-mcp-serverecosystem → ui5It creates and edits Fiori applications and ships from SAP/open-ux-tools; nothing about it is CAP's. Typed cap by placement, which defaults every candidate to the primary door. serves_ecosystems keeps it behind the CAP door, where a CAP developer building a Fiori front end still finds it.
2026-09-09@sap-ux/fiori-mcp-serverlinks.docs → https://github.com/SAP/open-ux-tools/tree/main/packages/fiori-mcp-serverlinks.repo is the whole of SAP/open-ux-tools, which carries much else besides this. Naming the package directory says which part of the monorepo the artifact is — and it is what lets a sweep tell this entry apart from the next package in the same repository.
2026-09-08@sap-ai-sdk/ai-apiartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ai-sdk/ai-apidescription.one_line → The AI Core API surface of SAP's AI SDK — deployments, configurations and the rest of the control plane, as opposed to calling a model.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-ai-sdk/coreartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ai-sdk/coredescription.one_line → The shared internals of SAP's AI SDK, which its own readme says is not meant to be depended on directly.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-ai-sdk/foundation-modelsartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ai-sdk/foundation-modelsdescription.one_line → Calls foundation models through SAP AI Core and the Generative AI Hub, which is the package an application actually reaches for.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-ai-sdk/orchestrationartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ai-sdk/orchestrationdescription.one_line → The Orchestration Service client — templating, grounding, filtering and masking applied around a model call rather than in the application.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-ai-sdk/prompt-registryartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ai-sdk/prompt-registrydescription.one_line → Prompts kept in SAP's registry rather than in the codebase, so changing one is not a deployment.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-cloud-sdk/connectivityartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-cloud-sdk/connectivitydescription.one_line → Destination lookup and the connectivity proxy — the package that turns a destination name into a reachable endpoint with credentials attached.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-cloud-sdk/http-clientartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-cloud-sdk/http-clientdescription.one_line → The HTTP client that carries a destination's credentials, so an outbound call inherits the authentication rather than assembling it.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-cloud-sdk/odata-commonartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-cloud-sdk/odata-commondescription.one_line → The shared machinery under the SDK's OData and OpenAPI client generators; a dependency of the generated clients rather than something written against directly.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-cloud-sdk/openapiartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-cloud-sdk/openapidescription.one_line → Generated OpenAPI clients for the Cloud SDK, so a REST API described by a specification is called through typed functions.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-cloud-sdk/resilienceartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-cloud-sdk/resiliencedescription.one_line → Timeouts, retries and circuit breaking around a remote call, so one slow downstream system does not take the application with it.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-cloud-sdk/utilartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-cloud-sdk/utildescription.one_line → General utilities shared across the Cloud SDK packages — a dependency, not a thing to reach for on its own.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-ux/cds-annotation-parserartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ux/cds-annotation-parserdescription.one_line → Parses annotations out of CDS source, so tooling can read what a model says about its UI without compiling it.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-ux/cds-odata-annotation-converterartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ux/cds-odata-annotation-converterdescription.one_line → Converts CDS annotations into their OData form, which is the translation Fiori tooling needs to reason about a service the way a client sees it.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-ux/eslint-plugin-fiori-toolsartifact_type → build-toolTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ux/eslint-plugin-fiori-toolsdescription.one_line → ESLint rules from the Fiori tools team, aimed at the parts of a project their generators produce.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-ux/fe-mockserver-plugin-cdsartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ux/fe-mockserver-plugin-cdsdescription.one_line → Lets the Fiori Elements mock server take a CDS file as its metadata source, so a UI is developed against the real model before a service exists.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-ux/fiori-annotation-apiartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ux/fiori-annotation-apidescription.one_line → The programmatic API Fiori tooling uses to read and write annotations on a project, rather than editing the files as text.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-ux/fiori-docs-embeddingsartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ux/fiori-docs-embeddingsdescription.one_line → Fiori documentation indexed as embeddings, which is what makes it searchable by something other than a person scrolling it.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-ux/fiori-generator-sharedartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ux/fiori-generator-shareddescription.one_line → The shared functions and types the Fiori generators are built from; a dependency of theirs rather than a generator itself.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-09-08@sap-ux/fiori-mcp-serverartifact_type → mcp-serverTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
2026-09-08@sap-ux/fiori-mcp-serverdescription.one_line → SAP's Fiori MCP server, run as `fiori-mcp`, letting a coding assistant create and edit Fiori applications directly rather than describing the steps.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
2026-08-30First entry seenDiscovered via npm registry, The discovery pass, GitHub API · SAP/open-ux-tools, GitHub API · SAP, npm registry · npm:scope:@sap, npm registry · npm:cds-plugin, npm registry · npm:sap cap plugin, Added by hand, npm registry · npm:cds-.

For your agent

Ref: actor:sap
JSON: /actors/sap.json
MCP: Connecting an agent