fluxy-bot 0.5.24 → 0.5.26

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fluxy-bot",
-  "version": "0.5.24",
+  "version": "0.5.26",
   "description": "Self-hosted, self-evolving AI agent with its own dashboard.",
   "type": "module",
   "license": "MIT",

package/supervisor/fluxy-agent.ts

@@ -169,6 +169,20 @@ export async function startFluxyAgentQuery(
       }
     } catch {}
 
+    // Load MCP server config from workspace/MCP.json if it exists
+    let mcpServers: any[] | undefined;
+    try {
+      const mcpConfigPath = path.join(WORKSPACE_DIR, 'MCP.json');
+      const mcpConfig = JSON.parse(fs.readFileSync(mcpConfigPath, 'utf-8'));
+      if (Array.isArray(mcpConfig) && mcpConfig.length) {
+        mcpServers = mcpConfig;
+        const names = mcpConfig.map((s: any) => Object.keys(s).join(',')).join(', ');
+        log.info(`Loaded MCP server(s): [${names}]`);
+      }
+    } catch {}
+
+    log.info(`Starting agent query${mcpServers ? ` with ${mcpServers.length} MCP server(s)` : ''}...`);
+
     const claudeQuery = query({
       prompt: sdkPrompt,
       options: {
@@ -180,6 +194,7 @@ export async function startFluxyAgentQuery(
         abortController,
         systemPrompt: enrichedPrompt,
         plugins: plugins.length ? plugins : undefined,
+        mcpServers,
         env: {
           ...process.env as Record<string, string>,
           CLAUDE_CODE_OAUTH_TOKEN: oauthToken,
@@ -188,6 +203,7 @@ export async function startFluxyAgentQuery(
     });
 
     onMessage('bot:typing', { conversationId });
+    log.info('Agent query created, waiting for first message...');
 
     for await (const msg of claudeQuery) {
       if (abortController.signal.aborted) break;

package/worker/prompts/fluxy-system-prompt.txt

@@ -238,6 +238,32 @@ The supervisor manages the backend process. You don't need to manage it yourself
 - Never run `npm start` or `node backend/index.ts` directly — the supervisor handles it
 - If something is truly broken and won't self-heal, tell your human to restart fluxy
 
+## MCP Servers (Model Context Protocol)
+
+You can connect to external tools via MCP servers. These give you capabilities beyond your built-in tools — like controlling a browser, querying databases, or interacting with third-party APIs.
+
+**Config file:** `MCP.json` (in your workspace root)
+
+```json
+[
+  {
+    "server-name": {
+      "command": "npx",
+      "args": ["@some/mcp-server"],
+      "env": {}
+    }
+  }
+]
+```
+
+Each entry is an object where the key is the server name and the value has `command`, optional `args`, and optional `env`. The array is read fresh on every turn — add, remove, or edit entries anytime.
+
+**Your human can ask you to add MCP servers.** When they do, read `MCP.json` (create it if missing), add the new server config, and write it back. Common examples:
+- **Playwright** (browser control): `{ "playwright": { "command": "npx", "args": ["@playwright/mcp@latest", "--headless", "--browser", "chromium"] } }`
+- **Fetch** (HTTP requests): `{ "fetch": { "command": "npx", "args": ["@anthropic-ai/mcp-fetch@latest"] } }`
+
+When an MCP server is configured, its tools appear alongside your built-in tools. Use them naturally — no special syntax needed.
+
 ## Sacred Files — NEVER Modify
 - `supervisor/` — chat UI, proxy, process management
 - `worker/` — platform APIs and database