slc-wp-mcp-bridge 1.0.0 → 1.1.0

package/README.md

@@ -3,24 +3,29 @@
 Design WordPress sites with AI (Claude Code, Claude Desktop or any MCP client) using **native Gutenberg blocks**.
 Build and test on your own machine, then deploy to your live site, or work on your live site directly.
 
-This is the connector for the **SLC WP MCP Bridge** WordPress plugin. Built by Silicate Labs.
+This is the optional companion connector for the **Silicate Studio** WordPress plugin. Built by Silicate Labs.
+
+The plugin has its own built-in MCP server, so AI clients that support remote MCP servers can connect to a site directly
+without this package. Use the connector when you also want a private local WordPress for designing and testing,
+one-step local-to-live deployment, block markup generated with WordPress's own block code, or the site password kept in
+a file only your OS user can read.
 
 ## Quick start
 
 **1. Local site (optional, recommended).** Needs Node.js 20+. No Docker required.
 
 ```bash
-npx slc-wp-mcp-bridge@1.0.0 dev
+npx slc-wp-mcp-bridge@1.1.0 dev
 ```
 
 This starts a private local WordPress at `http://127.0.0.1:9400` (reachable only from your computer) with the plugin installed and configured.
 It is kept between runs. Credentials are random per machine and stored in `~/.slc-wp-mcp/local.json`.
 
-**2. Connect your live site** (optional). On the site: install **SLC WP MCP Bridge**, enable it under
-Settings > SLC WP MCP Bridge, allow your user, and create an Application Password (Users > Profile). Then:
+**2. Connect your live site** (optional). On the site: install **Silicate Studio**, enable it under
+Settings > Silicate Studio, allow your user, and create an Application Password (Users > Profile). Then:
 
 ```bash
-npx slc-wp-mcp-bridge@1.0.0 connect --url https://your-site.com
+npx slc-wp-mcp-bridge@1.1.0 connect --url https://your-site.com
 ```
 
 The password is typed with hidden input, checked against the site, and saved in `~/.slc-wp-mcp/sites.json`,
@@ -29,7 +34,7 @@ readable only by your OS user. It never goes into a command line, shell history,
 **3. Add the connector to your AI client** once (Claude Code shown). No secrets in this command:
 
 ```bash
-claude mcp add wordpress -- npx -y slc-wp-mcp-bridge@1.0.0
+claude mcp add wordpress -- npx -y slc-wp-mcp-bridge@1.1.0
 ```
 
 **4. Ask**, for example:
@@ -66,8 +71,10 @@ before saving. Unsupported attributes are reported instead of silently lost.
 - The local dev site listens on 127.0.0.1 only; its credentials are random per machine.
 - Local images can only be uploaded from the media folder (current directory or `SLC_MEDIA_ROOT`), must be real
   JPEG/PNG/GIF/WebP/AVIF files (checked by content) and at most 10 MB.
-- No install scripts; the full dependency tree is pinned with `npm-shrinkwrap.json`. Pin the version in your MCP
-  config (`slc-wp-mcp-bridge@1.0.0`) so updates only happen when you choose.
+- Self-contained: the package has **no dependencies** and no install scripts, so installing it fetches nothing
+  else. Third-party code (MCP SDK, zod, WordPress block packages, jsdom) is bundled at build time from a pinned,
+  audited lockfile, unminified so it can be reviewed; licences are listed in `dist/THIRD_PARTY_NOTICES.txt`.
+  Pin the version in your MCP config (`slc-wp-mcp-bridge@1.1.0`) so updates only happen when you choose.
 
 **On your site**
 - Only Application Passwords from users an administrator allowed; WordPress capabilities always apply.
@@ -98,4 +105,5 @@ npx slc-wp-mcp-bridge reset --yes          delete the local site
 
 ## License
 
-GPL-2.0-or-later. Copyright (C) 2026 Silicate Labs. "SLC WP MCP Bridge" and "Silicate Labs" are names of Silicate Labs.
+GPL-2.0-or-later. Copyright (C) 2026 Silicate Labs. "Silicate Labs" is a name of Silicate Labs. Not affiliated with or
+endorsed by the Model Context Protocol project, Anthropic, WordPress or the WordPress Foundation.