onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
Person

shahidla

1maintains
GitHub@shahidlalast push

Capabilities2

Provides 2
LLM integrationCAPLLM integrationcapabilityCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.Serve your application over MCPCAPServe your application over MCPcapabilityExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through [service integration](capability:service-integration), connecting its exposed contract with [agent access to your systems](capability:agent-systems-access). Development assistance belongs to [agent access to your code](capability:agent-code-access).

Entries1

Group by
EntrySignals
Maintains1
@shahid.la/cds-db-nlquery-mcpv0.7.3
none

MCP server answering plain-English questions against a CDS schema

Details

History9
  • @shahid.la/cds-db-nlquery-mcpprovides[mcp-servers].facets → CDS database-layer schema (db/ by default); service-layer/OData exposure is outside this interface; SELECT only; no INSERT, UPDATE or DELETE; Configured LLM plans a query descriptor; CDS executes a database query and SQL joins, rather than invoking application-service operations; Direct database access bypasses CAP @requires/@restrict; MCP_ALLOWED_ENTITIES restricts direct/joined entities, MCP_BLOCKED_COLUMNS excludes result columns; unset allowlist permits all entitiesDirect persistence access does not enforce service-layer annotations; the database/configuration controls and their defaults are stated explicitly.
  • @shahid.la/cds-db-nlquery-mcpprovides[mcp-servers].what_it_does → Queries CDS database-layer entities from a CAP [Node.js](external:nodejs) project through an LLM-planned SELECT query, including database-executed association joins. It targets the database layer rather than OData/application services, and executes no INSERT, UPDATE or DELETE. The entity allowlist covers direct queries and joined entities; its default allows all entities. CAP service-level @requires/@restrict are not enforced; database permissions and configuration control access.Direct persistence access does not enforce service-layer annotations; the database/configuration controls and their defaults are stated explicitly.
  • @shahid.la/cds-db-nlquery-mcpprovides.mcp-servers.facets.mcp_exposure_source.value → CDS database schemaConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
  • @shahid.la/cds-db-nlquery-mcpprovides.mcp-servers.facets.mcp_execution_path.value → Direct database queriesConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
  • @shahid.la/cds-db-nlquery-mcpprovides.mcp-servers.facets.mcp_exposure_control.value → Entity allowlist; Output filtering; CAP service authorization bypassedConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
  • @shahid.la/cds-db-nlquery-mcprequires → @sap/cds >= 7 runtime prerequisiteThe README states this CAP project prerequisite; the explicit relationship records it without claiming end-to-end compatibility.
  • @shahid.la/cds-db-nlquery-mcpprovides.mcp-servers.facets.mcp_execution_path.source → this package queries the database directly via `cds.run()`Uses the exact direct-database execution sentence as the primary citation, retaining the prior LLM-planning quote among supporting sources.
  • @shahid.la/cds-db-nlquery-mcpprovides[mcp-servers].what_it_does → Queries CDS database-layer entities from a CAP [Node.js](external:nodejs) project through an LLM-planned SELECT query, including database-executed association joins. It targets the database layer with a default model path of db/ and executes no INSERT, UPDATE or DELETE. MCP_ALLOWED_ENTITIES restricts direct queries and joined entities; its default allows all entities. MCP_BLOCKED_COLUMNS excludes result columns before execution. CAP service-level @requires/@restrict are not enforced; database permissions and configuration control access.Resolves the requested review findings while preserving the structured comparison values, runtime scopes and implementation restrictions.
  • First entry seenDiscovered via npm registry · keywords:sap-cap.
For your agent
Ref
actor:shahidla
JSON
/actors/shahidla.json
MCP
Connecting an agent