Open Edition Cockpit and MCP server integration
Naia Build uses the Neptune DXP - Open Edition MCP server to create the artifacts an application needs, for example, tables, APIs, and server scripts. This is what turns a conversation into a running application. Instead of creating these artifacts yourself, Naia Build produces what the application needs to work, and you can open and edit the result without leaving Naia Build.
For more information about the Neptune DXP - Open Edition MCP server, see Neptune DXP - Open Edition MCP server.
What MCP integration provides
Through the MCP server connection, Naia Build can create and change back-end artifacts alongside the front end it generates, for example:
-
Tables
-
APIs
-
Server scripts
You can also work with these artifacts manually using the embedded Neptune DXP - Open Edition Cockpit in the Tools tab, as you would in the standalone Cockpit. Both approaches are supported and reliable. Use the manual route when you want direct control, and the Naia Build route when you want generation to extend into the back end.
MCP server connection
Naia Build acts on artifacts through a Model Context Protocol (MCP) server connection. The connection is gated by your approval:
-
When you approve the MCP server connection, Naia Build can create, read, and change artifacts, for example, tables, APIs, and server scripts.
-
When you do not approve the connection, Naia Build cannot work on these artifacts. It can build the application only.
Because artifact access depends on this approval, Naia Build has no visibility into these artifacts until you grant it. See Security and data for how this fits the wider data-handling model.
Where an artifact opens depends on its type:
-
Tables (via the Cockpit Table Definition/Table Browser tools) and APIs (via the Cockpit API Designer) open in the Tools tab.
-
Server scripts from the Cockpit’s Script Editor open in the Backend scripts tab.