OrganisationIndependent

neoimpulse GmbH

GitHub@neoimpulseGmbHlast push

Capabilities6

Provides 6
Database connectorsCAPDatabase connectorscapabilityConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).Local developmentCAPLocal developmentcapabilityRunning the whole stack on a laptop against real bindings — the service, the UI and the routing in front of it — without deploying to see a change.NotificationsCAPNotificationscapabilityTelling a person something happened when they are not looking at the screen — a notification in the launchpad, an email, a message somewhere they already are.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).Value normalisationCAPValue normalisationcapabilityMaking stored values consistent regardless of how they were typed — trimming the padding, fixing the case — declared on the model rather than repeated in every handler that writes.XML payloadsCAPXML payloadscapabilityAccepting and returning XML on a service, or sending it to one, for a counterpart that cannot speak JSON — usually a B2B partner or a system older than the extension in front of it.

Entries7

Group by
EntrySignals
Maintains7
@neoimpulse/cap-js-bootstrapv1.1.2
none

CLI starting several CAP services and an AppRouter locally together

@neoimpulse/cap-js-mcpv1.0.7
none

MCP server inside a CAP application with model and query tools

@neoimpulse/cap-js-notificationsv1.0.12
Functional boundary

Copy of @cap-js/notifications published under another scope

@neoimpulse/cap-js-restore-model-defined-typesv1.0.2
none

CAP plugin casting read values back to CDS model types

@neoimpulse/cap-js-trimv1.2.4
none

CAP plugin stripping whitespace from strings on write via @cds.trim

@neoimpulse/cap-js-uppercasev1.0.4
none

CAP plugin uppercasing strings on write via @cds.uppercase

@neoimpulse/cap-js-xml-protocolv1.0.5
none

CAP plugin letting the REST adapter accept XML payloads

Details

History13
  • @neoimpulse/cap-js-bootstrapprovides[capability:local-development] → The edge with what it does, its sources and the comparison value for the parts of the local stack it starts.capability:local-development curation on 2026-10-15. The edge was a bare reference: the one capability this package answers carried no sentence and no source, which rule 10 does not allow. The package's own npm text names what it starts, cds watch per service and the router through cds bind --exec, and is quoted in its own language. Read through registry.npmjs.org because npmjs.com refuses the fetcher.
  • @neoimpulse/cap-js-mcpdescription.one_line and description.what_it_solves → An MCP server inside a CAP application, with default tools that read the running model and query entities, plus configurable application tools, prompts and resources.The published npm README documents default model/query tools as well as configurable modules; the previous module-only wording contradicted those facts.
  • @neoimpulse/cap-js-mcpprovides[mcp-servers].facets and what_it_does → [{"key":"mcp_exposure_source","value":"Compiled CDS model plus configured tool/resource/prompt modules"},{"key":"mcp_operations","value":"Default model/query tools; application business/write operations need custom tools; product CRUD is an in-memory demo"},{"key":"mcp_context","value":"Extensible file/data resources and prompt templates; modules can inherit and override defaults"},{"key":"mcp_execution_path","value":"Default query tool uses a service instance when available, with cds.run() fallback; custom business tools own their dispatch"},{"key":"mcp_exposure_control","value":"Configured component modules and inheritance/overrides determine registered tools"}]The comparison distinguishes execution and surface selection at the stated runtime, retaining conditional operations and target restrictions.
  • @neoimpulse/cap-js-mcpprovides.mcp-servers.facets.mcp_exposure_source.value → Compiled CDS modelConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
  • @neoimpulse/cap-js-mcpprovides.mcp-servers.facets.mcp_context.value → MCP resources; MCP prompts; Model descriptions via toolsConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
  • @neoimpulse/cap-js-mcpprovides.mcp-servers.facets.mcp_execution_path.value → CAP service calls; CDS query fallback; Custom tool handlersConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
  • @neoimpulse/cap-js-mcpprovides.mcp-servers.facets.mcp_exposure_control.value → Tool module configurationConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
  • @neoimpulse/cap-js-notificationslineage → fork of artifact:cap-js-notificationsThe README says it is a copy of cap-js/notifications. GitHub does not flag it as a fork — the code was copied rather than forked on the platform — so this one has lineage and no fork_of, which is the case the two fields are kept apart for.
  • @neoimpulse/cap-js-bootstraplinks.repo → npm onlyThe repository declared in package.json returns 404.
  • @neoimpulse/cap-js-mcplinks.repo → npm onlyThe repository declared in package.json returns 404. npm is the only address that resolves, and source_available says so.
  • @neoimpulse/cap-js-mcpdescription.one_line → An MCP server inside a CAP application, where the tools, prompts and resources are modules you point it at rather than the model it derives.The npm description is wrong — it is the sibling trim plugin's line, pasted. Anyone reading the registry entry, agents included, is told this package trims strings. It does not.
  • @neoimpulse/cap-js-uppercaselinks.repo → npm onlyThe repository declared in package.json returns 404.
  • First entry seenDiscovered via npm registry · cds-plugin, npm registry · @cap-js.
For your agent