Rapid Development Toolkit (RDT) — Installation

RDT consists of two components: the RDT VS Code Extension and the RDT MCP Server. Both are available from their respective GitLab repositories.

---

RDT VS Code Extension

Download

1. Go to the project's Releases page in GitLab.
2. Find the latest release.
3. Under Assets, click SAMO RDT VS Code Extension to download the .vsix file.

Installation

Option A: From the VS Code UI

1. Open Visual Studio Code.
2. Go to the Extensions View (Ctrl+Shift+X).
3. Click the ... (More Actions) button in the Extensions view.
4. Select Install from VSIX....
5. Choose the downloaded .vsix file.
6. Restart VS Code if required.

Option B: From the Command Line

code --install-extension samo-rdt-<version>.vsix

Updating

To update to a newer version, download the latest .vsix from the Releases page and repeat the installation steps above. VS Code will replace the existing version automatically.

Prerequisites

• VS Code 1.103.0+
• Node.js 22.x

Configuration

The extension exposes the following settings under samo-rdt.* in VS Code (Settings → Ctrl+, → search for samo-rdt).

General

Setting	Type	Default	Description
samo-rdt.gitlabToken	string	""	GitLab access token for cloning project templates. This token is not public — contact the RDT team to obtain it.

Kubernetes Deploy — Infrastructure (samo-rdt.kubeDeploy.*)

Setting	Type	Default	Description
kubeDeploy.namespace	string	rdt-test	Kubernetes namespace for deployment and pod operations
kubeDeploy.helmChartVersion	string	0.33.0	Version of the SAMO Helm chart to deploy
kubeDeploy.ociRegistry	string	oci://docker.asseco-ce.com/...	OCI registry URL for the SAMO Helm chart
kubeDeploy.helmTimeout	string	5m	Timeout for Helm operations and pod monitoring (supports m, s, h units)

Kubernetes Deploy — Binary Paths

Setting	Type	Default	Description
kubeDeploy.kubectlPath	string	""	Custom path to kubectl binary (empty = use system PATH)
kubeDeploy.helmPath	string	""	Custom path to helm binary (empty = use system PATH)

Kubernetes Deploy — Required Files

Setting	Type	Default	Description
kubeDeploy.licenseXmlPath	string	""	Path to license XML file (relative to workspace root)
kubeDeploy.licenseFilePath	string	""	Path to license file (relative to workspace root)
kubeDeploy.secretsYamlPath	string	""	Path to secrets YAML file (relative to workspace root)

Kubernetes Deploy — Database

Setting	Type	Default	Description
kubeDeploy.driverName	oracle | postgresql	postgresql	Database driver used for Helm deployment

Kubernetes Deploy — Environment ConfigMap File Names

These settings specify file names (no path separators) from the {subproject}/project/environments/{subproject}-dev/ directory. Each file is mapped to a corresponding Kubernetes ConfigMap.

Setting	ConfigMap Name	ConfigMap Key	Description
kubeDeploy.lidsasProperties	lidsas-properties	environment.properties	LIDS-AS environment properties
kubeDeploy.samogatewayProperties	samogateway-properties	environment.properties	SAMO Gateway environment properties
kubeDeploy.securityserverProperties	securityserver-properties	environment.properties	Security Server environment properties
kubeDeploy.userserviceProperties	userservice-properties	environment.properties	User Service environment properties
kubeDeploy.licenseserverProperties	licenseserver-properties	environment.properties	License Server environment properties
kubeDeploy.datasourceProperties	datasource-properties	datasource.properties	Datasource connection properties
kubeDeploy.lidsasMasterProperties	lidsas-master-properties	environment_master.properties	LIDS-AS Master environment properties

---

SAMO Pilot (Claude Code Plugin)

SAMO Pilot is a Claude Code plugin that bundles the MCP server and gives AI deep knowledge of the SAMO platform. For full feature documentation, see the SAMO Pilot overview.

Prerequisites

• Claude Code CLI
• Node.js 18+ (for MCP server execution via npx)
• @samo npm scope configured (see below)
• Network access to SAMO GitLab
• GitLab access token (contact the RDT team or email simon.misak@asseco-ce.com)

Installation

1. Open your SAMO project directory and start Claude Code:

   cd your-samo-project/
   claude

2. Add the plugin marketplace:

   /plugin marketplace add git@gitlab:samo/server/tools-implementation/samo-pilot.git

   If you don't have access to the SAMO GitLab, contact the RDT team or email simon.misak@asseco-ce.com to request access.

Configuring the Token

The GitLab token is stored securely by Claude Code. To update it later:

/plugin config samo-pilot

Updating

To update SAMO Pilot to the latest version:

1. Type /plugin in Claude Code and press Enter
2. Select Installed from the menu
3. Select samo-pilot from the list
4. Select Update now
5. After the update completes, select Reload plugins to apply the changes

---

RDT MCP Server

The MCP server (@samo/mcp-server) is published to the SAMO Nexus npm registry and can be run via npx — no manual build required.

Source code: samo-mcp-server GitLab repository

Prerequisites

• Node.js 18+
• npm with the @samo scope configured (see below)
• GitLab access token for project scaffolding features (contact the RDT team or email simon.misak@asseco-ce.com)

Configuring the @samo npm scope

The @samo/mcp-server package is hosted on the SAMO Nexus npm registry. You need to configure npm to resolve the @samo scope from this registry and authenticate.

1. Log in to the SAMO Nexus registry:

npm login --registry=https://nexus/repository/samo-npm/

Enter your Nexus credentials when prompted (username, password, email).

2. Configure the @samo scope:

npm config set @samo:registry https://nexus/repository/samo-npm/

This adds the following to your ~/.npmrc:

@samo:registry=https://nexus/repository/samo-npm/
//nexus/repository/samo-npm/:_authToken=<your-token>

After this one-time setup, npx @samo/mcp-server and npm install @samo/mcp-server will resolve from the correct registry.

Installation via SAMO Pilot (recommended)

If you use Claude Code, the MCP server is included in the SAMO Pilot plugin and starts automatically — no separate setup needed:

/plugin marketplace add git@gitlab:samo/server/tools-implementation/samo-pilot.git

Standalone Installation

For use with other AI clients (VS Code Copilot, Claude Desktop), run via npx:

npx @samo/mcp-server

Or install globally:

npm install -g @samo/mcp-server

Updating

When using npx, it always fetches the latest version automatically. If installed globally, update with:

npm install -g @samo/mcp-server@latest

Connecting to AI Tools

The MCP server uses stdio transport — the AI client launches it as a local process. Below are configuration examples for supported tools.

VS Code — GitHub Copilot (Agent Mode)

Create or edit .vscode/mcp.json in your project root:

{
  "servers": {
    "samo-rdt": {
      "type": "stdio",
      "command": "npx",
      "args": ["@samo/mcp-server"],
      "env": {
        "SAMO_GITLAB_TOKEN": "your-gitlab-access-token"
      }
    }
  }
}

Claude Desktop

Add the server to claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "samo-rdt": {
      "command": "npx",
      "args": ["@samo/mcp-server"],
      "env": {
        "SAMO_GITLAB_TOKEN": "your-gitlab-access-token"
      }
    }
  }
}

Claude Code (CLI)

claude mcp add samo-rdt -- npx @samo/mcp-server

Environment Variables

Variable	Description
SAMO_GITLAB_TOKEN	GitLab access token for project scaffolding. Contact the RDT team or email simon.misak@asseco-ce.com to obtain it.
DOCS_URL	URL to gzipped docs JSON. Defaults to public SAMO docs endpoint.
BUSINESS_SERVER_VERSION	Override the business-server schema version fetched from Lighthouse.
DYNAPP_VERSION	Override the Dynamic App version for module-catalog and dynapp-configuration schemas.