Deployment & Configuration

Supported Deployment Models

Agentic AI Workflow with MCP supports the following deployment types:

  • Standalone containerized deployment (supported)

    MCP runs as a standalone service in your environment (e.g., Kubernetes) and connects to SD Elements via API.

  • SD Elements SaaS-integrated deployment

    Native MCP integration within SD Elements SaaS

Core MCP Client Configuration (JSON)

MCP client configuration is typically defined in:

  • A JSON configuration file (common for IDE extensions)

  • A configuration manager

  • Environment variables

At minimum, the client must know:

  • Where the MCP server is running

  • Which headers to include for authentication and routing

This example shows the general structure used by IDE extensions such as Cursor or VS Code plugins. Adapt it as needed for your client.

{
  "servers": {
    "sde-mcp-server": {
      "url": "https://your-sde-instance.sdelements.com/mcp",
      "headers": {
        "sde-api-key": "my-api-key"
      }
    }
  }
}

Client Configuration for Standalone

Prerequisite

Before configuring your client, ensure the following are in place:

  • MCP server deployed and running

    • Deployed via Helm (containerized) or running locally

  • Service accessibility

    • MCP service must be reachable from the client machine via TLS/SSL (Port 443)

  • MCP service URL

    • External ingress hostname (recommended for IDEs)

    • Internal Kubernetes service URL (if running inside the cluster)

  • SD Elements API key

    • A valid personal API key for authentication

Deployment-Specific Configuration

A. Single Instance Mode

Use this configuration if MCP is deployed for a single SD Elements instance (mcp.sdeInstance enabled in the Helm chart).

Required configuration:

  • MCP service URL

  • SD Elements API key

{
  "mcpServers": {
    "sdelements": {
      "url": "https://sde-mcp.example.com/mcp",
      "headers": {
        "sde-api-key": "your-api-key-here"
      }
    }
  }
}

B. Allowlist Mode

Use this configuration if MCP supports multiple SD Elements instances (mcp.sdeInstanceAllowlist enabled).

Required configuration:

  • MCP service URL

  • SD Elements instance URL

  • SD Elements API key

{
  "mcpServers": {
    "sdelements": {
      "url": "https://sde-mcp.example.com/mcp",
      "headers": {
        "sde-host": "https://your-sdelements-instance.com",
        "sde-api-key": "your-api-key-here"
      }
    }
  }
}

Configuration Reference

MCP Service URL (url)

Access Type Example When to Use

External

https://sde-mcp.example.com/mcp

Most IDE and desktop clients

Internal

http://sde-mcp-service.namespace.svc.cluster.local:3000/mcp

Agents running inside the same cluster

HTTP Headers (headers)

Header Name Required Description

SDE-API-KEY

Always

Your personal SD Elements API key

SDE-HOST

Allowlist mode only

Full URL of the target SD Elements instance

Header Naming Requirements

Header names must use hyphens, not underscores. We also recommend using lowercase header names to ensure consistent handling across clients and proxies.

✓ Correct:

  • sde-api-key

  • sde-host

✗ Incorrect:

  • SDE_API_KEY

  • SDE_HOST

Headers containing underscores may be silently dropped by HTTP proxies (such as NGINX or Istio), causing authentication failures.

results matching ""

    No results matching ""