@elixium.ai/mcp-server 0.1.2 → 0.1.4

package/dist/index.js

@@ -7,6 +7,48 @@ const API_KEY = process.env.ELIXIUM_API_KEY;
 const API_URL = process.env.ELIXIUM_API_URL || "https://elixium.ai/api";
 const BOARD_SLUG = process.env.ELIXIUM_BOARD_SLUG;
 const LANE_STYLE_ENV = process.env.ELIXIUM_LANE_STYLE;
+import * as fs from "fs";
+import * as path from "path";
+import { fileURLToPath } from "url";
+// Handle init command
+if (process.argv.includes("init")) {
+    const targetDir = path.join(process.cwd(), ".agent", "workflows");
+    const __dirname = path.dirname(fileURLToPath(import.meta.url));
+    // In source, templates are at ../templates. In dist, they are copied to dist/templates? 
+    // We need to ensure package.json copies them correctly or we read from source.
+    // For 'npx run', it runs from installed node_modules.
+    // Let's assume structure:
+    // node_modules/@elixium.ai/mcp-server/
+    //   dist/index.js
+    //   templates/workflows/...
+    // When running with ts-node src/index.ts, __dirname is .../mcp-server/src
+    // Templates are at .../mcp-server/templates
+    // So we need to go up one level from src
+    const templateDir = path.resolve(__dirname, "..", "templates", "workflows");
+    console.log(`Initializing Elixium Agent Workflows...`);
+    console.log(`Target: ${targetDir}`);
+    if (!fs.existsSync(targetDir)) {
+        fs.mkdirSync(targetDir, { recursive: true });
+    }
+    const files = [
+        "manage-board.md",
+        "implement-story.md",
+        "load-board-context.md",
+    ];
+    files.forEach(file => {
+        const src = path.join(templateDir, file);
+        const dest = path.join(targetDir, file);
+        if (fs.existsSync(src)) {
+            fs.copyFileSync(src, dest);
+            console.log(`✓ Created ${file}`);
+        }
+        else {
+            console.error(`Error: Could not find template for ${file} at ${src}`);
+        }
+    });
+    console.log(`\nWorkflows initialized successfully!`);
+    process.exit(0);
+}
 if (!API_KEY) {
     console.error("Error: ELIXIUM_API_KEY environment variable is required");
     process.exit(1);
@@ -183,6 +225,10 @@ server.setRequestHandler(ListToolsRequestSchema, async () => {
                             type: "string",
                             description: "Description of the story",
                         },
+                        acceptanceCriteria: {
+                            type: "string",
+                            description: "Acceptance criteria in Given/When/Then format",
+                        },
                         lane: {
                             type: "string",
                             description: "Lane to add the story to (case-insensitive)",
@@ -332,6 +378,10 @@ server.setRequestHandler(ListToolsRequestSchema, async () => {
                             type: "string",
                             description: "Learning outcome summary",
                         },
+                        acceptanceCriteria: {
+                            type: "string",
+                            description: "Acceptance criteria in Given/When/Then format",
+                        },
                     },
                     required: ["storyId"],
                 },
@@ -437,13 +487,19 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
             }
             case "update_story": {
                 const args = request.params.arguments;
-                const { storyId, lane, ...rest } = args;
+                const { storyId, lane, state, ...rest } = args;
                 if (!storyId) {
                     throw new Error("storyId is required");
                 }
+                // Guardrail: Block AI from setting accepted/rejected states (human-in-the-loop)
+                const blockedStates = ["accepted", "rejected"];
+                if (state && blockedStates.includes(state.toLowerCase())) {
+                    throw new Error(`Cannot set state to "${state}". Acceptance decisions require human review.`);
+                }
                 const normalizedLane = await normalizeLane(lane);
                 const payload = Object.fromEntries(Object.entries({
                     ...rest,
+                    ...(state ? { state } : {}),
                     ...(normalizedLane ? { lane: normalizedLane } : {}),
                 }).filter(([, value]) => value !== undefined));
                 const response = await client.patch(`/stories/${storyId}`, payload);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elixium.ai/mcp-server",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "type": "module",
   "description": "MCP Server for Elixium.ai",
   "publishConfig": {
@@ -8,6 +8,7 @@
   },
   "files": [
     "dist",
+    "templates",
     "README.md",
     "package.json"
   ],
@@ -30,4 +31,4 @@
     "ts-node": "^10.9.0",
     "typescript": "^5.3.0"
   }
-}
+}

package/templates/workflows/implement-story.md

@@ -0,0 +1,19 @@
+---
+description: How to implement an Elixium story using the agent and MCP
+---
+
+Follow this workflow when a developer selects a story for implementation.
+
+### 1. Identify & Prepare the Story
+- Ask the developer which story they want to work on, or list the stories in the **Current** lane using `mcp_elixium_list_stories`.
+- Once a story is selected, run the `mcp_elixium_prepare_implementation` tool.
+
+### 2. Review the Brief
+- The tool will output an **Implementation Brief** containing:
+    - **Acceptance Criteria**
+    - **Assumptions / Learning Goals**
+    - **Guardrail Warnings** (e.g., if the story is in the wrong lane)
+
+### 3. Propose & Confirm
+- Review the brief and add a **Proposal**: "Here’s the smallest change that will validate it: [Describe minimal slice]"
+- Only after the developer confirms the plan should the agent transition to `EXECUTION` mode.

package/templates/workflows/load-board-context.md

@@ -0,0 +1,16 @@
+---
+description: Load Elixium board context at the start of a session
+---
+
+Use this workflow at the beginning of a session or when the user asks about board context.
+
+> [!IMPORTANT]
+> **ALWAYS** use the `mcp_elixium_*` tools. **NEVER** call the Elixium API directly.
+
+### 1. Load context
+- Call `mcp_elixium_get_iteration_context` immediately.
+- Cache the `current` and `backlog` stories for the rest of the session.
+
+### 2. Keep context fresh
+- Re-run `mcp_elixium_get_iteration_context` if the user asks for the “latest” state
+  or if the session has been idle for ~10 minutes.

package/templates/workflows/manage-board.md

@@ -0,0 +1,25 @@
+---
+description: How to manage the product backlog and board using Elixium MCP
+---
+
+Use this workflow for any project management requests (creating stories, checking status, adding epics).
+
+> [!IMPORTANT]
+> **ALWAYS** use the `mcp_elixium_*` tools. **NEVER** try to write scripts to interact with the API directly.
+> The MCP server is your authenticated, context-aware interface to the board.
+
+### 1. View the Board
+- Use `mcp_elixium_list_stories` to see the current state of the board.
+- Use `mcp_elixium_list_epics` to see high-level initiatives.
+
+### 2. Create Stories
+- **New Features**: Use `mcp_elixium_create_story` with `lane: "Backlog"` (or `Icebox` for ideas).
+- **Assumptions**: Use `mcp_elixium_create_hypothesis` for risky ideas that need validation first.
+- **Epics**: Use `mcp_elixium_create_epic` for large initiatives.
+
+### 3. Update Status
+- Use `mcp_elixium_update_story` to move cards (e.g., `lane: "Current"`, `lane: "Done"`).
+- **Do not** set state to `accepted` or `rejected`. Only humans can accept stories.
+
+### 4. Continuous Context
+- Use `mcp_elixium_get_iteration_context` when planning a coding session to see exactly what is in scope for the Current iteration.