From 3d1560d69c2af976939bd7dfed6adbcfd91c5e46 Mon Sep 17 00:00:00 2001
From: "lei.chen" <lei.chen@nexa.com>
Date: Wed, 12 Aug 2026 08:41:19 +0000
Subject: [PATCH] chore(mcp): use XCE_API_KEY env var in xce-scheduler MCP
 config
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Reference the operator key via ${XCE_API_KEY} instead of a hardcoded value —
apiserver restarts clear in-memory keys, so a committed key goes stale
silently and is a credential risk. Export XCE_API_KEY before starting Claude
Code to use the scheduler-agent MCP server.

Co-Authored-By: Claude <noreply@anthropic.com>
---
 .mcp.json | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/.mcp.json b/.mcp.json
index da39e4ff..42a9445b 100644
--- a/.mcp.json
+++ b/.mcp.json
@@ -1,3 +1,13 @@
 {
-  "mcpServers": {}
+  "mcpServers": {
+    "xce-scheduler": {
+      "type": "stdio",
+      "command": "/tmp/xce-mcp",
+      "args": [],
+      "env": {
+        "XCE_API_URL": "http://172.31.1.30:8080",
+        "XCE_API_KEY": "${XCE_API_KEY}"
+      }
+    }
+  }
 }