Scribe v0.3.0 - PyPI install path

Scribe v0.3.0

Minor-version release marking the shift from git-URL fork dependency to PyPI-published upstream. No user-facing capability changes.

What changed

The plugin's manifest used to install workspace-mcp from git+https://github.com/juliandickie/google_workspace_mcp.git@fork-extension. As of v0.3.0 it installs from PyPI -

- "args": [
-   "--from",
-   "git+https://github.com/juliandickie/google_workspace_mcp.git@fork-extension",
-   "workspace-mcp",
+ "args": [
+   "workspace-mcp@1.20.4",
    ...
  ]

This is possible because our markdown writer contribution (PR #727) and the QoL improvements that followed (PR #742) are now both shipped in upstream taylorwilsdon/google_workspace_mcp v1.20.4 on PyPI.

Why this matters

• Faster cold start - uvx pulls from PyPI cache instead of cloning a git branch
• Pinned to a known-good version - reproducible installs across machines and time
• No more fork dependency - users no longer need to trust a branch on a downstream fork; they're consuming the same upstream package the maintainer publishes
• Free upstream improvements - when taylor cuts v1.20.5, v1.21.0, etc., we test and bump the pin in plugin.json

Items addressed in upstream

The original deferred-items list from v0.2.1 has now been resolved -

Item	Status
Auto-retry on transient HTTP 500s	✅ in v1.20.3+ via PR #742
import_to_google_doc description rewording	✅ in v1.20.3+ via PR #742
list_drive_items surfaces driveId	✅ in v1.20.3+ via PR #742
Configurable scope subset per install	⏳ design discussion at upstream issue #771

Migration

If you have v0.2.x installed -

/plugin update scribe

Or full reinstall in fresh sessions -

/plugin uninstall scribe
/plugin install scribe

Existing OAuth tokens at ~/.workspace-mcp/credentials/*.json continue to work. The upstream tool surface is the post-PR-727 shape (the consolidated manage_doc_tab action tool with populate_from_markdown, create, rename, delete actions) which the v0.2.2 skills already match.

What v0.3.0 is NOT

This is not a feature release. The plugin's user-facing surface (skills, slash commands, install flow, multi-org docs) is identical to v0.2.2. The change is entirely behind-the-scenes plumbing.

Acknowledgements

Major thanks to @taylorwilsdon for the responsive review of PR #727, the elegant manage_doc_tab consolidation refactor during merge, and the same-week turnaround on the four QoL improvements via PR #742. This release exists because upstream is healthy and active.

License

MIT - see LICENSE.