From e14ae9c9cff385d35a4f2fbe977ead62edd1bcc4 Mon Sep 17 00:00:00 2001
From: Eyal Toledano <eyal@microangel.so>
Date: Wed, 2 Apr 2025 22:29:38 -0400
Subject: [PATCH] chore: adjust the setupMCPConfiguration so it adds in the new
 env stuff.

---
 .cursor/mcp.json               |  4 ++--
 scripts/init.js                | 12 +++++++++++-
 scripts/modules/ai-services.js |  3 +++
 3 files changed, 16 insertions(+), 3 deletions(-)

diff --git a/.cursor/mcp.json b/.cursor/mcp.json
index 6dd8186d..3fc04e9c 100644
--- a/.cursor/mcp.json
+++ b/.cursor/mcp.json
@@ -10,8 +10,8 @@
                 "PERPLEXITY_API_KEY": "%PERPLEXITY_API_KEY%",
                 "MODEL": "%MODEL%",
                 "PERPLEXITY_MODEL": "%PERPLEXITY_MODEL%",
-                "MAX_TOKENS": "%MAX_TOKENS%",
-                "TEMPERATURE": "%TEMPERATURE%",
+                "MAX_TOKENS": 64000,
+                "TEMPERATURE": 0.4,
                 "DEFAULT_SUBTASKS": 5,
                 "DEFAULT_PRIORITY": "medium"
             }
diff --git a/scripts/init.js b/scripts/init.js
index 31432c89..d472c4b5 100755
--- a/scripts/init.js
+++ b/scripts/init.js
@@ -702,7 +702,17 @@ function setupMCPConfiguration(targetDir, projectName) {
       "args": [
         "-y",
         "task-master-mcp-server"
-      ]
+      ],
+      "env": {
+          "ANTHROPIC_API_KEY": "%ANTHROPIC_API_KEY%",
+          "PERPLEXITY_API_KEY": "%PERPLEXITY_API_KEY%",
+          "MODEL": "%MODEL%",
+          "PERPLEXITY_MODEL": "%PERPLEXITY_MODEL%",
+          "MAX_TOKENS": "%MAX_TOKENS%",
+          "TEMPERATURE": "%TEMPERATURE%",
+          "DEFAULT_SUBTASKS": 5,
+          "DEFAULT_PRIORITY": "medium"
+      }
     }
   };
   
diff --git a/scripts/modules/ai-services.js b/scripts/modules/ai-services.js
index 6e9c4c81..280f3f93 100644
--- a/scripts/modules/ai-services.js
+++ b/scripts/modules/ai-services.js
@@ -171,6 +171,9 @@ Guidelines:
 6. Set appropriate dependency IDs (a task can only depend on tasks with lower IDs)
 7. Assign priority (high/medium/low) based on criticality and dependency order
 8. Include detailed implementation guidance in the "details" field
+9. If the PRD contains specific requirements for libraries, database schemas, frameworks, tech stacks, or any other implementation details, STRICTLY ADHERE to these requirements in your task breakdown and do not discard them under any circumstance
+10. Focus on filling in any gaps left by the PRD or areas that aren't fully specified, while preserving all explicit requirements
+11. Always aim to provide the most direct path to implementation, avoiding over-engineering or roundabout approaches
 
 Expected output format:
 {