cap-mcp-apps
A CAP plugin that swaps in its own MCP protocol adapter so the results of the @cap-js/mcp@cap-js/mcpA CAP plugin that serves an @mcp-annotated service over MCP with three generated tools, describe, query and call_action, and writes its endpoint into the local agent's configuration in development.sap official, cap query tool open as a @ui5/webcomponents@ui5/webcomponentsSAP's UI elements as standard custom elements, ui5-button among them, implementing SAP Fiori design and usable from plain HTML, React, Angular or Vue.sap official, ui5 table in hosts that support MCP Apps.
In a host that supports MCP Apps, the results of the query tool of @cap-js/mcp@cap-js/mcpA CAP plugin that serves an @mcp-annotated service over MCP with three generated tools, describe, query and call_action, and writes its endpoint into the local agent's configuration in development.sap official, cap open as a table, served as the resource ui://cap-query-table/index.html. The plugin sets protocols.mcp.impl to its own adapter, which registers the describe, query and call tools from the lib modules of @cap-js/mcp and attaches the table to query; setting cds.mcp.apps.queryTable to false keeps the stock adapter. Unbound service actions annotated with @mcp.apps.Action appear as buttons on the toolbar or on each row, with a form inferred from the action's parameters, and a button calls the existing call tool and then re-runs the last query. Only actions the current MCP user may call under @requires or @restrict are shown. The table is one HTML file bundled from @ui5/webcomponents@ui5/webcomponentsSAP's UI elements as standard custom elements, ui5-button among them, implementing SAP Fiori design and usable from plain HTML, React, Angular or Vue.sap official, ui5 at build time, with everything inlined because hosts with a strict content security policy block CDN imports.
Facts
Where it sits
Who is behind it
In the atlas: maintains 1, contributes to 1@aelghanammaintainer
Before choosing this
Conditions
LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2, 3A cds-plugin is used with SAP CAP materials, or an artifact is explicitly identified as a CAP plugin or application.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
- § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
- § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
What it declares
Every artifact
- Type
- CDS plugin
- Origin
- Independently maintained
- Runtime
- Node.js
As a CDS plugin
- Declared for
- >=9
- Distributed through
- npm
Connections
Showing an interface inside an agent conversation
Exposes CAP services as MCP servers for AI agents
CAP Node.js runtime
Download
Install
npm add cap-mcp-appsDerived from the package name. No recipe recorded; the README has the configuration.
README
quoted from aelghanam/mcp-apps under Apache-2.0, readcap-mcp-apps
CDS plugin for CAP Node.js. It enriches @cap-js/mcp query tool results with an MCP App (UI5 Web Components table) when the host supports MCP Apps.
CAP loads it automatically. A consuming app only needs this package in dependencies. There is no server.js protocol override.
Install
npm add @cap-js/mcp cap-mcp-apps
From GitHub before it is published to npm:
{
"dependencies": {
"cap-mcp-apps": "github:aelghanam/mcp-apps"
}
}
Annotate services with @mcp as usual. On cds watch / cds serve, CAP detects cds-plugin.js, merges this package's cds configuration, and loads the plugin.
The plugin contributes the annotation vocabulary in vocab/ through:
"cds": {
"requires": {
"cap-mcp-apps-vocab": {
"model": "cap-mcp-apps/vocab"
}
}
}
Peer packages (@sap/cds, @cap-js/mcp, express) resolve from the consuming app. .npmrc sets omit=peer so a nested @sap/cds is not installed inside this package.
Configuration
Query-table enrichment is on by default. To keep the stock @cap-js/mcp adapter, set:
{
"cds": {
"mcp": {
"apps": {
"queryTable": false
}
}
}
}
When queryTable is false, this plugin does not override protocols.mcp.impl.
Action buttons (@mcp.apps.Action)
Unbound service actions can be shown in the MCP App UI. The annotation shape is declared in vocab/index.cds (mcp.apps.Action / mcp.apps.Placement).
annotate MyService.ping with @mcp.apps.Action: {
placement: #Toolbar,
label: 'Ping'
};
annotate MyService.submitOrder with @mcp.apps.Action: {
placement: #Row,
label: 'Submit Order',
entities: [Books, ListOfBooks]
};
| Field | CDL form | CSN | Meaning |
|---|---|---|---|
placement | #Toolbar / #Row | { "#": "…" } | Below the table, or on each row |
label | string | string | Button text (defaults to the action name) |
entities | [Books, …] type refs | [{ "=": "Books" }, …] | Optional. Omit to show for every queried entity. |
Use type references [Books], not element expressions (Books). Parentheses are CXL paths resolved in the action scope and fail to compile for entity names.
Input forms are inferred from CDS parameters: no parameters calls immediately, scalars become inputs, structured or many parameters use a JSON textarea.
The App invokes the existing MCP call tool via app.callServerTool. After a successful action it re-runs the last query (structuredContent.queryArgs). A Refresh button in the header does the same.
Only actions the current MCP user may call (@requires / @restrict) are included.
Logging
const LOG = cds.log('cap-mcp-apps')
{
"cds": {
"log": {
"[development]": {
"levels": {
"cap-mcp-apps": "debug"
}
}
}
}
}
Develop this plugin
src/ is the App UI. npm run build bundles it into assets/query-table.html, which the adapter serves at runtime. UI5 Web Components and esbuild are devDependencies of this package.
npm install
npm run build
Link it into a CAP app with "cap-mcp-apps": "file:../cap-mcp-apps", then run cds watch in that app.
License
PolyForm Small Business 1.0.0. Use is free for an individual, and for an organization with fewer than 100 people and under the license's revenue cap (1,000,000 USD in 2019 dollars, adjusted for inflation). Larger organizations are not covered and need a separate commercial license from the copyright holder.
The CDS annotation namespace stays mcp.apps (@mcp.apps.Action). That name is the annotation API, not the npm package name.
History
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
Flavors
“CDS plugin for CAP Node.js.” — cap-mcp-apps — README
History in the atlas
- First seen.
For your agent
- Ref
artifact:aelghanam-cap-mcp-apps- JSON
- /artifacts/aelghanam-cap-mcp-apps.json
- MCP
- Connecting an agent