@opsee/mcp-server 0.7.1 → 0.7.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@opsee/mcp-server",
-  "version": "0.7.1",
+  "version": "0.7.2",
   "description": "Opsee MCP server — manage projects, tasks, docs, and cycles from AI coding environments",
   "type": "module",
   "bin": {

package/src/auth/kv-store.ts

@@ -87,16 +87,24 @@ export function createKVStore(): KVStore {
     port: parseInt(process.env.REDIS_PORT || "6379", 10),
     password: process.env.REDIS_PASSWORD || undefined,
     db: parseInt(process.env.REDIS_DB || "0", 10),
-    tls: process.env.REDIS_TLS === "true" ? {} : undefined,
-    // Don't queue commands forever if Redis is unreachable; surface errors.
+    // ElastiCache with in-transit encryption requires TLS. ServerName must be
+    // set so SNI/cert validation matches the endpoint host.
+    tls: process.env.REDIS_TLS === "true" ? { servername: host } : undefined,
+    // Fail fast instead of hanging the request forever. Without these a
+    // misconfigured connection (e.g. plaintext to a TLS-only server) leaves
+    // commands queued indefinitely, so awaiting a GET/SET never resolves.
     maxRetriesPerRequest: 3,
+    connectTimeout: 10_000,
+    commandTimeout: 5_000,
   });
 
   redis.on("error", (err: Error) => {
     console.error("[oauth] Redis error:", err.message);
   });
-  redis.on("connect", () => {
-    console.log(`[oauth] Connected to Redis at ${host}`);
+  // "ready" (not "connect") means commands will actually execute — a plaintext
+  // socket to a TLS-only server fires "connect" but never becomes ready.
+  redis.on("ready", () => {
+    console.log(`[oauth] Redis ready at ${host}`);
   });
 
   return new RedisKVStore(redis);