@brixies-mcp/server 0.0.0-stage → 1.12.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +16 -2
- package/index.js +1251 -0
- package/lib/transforms.js +185 -0
- package/lib/update-notice.js +21 -0
- package/package.json +33 -4
package/README.md
CHANGED
|
@@ -1,3 +1,17 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Brixies MCP
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Local MCP server for the Brixies layout library. Requires Node.js 22+ and an active Brixies API key and membership.
|
|
4
|
+
|
|
5
|
+
## Run
|
|
6
|
+
|
|
7
|
+
```sh
|
|
8
|
+
npx -y --prefer-online @brixies-mcp/server@latest
|
|
9
|
+
```
|
|
10
|
+
|
|
11
|
+
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.
|
|
12
|
+
|
|
13
|
+
## Version 1.12.9
|
|
14
|
+
|
|
15
|
+
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.
|
|
16
|
+
|
|
17
|
+
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.
|