forked from elastic/example-mcp-app-security
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
21 lines (17 loc) · 1.2 KB
/
Copy path.env.example
File metadata and controls
21 lines (17 loc) · 1.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
# Cluster configuration for the MCP server.
#
# Set CLUSTERS_JSON to a single-cluster JSON array, or point CLUSTERS_FILE
# at a JSON file with the same shape to keep secrets out of this file.
# CLUSTERS_FILE wins if both are set.
CLUSTERS_JSON=[{"name":"primary","elasticsearchUrl":"https://your-cluster.es.cloud.example.com","kibanaUrl":"https://your-cluster.kb.cloud.example.com","elasticsearchApiKey":"your-elasticsearch-api-key","sslVerify":true}]
# TLS verification options (per cluster, inside CLUSTERS_JSON / CLUSTERS_FILE):
# sslVerify — boolean, default true. Set false only for trusted self-signed dev clusters.
# caCertPath — absolute path to a PEM CA bundle file. Prefer this over sslVerify:false.
# Cannot be combined with sslVerify:false (rejected at startup).
# Alternative: load the same JSON from a file.
# CLUSTERS_FILE=/absolute/path/to/clusters.json
# Telemetry endpoint override. Defaults to production (telemetry.elastic.co).
# Set to `staging` to point at telemetry-staging.elastic.co — useful when
# verifying dashboards or working on the MCP App's analytics locally.
# See docs/telemetry.md for the full event catalog and opt-out story.
# MCP_APP_TELEMETRY_ENV=staging