@brixies-mcp/server 1.12.9 → 1.12.10

package/README.md

@@ -8,10 +8,14 @@ Local MCP server for the Brixies layout library. Requires Node.js 22+ and an act
 npx -y --prefer-online @brixies-mcp/server@latest
 ```
 
-Configure BRIXIES_API_URL and BRIXIES_API_KEY in your client's MCP process environment. Use your Brixies site's API base URL ending in /wp-json/brixies/v1. Keep the key private and out of chats and version control. Preserve existing MCP servers when editing client configuration.
+Configure BRIXIES_API_URL and BRIXIES_API_KEY in your client's MCP process environment. The official API base URL is `https://brixies.co/wp-json/brixies/v1`. Keep the key private and out of chats and version control. Preserve existing MCP servers when editing client configuration.
+
+## Version 1.12.10
+
+Uses the production API by default and reports the same version in npm and MCP. Authentication errors preserve the server’s reason without assuming that a revoked key expired. Recovery instructions apply to all supported assistants.
 
 ## Version 1.12.9
 
 Reads the recommended release from existing API response headers. Adds one update notice per MCP process when a newer stable version is recommended. It makes no extra requests and preserves tool payloads. Restart the MCP process to resolve latest; opening a new chat alone may not restart it. Existing pinned configurations must be changed manually once. Offline or missing version metadata never blocks ordinary tools.
 
-The API endpoint defaults to the Brixies staging environment; set BRIXIES_API_URL explicitly for production. This server runs locally via stdio. Releases are distributed through npm.
+The API endpoint defaults to `https://brixies.co/wp-json/brixies/v1`. An explicit `BRIXIES_API_URL` overrides this default; use your staging API URL only for staging tests. This server runs locally via stdio. Releases are distributed through npm.

package/index.js

@@ -9,12 +9,12 @@ import postcss from "postcss";
 import { deflateRawSync } from "node:zlib";
 import selectorParser from "postcss-selector-parser";
 
-const MCP_VERSION = "1.12.9";
+const MCP_VERSION = "1.12.10";
 const updateNotice = createUpdateNotice(MCP_VERSION);
 const MANUAL_JSON_DELIVERY_INSTRUCTIONS = "For manual JSON delivery, use the complete JSON value after __BRICKS_JSON__ from this tool response as the authoritative base and deliver one complete JSON code block, excluding the marker and surrounding diagnostics. If the user has not explicitly requested content-text edits, reproduce that JSON exactly. If the user explicitly requests content-text edits, change only the requested user-facing text values (for example headings, paragraphs, button labels or form labels/placeholders) at the identified locations. Preserve existing fields, HTML tags, attributes and dynamic-data tokens within those values; edit only the requested literal text. Do not infer other edits. If a requested text target is ambiguous, ask which target to edit before changing it. Preserve every unrelated value, class definition, ID, reference, CSS rule, script, code signature, element order and structural relationship. Confirmed BEM renames must still be performed by the JSON tool using new_name/new_names, not by rewriting its output. Never reconstruct or summarize the JSON, truncate it, split a combined snippet, add duplicate keys, or append an empty globalClasses field. When editing text, prefer parsing the authoritative JSON, updating only the requested text values and serializing the complete object with correct JSON escaping; serialization whitespace may change, but unrelated values must not. Do not claim verbatim delivery if text was edited. If the complete result cannot be delivered reliably, report that limitation instead of supplying partial or invented JSON. A request for JSON or text personalization alone does not authorize creating pages/classes or importing through Bricks tools; use native import tools only when the user explicitly requests a site import.";
 
-// Set BRIXIES_API_URL explicitly outside staging.
-const BRIXIES_API = process.env.BRIXIES_API_URL || "https://brixies-fip1.1wp.site/wp-json/brixies/v1";
+// Production by default. Set BRIXIES_API_URL explicitly to test against staging.
+const BRIXIES_API = process.env.BRIXIES_API_URL || "https://brixies.co/wp-json/brixies/v1";
 const BRIXIES_API_KEY = process.env.BRIXIES_API_KEY || "";
 
 // Stable identifier for API logs and firewall rules.
@@ -312,10 +312,13 @@ async function apiRequest(path) {
   if (res.status === 401) {
     return {
       ok: false,
+      status: 401,
       error:
-        `Your Brixies API key was rejected (${data.message || "invalid, expired or revoked"}). ` +
-        "Keys expire after 90 days. Check or regenerate your key on your Brixies account page, " +
-        "then update BRIXIES_API_KEY in your Claude Desktop config and restart Claude Desktop.",
+        `Your Brixies API key was rejected. Server response: ${data.message || "Authentication failed; the server did not specify the cause."} ` +
+        "Do not infer expiration unless the server explicitly reports it. " +
+        "Check or regenerate your key at https://brixies.co/account/api-key/, " +
+        "then update BRIXIES_API_KEY in your assistant's local MCP configuration and restart the Brixies MCP connection. " +
+        "Do not paste your API key into the chat.",
     };
   }
   if (res.status === 403) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brixies-mcp/server",
-  "version": "1.12.9",
+  "version": "1.12.10",
   "type": "module",
   "description": "Brixies authenticated catalog MCP",
   "main": "index.js",
@@ -9,7 +9,7 @@
   },
   "scripts": {
     "start": "node index.js",
-    "test": "node test/migration.test.mjs && node test/rename.test.mjs && node test/requests.test.mjs && node test/preparations.test.mjs && node test/updates.test.mjs && node test/update-integration.test.mjs"
+    "test": "node test/migration.test.mjs && node test/rename.test.mjs && node test/requests.test.mjs && node test/preparations.test.mjs && node test/updates.test.mjs && node test/update-integration.test.mjs && node test/production.test.mjs"
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "1.30.0",