salesforce-metadata-mcp 2.5.4 → 2.5.6

package/CHANGELOG.md

@@ -1,5 +1,57 @@
 # Changelog
 
+## [2.5.6] - 2026-06-05
+
+### Flow Builder Bug Fixes + Deploy Inline XML + New `sf_create_flow_from_xml` Tool
+
+Eight real-world bugs fixed based on production usage of the flow builder and deployment tools.
+
+#### Bug fixes — `sf_create_flow` (flow XML builder)
+
+- **Bug 1 — Loop connectors (HTTP 500):** Loop elements now emit the correct `<nextValueConnector>` (loop body) and `<noMoreValuesConnector>` (after loop exits) XML. Previously, a single `<connector>` was generated, which is not valid for Loop elements and caused a Salesforce 500 error on deploy. Use `loopBodyElement` for the body and `nextElement` for the exit path.
+
+- **Bug 2 — GetRecords filter value type:** GetRecords filter values are now correctly typed. When `filterValue` (literal string) is provided, `<stringValue>` is used; when `filterValueRef` (flow variable) is provided, `<elementReference>` is used. Previously, every filter value was unconditionally wrapped in `<elementReference>`, causing failures when the filter value was a plain string.
+
+- **Bug 3 — String-match operators in GetRecords:** `Contains`, `NotContain`, `StartsWith`, and `EndsWith` filter operators now always use `<stringValue>` for the filter value, matching what Salesforce Flow expects. `IsNull` now uses `<booleanValue>`. Previously, these operators generated the wrong value element type.
+
+- **Bug 4 — Loop iteration variable:** Removed the invalid `<iterationVariable>` XML element from Loop nodes — this element does not exist in the Salesforce Flow Metadata API schema. The collection item variable must be declared in the flow's `variables` array and referenced by name in downstream Assignment elements via `valueRef`.
+
+- **Bug 5 — Decision element connectors:** Each Decision rule (outcome) now generates its own `<connector>` using the new per-condition `nextElement` field. Previously, all rules shared a single connector target, making proper branching impossible. `IsNull`/`IsNotNull` operators now generate `<booleanValue>` for the right-value element instead of `<stringValue>`.
+
+- **Bug 6 — GetRecords missing fields:** GetRecords elements now support `queriedFields` (list of fields to return), `sortField`, `sortOrder` (Asc/Desc), `limitValue`, and `getFirstRecordOnly`. Previously, no sorting, limiting, or field selection was possible via the tool.
+
+#### Bug fix — `sf_deploy_metadata`
+
+- **Bug 7 — Inline XML content:** Components can now include `xmlContent` (the raw XML string) and an optional `filePath` (inferred from type/name if omitted). When `xmlContent` is provided, the file is included in the deploy zip so the component is actually created or updated. Previously, only a `package.xml` manifest was generated — deploying a component that didn't already exist in the org would silently fail with "No metadata found to deploy."
+
+#### New tool — `sf_create_flow_from_xml`
+
+- **Bug 8 — No escape hatch for complex flows:** Added `sf_create_flow_from_xml` for deploying a Salesforce Flow by providing the complete Flow XML string. Use when `sf_create_flow`'s structured builder cannot express what you need — multi-level branching, Wait elements, or flows exported from another org. Accepts `apiName`, `flowXml` (complete XML), and `activate` (boolean). Deploys via Metadata API zip and optionally activates after deploy.
+
+#### Schema additions
+- `FlowElementSchema`: new fields `loopBodyElement`, `filterValue`, `queriedFields`, `sortField`, `sortOrder`, `limitValue`, `getFirstRecordOnly`; per-condition `nextElement` on `conditions` array items
+- `DeployComponentSchema`: extends `ComponentRefSchema` with optional `xmlContent` and `filePath`
+- `CreateFlowFromXmlSchema`: new schema for `sf_create_flow_from_xml`
+
+Tool count: **133** (+1: `sf_create_flow_from_xml`)
+
+---
+
+## [2.5.5] - 2026-06-03
+
+### Auth & Quality — Token Refresh + Code Analyzer Fixes
+
+#### Auth improvement
+- **`getFreshTokenFromCLI`**: switched from `sf org display` (which redacts the access token since Salesforce CLI v2.50) to `sf org auth show-access-token`, restoring `SF_ALIAS`-based authentication
+
+#### Code quality
+- **Salesforce Code Analyzer v5**: fixed all 544 violations across `src/` — no unused variables, all `let` → `const`, no `@typescript-eslint/no-explicit-any` warnings where the dynamic type was intentional, bias-neutral terminology throughout
+- **TypeScript strict mode**: zero compiler errors; `@ts-nocheck` removed from all source files
+
+Tool count: **132** (unchanged)
+
+---
+
 ## [2.5.4] - 2026-06-03
 
 ### TypeScript Source Sync — Proper Typing for All 132 Tools

package/README.md

@@ -1,6 +1,6 @@
 # salesforce-metadata-mcp
 
-[![Version](https://img.shields.io/badge/version-2.5.4-blue.svg)](https://npmjs.com/package/salesforce-metadata-mcp)
+[![Version](https://img.shields.io/badge/version-2.5.5-blue.svg)](https://npmjs.com/package/salesforce-metadata-mcp)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
 [![MCP Compatible](https://img.shields.io/badge/MCP-Compatible-green.svg)](https://modelcontextprotocol.io)
 

package/TOOLS.md

@@ -155,12 +155,12 @@ Creates an Agentforce Einstein Copilot agent.
 ---
 
 ### sf_deploy_metadata
-Deploys metadata components via SOAP deploy.
+Deploys metadata components via SOAP deploy. Include `xmlContent` on each component to embed the XML definition in the zip — required when creating or updating a component whose source isn't already in the org.
 
 **Parameters:**
 | Parameter | Type | Description |
 |-----------|------|-------------|
-| `components` | array | `[{type, name}]` to deploy |
+| `components` | array | `[{type, name, xmlContent?, filePath?}]` — `xmlContent` includes the file in the zip |
 | `checkOnly` | boolean | Validate without deploying |
 | `runTests` | array | Test classes to run |
 | `rollbackOnError` | boolean | Rollback on any failure |
@@ -169,7 +169,23 @@ Deploys metadata components via SOAP deploy.
 **Example prompts:**
 - "Deploy the AccountService Apex class and AccountTrigger to the org"
 - "Validate the deployment of these components without making changes"
-- "Deploy MyFlow and MyClass, running MyClassTest during deployment"
+- "Deploy this Flow XML to the org: ..." (provide xmlContent)
+
+---
+
+### sf_create_flow_from_xml
+Deploys a Salesforce Flow by providing the complete Flow XML string. Use as an escape hatch when `sf_create_flow` cannot express a complex flow.
+
+**Parameters:**
+| Parameter | Type | Description |
+|-----------|------|-------------|
+| `apiName` | string | Flow API name (no spaces, starts with letter) |
+| `flowXml` | string | Complete Flow XML starting with `<?xml version...` |
+| `activate` | boolean | Activate after deployment (default false) |
+
+**Example prompts:**
+- "Deploy this exported flow XML to my org and activate it"
+- "Create a flow from this XML I copied from production"
 
 ---
 

package/dist/index.js

@@ -6,14 +6,14 @@ import { createServer } from "http";
 import { registerTools } from "./tools/index.js";
 const server = new McpServer({
     name: "salesforce-metadata-mcp",
-    version: "2.5.4",
+    version: "2.5.6",
 });
 registerTools(server);
 // ─── Transport: stdio ─────────────────────────────────────────────────────────
 async function runStdio() {
     const transport = new StdioServerTransport();
     await server.connect(transport);
-    console.error("Salesforce Metadata MCP server v2.5.4 running on stdio");
+    console.error("Salesforce Metadata MCP server v2.5.6 running on stdio");
 }
 // ─── Transport: HTTP ──────────────────────────────────────────────────────────
 function readBody(req) {
@@ -38,7 +38,7 @@ async function runHTTP() {
         const url = req.url ?? "/";
         if (url === "/health" && req.method === "GET") {
             res.writeHead(200, { "Content-Type": "application/json" });
-            res.end(JSON.stringify({ status: "ok", server: "salesforce-metadata-mcp", version: "2.5.4" }));
+            res.end(JSON.stringify({ status: "ok", server: "salesforce-metadata-mcp", version: "2.5.6" }));
             return;
         }
         if (url === "/mcp" && req.method === "POST") {
@@ -64,7 +64,7 @@ async function runHTTP() {
         res.end(JSON.stringify({ error: "Not found" }));
     });
     httpServer.listen(port, () => {
-        console.error(`Salesforce Metadata MCP server v2.5.4 running on http://localhost:${port}/mcp`);
+        console.error(`Salesforce Metadata MCP server v2.5.6 running on http://localhost:${port}/mcp`);
     });
 }
 // ─── Entry point ──────────────────────────────────────────────────────────────