Skip to content

Plugin v1.0.5 — the RDP port preference finally works

Choose a tag to compare

@introfini introfini released this 31 Jul 10:22
· 15 commits to main since this release

Fixed

extensions.mcp-rdp.port is now actually read. (#17, found and fixed by @mjthoraval)

The 1.0.4 release notes claimed this was fixed. It wasn't: the change landed in src/bootstrap.ts and src/index.ts, but the build ships src/bootstrap.js, so the released XPI still read the preference without the global flag. The name resolved under extensions.zotero. and the documented preference did nothing — the bridge stayed on 6100 no matter what you set.

Both names are read now, documented first, falling back to the legacy extensions.zotero.extensions.mcp-rdp.port so anyone already running a custom port keeps it.

Invalid port values no longer break the bridge. Zotero's Config Editor pre-selects Boolean, so creating the preference without switching to Number stored true. A non-numeric value makes SocketListener open a local pipe instead of a TCP port without failing, so the bridge logged success, served nothing, and reopened itself every 10 seconds forever. Invalid values are now rejected: the bridge keeps port 6100 and logs what it ignored.

Removed

The dead src/bootstrap.ts and src/index.ts. Nothing ever compiled them, and they called three DevTools APIs that do not exist. Keeping a second, unbuildable copy of the bootstrap is exactly what shipped the broken 1.0.4 fix.

Upgrading

If you set extensions.mcp-rdp.port in the past and it did nothing, it will take effect now. Either remove the stale preference or set ZOTERO_RDP_PORT on your MCP client to match — the two sides must agree.

See Changing the RDP Port in the README.

Verified on

Zotero 9.0.6 and Zotero 10.0-beta.22, including two instances running concurrently on separate ports.