drupal-mcp-connector 1.3.1 → 1.3.2

package/CHANGELOG.md

@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.3.2] - 2026-06-27
+
+### Fixed
+- `drupal_config_set` now forwards the configuration map under the `data` key the
+  server-side tool requires, instead of `value`. The governed tool
+  (`tool_api.mcp_sentinel_config_set`) declares its inputs as `name` plus `data` (a
+  map of top-level keys to new values, applied as a partial update). Previously the
+  connector sent `{ name, value }`, so every `config_set` was rejected with
+  `-32602 Invalid parameters … Missing required properties: \`data\``. The public
+  tool surface is unchanged — callers still pass `value` (a map); it is translated to
+  `data` at the call site. `config_get` / `config_list` were unaffected.
+
 ## [1.3.1] - 2026-06-27
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "drupal-mcp-connector",
-  "version": "1.3.1",
+  "version": "1.3.2",
   "description": "A secure, multi-site Model Context Protocol (MCP) connector for Drupal — dual-protocol JSON:API and GraphQL.",
   "type": "module",
   "main": "src/index.js",

package/src/tools/config.js

@@ -57,6 +57,11 @@ async function configList({ site: siteName, prefix }) {
 /**
  * Set a configuration value. Governed and audited server-side; the connector
  * additionally enforces the config-write cap before dispatching.
+ *
+ * The public `value` is a map of top-level config keys to their new values; the
+ * server-side tool (mcp_sentinel McpConfigSetTool) takes that map under the key
+ * `data` and applies a partial `$editable->set($key, $value)` per entry, so we
+ * translate `value` → `data` at the call site.
  * @param {object} args - { site?, name, value }.
  * @returns {Promise<*>} The server tool's result.
  * @throws {SecurityError} if the site is read-only or config writes are disabled.
@@ -67,7 +72,7 @@ async function configSet({ site: siteName, name, value }) {
   assertConfigScope(site, `config:set ${name}`);
   assertNotReadOnly(sec, `config:set ${name}`);
   assertConfigWriteAllowed(sec);
-  return callServerTool(site, SERVER_TOOLS.configSet, { name, value });
+  return callServerTool(site, SERVER_TOOLS.configSet, { name, data: value });
 }
 
 // ---------------------------------------------------------------------------
@@ -163,7 +168,7 @@ export const definitions = [
       properties: {
         site:  { type: "string" },
         name:  { type: "string" },
-        value: { description: "The configuration value to set (object, array, or scalar)." },
+        value: { type: "object", description: "A map of top-level config keys to their new values (e.g. { \"slogan\": \"Information Technology\" }). Other keys in the object are preserved server-side." },
       },
     },
   },