MCP configuration file and environment variables
For other agents not specified in the documentation, you can configure the MCP server by using environment variables or an .env configuration file.
Configuration file example
With API key
{
"servers": {
"wxdi-mcp-server": {
"url": "<url_to_mcp_server>",
"type": "http",
"headers": {
"x-api-key": "your api key from cloud SaaS/cpd"
}
}
}
}
With bearer token
{
"servers": {
"wxdi-mcp-server": {
"url": "<url_to_mcp_server>",
"type": "http",
"headers": {
"authorization": "Bearer token"
}
}
}
}
HTTP and stdio environment variables
| Environment variable | Description |
|---|---|
| DI_SERVICE_URL | Base URL. |
| DI_ENV_MODE | Environment mode. |
| REQUEST_TIMEOUT_S | HTTP request timeout in seconds. The default is 60. |
| LOG_FILE_PATH | Logs are written here if provided. Mandatory for the stdio mode. |
| DI_CONTEXT | Context for URLs returned from tool responses. |
stdio environment variables
| Environment variable | Description |
|---|---|
| DI_APIKEY | API key for authentication. |
| DI_USERNAME | Username - required when using API key. |
| DI_AUTH_TOKEN | Bearer token as an alternative to an API key. |
HTTP/HTTPS environment variables
| Environment variable | Description |
|---|---|
| x-api-key | API keyfor authentication. |
| username | Username - required when using API key. |