MODEL CONTEXT PROTOCOL

MCP integration

MCP provides a bridge between supported AI clients and DDL tools. The available actions depend on the identity, permissions, and configuration set by your organization.

AI-assisted analysisHuman reviewOn-premise available
MCP integration · workflow viewCapability flow
AI clientCompatible client
MCP bridgeAuthenticated connection
Permitted DDL toolsConfigured scope
Purpose-built diagram to explain the capability. No live DDL data, model, or connector is used.
HOW IT FITS

A connection with an explicit access boundary.

Choose the client and identity deliberately. The connected client can only use the tools made available to that identity in the configured environment.

  1. 01Choose a compatible client

    Use an AI client that supports the DDL MCP connection method configured by your organization.

  2. 02Set the identity and scope

    Manage access through your DDL integration settings; permitted tools depend on the assigned permissions.

  3. 03Use allowed DDL tools

    Explore project information and available actions within the configured access boundary.

This connection path depends on the MCP client, authentication, and DDL tools enabled for its identity. Authentication, reachable endpoints, and enabled tools must be configured and tested in the real environment. Never place tokens in a public page.

AI-CENTERED, HUMAN-REVIEWED
Keep the work connected to business context.

Delman has worked with enterprise data since 2018. DDL is available on-premise; model routes, permissions, and data paths depend on each organization’s configuration.

AI AT THE CENTER

See how an agent can work with selected data and team context.

Explore agentic AI