OrganisationIndependent
neoimpulse GmbH
GitHub@neoimpulseGmbHlast push
Provides
Database connectorsCAPDatabase connectorsConnecting 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 developmentRunning 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.NotificationsCAPNotificationsTelling 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 MCPExposing 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 normalisationMaking 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 payloadsAccepting 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.
Entries
Group by
EntrySignals
Maintains
@neoimpulse/cap-js-bootstrap@neoimpulse/cap-js-bootstrapA command-line tool that starts a local CAP environment with several services and an AppRouter together from one command, documented in German and requiring Node 22 or newer.independent, cap
CLI starting several CAP services and an AppRouter locally together
@neoimpulse/cap-js-mcp@neoimpulse/cap-js-mcpAn MCP server inside a CAP application, with default tools that read the running model and query entities, plus configurable application tools, prompts and resources.independent, cap
MCP server inside a CAP application with model and query tools
@neoimpulse/cap-js-notifications@neoimpulse/cap-js-notificationsA copy of the official @cap-js/notifications plugin republished under another scope, whose README points at the original and says nothing about what was changed.independent, cap
Reach for the original unless you know why you are not. This is a republished copy rather than a fork with a direction of its own: the README points at cap-js/notifications for the details, and nothing here says what was changed or why.
Copy of @cap-js/notifications published under another scope
@neoimpulse/cap-js-restore-model-defined-types@neoimpulse/cap-js-restore-model-defined-typesA CAP plugin that casts values back to the types the CDS model declares after a READ, for the entities you name, where the database driver returned them as strings.independent, cap
CAP plugin casting read values back to CDS model types
@neoimpulse/cap-js-trim@neoimpulse/cap-js-trimA CAP plugin that strips whitespace from string elements on write, driven by a @cds.trim annotation on an entity or on single elements.independent, cap
CAP plugin stripping whitespace from strings on write via @cds.trim
@neoimpulse/cap-js-uppercase@neoimpulse/cap-js-uppercaseA CAP plugin that uppercases string elements on write, driven by a @cds.uppercase annotation on an entity or on single elements, the twin of the trim plugin.independent, cap
CAP plugin uppercasing strings on write via @cds.uppercase
@neoimpulse/cap-js-xml-protocol@neoimpulse/cap-js-xml-protocolA CAP plugin that lets the REST adapter take XML, parsing the payload to JSON and rewriting the content type before CAP sees the request.independent, cap
CAP plugin letting the REST adapter accept XML payloads
Details
History
- @neoimpulse/cap-js-bootstrapcapability: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-mcpThe published npm README documents default model/query tools as well as configurable modules; the previous module-only wording contradicted those facts.
- @neoimpulse/cap-js-mcpThe comparison distinguishes execution and surface selection at the stated runtime, retaining conditional operations and target restrictions.
- @neoimpulse/cap-js-mcpConverts 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-mcpConverts 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-mcpConverts 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-mcpConverts 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-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-bootstrapThe repository declared in package.json returns 404.
- @neoimpulse/cap-js-mcpThe repository declared in package.json returns 404. npm is the only address that resolves, and source_available says so.
- @neoimpulse/cap-js-mcpThe 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-uppercaseThe repository declared in package.json returns 404.
- First entry seenDiscovered via npm registry · cds-plugin, npm registry · @cap-js.
For your agent
- Ref
actor:neoimpulse- JSON
- /actors/neoimpulse.json
- MCP
- Connecting an agent