Neptune DXP - Open Edition MCP server

MCP server support is available from Neptune DXP - Open Edition 24.15 onward. Earlier releases, including Neptune DXP - Open Edition 24.14 LTS, 24.12 MTS, and 23 LTS, do not include the MCP server. Upgrade to Neptune DXP - Open Edition 24.15 MTS or later before you connect a client.

Neptune DXP - Open Edition includes a built-in MCP (Model Context Protocol) server. The MCP server lets AI-powered editors and assistants, for example, Claude Code, Claude Desktop, Cursor, and Windsurf, manage your design-time artifacts directly through natural-language instructions.

This documentation explains how to connect a supported MCP client, how authorization works for end users, which artifacts you can manage through MCP, and how to resolve common connection issues. Instructions are intended for developers, designers, and administrators who use Neptune DXP - Open Edition.

MCP server general information

The MCP server is part of Neptune DXP - Open Edition. It exposes the same design-time tools that the Cockpit uses, over the open Model Context Protocol. Any MCP-compatible client can connect to the server and, after authorization, operate on applications, web apps, server scripts, adaptive entities, tables, APIs, and development packages.

The MCP server is enabled by default on every supported Neptune DXP - Open Edition instance. No additional installation is required.

Supported artifacts and operations

The MCP server provides tools to:

  • List, view, create, update, and delete applications.

  • Manage standalone React and Vue web apps.

  • Create and edit server scripts written in JavaScript or TypeScript, and organize them into projects.

  • Manage adaptive entities and their field definitions.

  • Define and modify database tables (including the underlying database schema).

  • Inspect APIs that are registered on the platform.

  • Organize artifacts into development packages and manage development package-level access control.

Every action runs as the signed-in user. The MCP server enforces the same access control rules, validation checks, edit locks, and save hooks as the Cockpit. An MCP client cannot bypass platform-level checks.

Connection URL

Clients connect to the MCP server at the following URL:

http(s)://<host>:<port>/mcp

Use the public URL of your Neptune DXP - Open Edition instance. In production, the server must be reached over HTTPS.

The MCP server uses the Streamable HTTP transport. Clients that support only the legacy stdio MCP transport cannot connect directly. Such clients require a bridge process (see Other MCP clients).

Related topics