Development packages
Development packages organize artifacts — applications, web apps, server scripts, adaptive entities, tables, and APIs — into groups. Development packages also drive access control for non-administrative users: a user can only see and modify artifacts in development packages that their roles grant access to.
When you create an artifact through the MCP plugin without naming a development package, the artifact is assigned to your default development package. A package that you name explicitly takes precedence. If you have no edit access to your default package, it is skipped, and the artifact is created without it.
Required role: package.
If your user account does not have this role, every tool in this group fails immediately with an access denied error. Contact an administrator to request the role, or see Access control for more information on how roles are enforced.
Available tools
Parameters are shown with their type and a short description. UUIDs are always strings.
| Tool | Description | Parameters |
|---|---|---|
|
List all development packages in Neptune DXP - Open Edition. Development packages organize artifacts (apps, scripts, tables, APIs) together. |
None |
|
Return detailed information about a development package by its ID. |
|
|
Create or update a development package. For a new development package, the object
must contain |
|
|
Delete a development package by its ID. |
|
Related topics
-
Tools overview — the full list of artifact types and required roles.
-
Access control — how development package permissions interact with role checks.