AI agent integration

The DALP CLI is the supported interface for AI coding agents. Agents can run dalp commands directly, call DALP through MCP tools, or read generated skill files before a run starts. In every mode, each command uses the authenticated CLI session, the active organisation, and the same DALP permission checks as a manual operator.

Integration modes

Use shell execution for transparent commands in logs. Use MCP when the assistant supports typed tool calls and shell parsing would add risk. Use skills for local command guidance before the agent writes or runs commands.

Set up a development workspace

1. Install and authenticate

npm install -g @settlemint/dalp-cli
dalp login --url https://your-platform.example.com

Check the authenticated account before starting the agent:

dalp whoami --format json

2. Set the organisation context

If your account can access more than one organisation, list the organisations and switch explicitly.

dalp auth org-list --format json
dalp auth org-switch <organizationId> --format json

dalp auth org-switch requires an organisation ID. Do not rely on an agent to guess the target organisation from natural language.

3. Prefer JSON output for shell agents

dalp config set format json

Agents should parse JSON fields rather than terminal tables. For one-off commands, you can also pass --format json directly.

4. Register MCP and skills when supported

# Register the CLI as an MCP server for supported local agents.
dalp mcp add

# Install generated DALP skill files for agent discovery.
dalp skills add

# Confirm the installed DALP skills.
dalp skills list

dalp mcp and dalp skills are local setup commands. They can run before authentication, but DALP platform operations still require a valid login and the required roles.

MCP server integration

The DALP CLI includes a built-in MCP registration command:

dalp mcp add

Use this as the default setup path. The CLI registers itself as an MCP server for supported local agents. After registration, DALP commands appear as assistant tools.

If you maintain MCP configuration manually, the server command is the DALP CLI in MCP mode:

{
  "mcpServers": {
    "dalp": {
      "command": "dalp",
      "args": ["--mcp"]
    }
  }
}

Keep authentication in the CLI session or approved environment configuration. Do not put API keys, private keys, or customer secrets in the MCP configuration file.

Skill integration

The CLI can sync generated skill files for agents that read local Markdown instructions.

dalp skills add
dalp skills list

Skills document commands, arguments, options, output format, and examples from CLI metadata. They are guidance for the assistant, not a security boundary.

You can also inspect machine-readable command metadata directly:

# LLM-readable command manifest
dalp --llms

# JSON Schema for command metadata
dalp --schema

Safe agent patterns

Inspect before mutate

Ask the agent to query current state first, then propose the exact mutation command for review.

# 1. Inspect the token.
dalp tokens read <tokenAddress> --format json

# 2. Inspect account roles before asking the agent to prepare privileged actions.
dalp system access-manager roles-list --format json

Make retries idempotent

Use list-before-create or read-before-update patterns. Agents should not retry a mutation blindly after a timeout.

existing=$(dalp tokens list --format json | jq '.data[]? | select(.symbol == "MTK")')
if [ -z "$existing" ]; then
  dalp tokens create --type equity --name "My Token" --symbol MTK --decimals 18 --countryCode 840 --format json
fi

Preserve organisation scope

Pin the organisation at the start of the run and include it in the agent's working notes.

dalp auth org-list --format json
dalp auth org-switch <organizationId> --format json
dalp whoami --format json

Handle structured errors

Agents should check exit codes and read the structured error body before retrying or escalating.

result=$(dalp tokens read <tokenAddress> --format json 2>&1) || {
  echo "$result" | jq -r '.message // .error // .'
  exit 1
}

Security considerations

• Agents inherit the authenticated CLI account. Limit that account with DALP roles instead of relying on prompt instructions.
• Operations are scoped to the active organisation. Switch explicitly with dalp auth org-switch <organizationId>.
• dalp mcp add and dalp skills add configure the local agent environment; they do not grant platform access by themselves.
• Keep credentials in the CLI-supported login flow or approved environment configuration. Do not paste secrets into agent prompts, skill files, or MCP JSON.
• Require a human review step for privileged operations such as minting, pausing, role changes, compliance changes, and identity approval.
• Store operational evidence from DALP command output and platform records, not from the assistant's narrative summary alone.

Command checks

Use these commands to verify the agent workspace before a DALP run:

dalp --version
dalp whoami --format json
dalp auth org-list --format json
dalp system access-manager roles-list --format json
dalp mcp --help
dalp skills --help

Next steps

• Use the command reference to confirm command names and options.
• Read CLI scripting for shell automation patterns.
• Review the AI assistants overview for operator-facing controls and usage examples.