Implement a local MCP server to calculate the final line numbers of the security findings.

Author: heltonduarte

GEMINI.md

@@ -162,7 +162,7 @@ For each identified vulnerability, provide the following:
 
 *   **Vulnerability:** A brief name for the issue (e.g., "Cross-Site Scripting," "Hardcoded API Key").
 *   **Severity:** Critical, High, Medium, or Low.
-*   **Location:** The file path where the vulnerability was introduced.
+*   **Location:** The file path where the vulnerability was introduced and the line numbers if that is available.
 *   **Line Content:** The complete line of code where the vulnerability was found.
 *   **Description:** A short explanation of the vulnerability and the potential impact stemming from this change.
 *   **Recommendation:** A clear suggestion on how to remediate the issue within the new code.

commands/security/analyze.toml

@@ -26,4 +26,8 @@ You will now begin executing the plan. The following are your precise instructio
 
 After completing these two initial tasks, continue executing the dynamically generated plan according to your **Core Operational Loop**.
 
+**Final Report Generation**
+
+When you have finished your analysis and are ready to generate the final report, you must use the `gemini-cli-security` MCP server to get the line numbers for each finding. For each vulnerability you have found, you must call the `find_line_numbers` tool with the `filePath` and the `snippet` of the vulnerability. You will then add the `startLine` and `endLine` to the final report.
+
 Proceed with the Initial Planning Phase now."""

gemini-extension.json

@@ -1,5 +1,12 @@
 {
   "name": "gemini-cli-security",
-  "version": "0.1.0",
-  "contextFileName": "GEMINI.md"
+  "version": "0.2.0",
+  "contextFileName": "GEMINI.md",
+  "mcpServers": {
+    "securityServer": {
+      "command": "node",
+      "args": ["${extensionPath}/mcp-server/security.ts"],
+      "env": {}
+    }
+  }
 }