[@weaverse/mcp v3] Make live Content API tools explicit and opt-in

[paul-phan]

Problem

@weaverse/mcp@2.3.1 always registers live page, theme, project, and delete tools. Calls require WEAVERSE_API_KEY, while the README and source comments describe the authenticated account surface as read-only and claim no write tools are exposed.

Scope

• Require WEAVERSE_ENABLE_LIVE_WRITES=true before registering the existing write/delete tools.
• Keep read tools available with the current Content API key.
• Print a startup warning when live writes are enabled.
• Make the README, package description, source comments, tool names, and MCP annotations describe the released behavior accurately.
• Preserve Content API authorization and shop/scope enforcement.

Acceptance criteria

• Default tool discovery excludes every live mutation tool.
• The flag plus compatible Content API credentials exposes the existing live tools.
• Missing or incompatible credentials cannot invoke them.
• One focused registry test proves both modes.
• Documentation no longer calls a write-capable configuration read-only.

Out of scope

Proposal APIs, changesets, approval/publication tools, Builder proposal infrastructure, and a new authentication system.

[paul-phan]

Narrowed after retiring Weaverse/weaverse Weaverse/weaverse#505. This issue now owns only the current live-write discovery/disclosure defect; proposal APIs and Builder changesets are out of scope.

[paul-phan]

Released @weaverse/mcp@3.0.0 and verified it from npm.

• Default discovery is mutation-free: 9 tools.
• WEAVERSE_ENABLE_LIVE_WRITES=true adds exactly six mutation tools; every mutation still requires an accepted Content API key and project ownership.
• Synchronized the MCP with the current Content API operations, including project detail, page creation, template assignments, page defaults/formats, and the public OpenAPI document.
• Removed unsupported identity/scope behavior and corrected mutation metadata.
• Verification: 33/33 tests, build, package smoke, and production dependency audit passed; registry package smoke confirmed 9 default / 15 opt-in tools.

Closing as complete.