PLwC Personal
io.github.mhoedt-aiPublished by GitHub account mhoedt-aiv1.0.1-rc.1Updated Oct 24, 2026
Windows x64/Python 3.12 MCPB preview: governed local tools and persistent profiles.
Overview
A Windows-only local gateway that gives AI assistants governed access to workspace files, documents, persistent profiles and sandboxed Python/Node.js runs.
- What you can do
- Check gateway status and describe its capabilities and configuration through status and describe tools. Read and organise bounded workspace files and directories. Create and read DOCX, XLSX, PPTX, PDF and ZIP documents through a document worker. Run Python or Node.js in isolated Docker sandboxes without network access. Manage persistent profiles, reflection and memory, with proposed lasting changes separated from confirmed application via a Governor plan/apply workflow.
- When to use it
- Worth adding on a Windows 11 x64 machine when an assistant should work with local files and office documents under configured rules, keep working context across sessions, or execute code in an isolated sandbox rather than on the host.
- Requirements
- Windows 11 x64 with Python for the gateway; Node.js additionally for the Chat Bridge. Docker Desktop with Linux containers and WSL 2 for document and sandbox operations; without Docker, only profile and workspace functions work in Safe Mode. Installed via a Windows installer or the MCPB package; no API keys or environment variables are declared.
Installation
In SourceWeft
- Open PLwC Personal in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
PLwC Personal 1.0.0
Controlled local access for AI assistants, persistent profiles and governed changes.
PLwC lets compatible AI assistants read and organise allowed local files, create and read documents, and run Python or Node.js in isolated Docker environments under locally configured rules. Persistent profiles retain preferences and working context across sessions and compatible clients. The Governor separates proposed lasting profile changes from their explicitly confirmed application.
PLwC provides the local gateway and tools; you choose the AI client and model. Requests and returned contents can still be processed by an external AI provider.
Downloads and documentation
- Official release: Windows setup, checksums, sources and browser packages
- Full software description in German: 65 pages, 22 diagrams
- Full software description in English: 62 pages, 22 diagrams
- Website and installation guidance
PLwC Personal and its gateway use version 1.0.0. The browser extension, PLwC Personal Chat Bridge, uses version 2.0.0 for Chrome and Edge; its store publication is separate. The bridge protocol is 1.0.0.
What is included
- A bilingual Windows installer with the gateway, configuration and selectable client integrations.
- Bounded workspace file and directory operations.
- DOCX, XLSX, PPTX, PDF and ZIP operations through the document worker.
- Separate Docker runtimes for documents, Python and Node.js. Sandbox execution has no network access and no automatic host-shell fallback.
- Local profiles, Compile, Reflection, memory and Governor Plan/Apply workflows.
- A local Chat Bridge for ChatGPT in supported browsers; native STDIO integration for compatible MCP clients.
The gateway exposes exactly eight tools: plwc_status, plwc_describe, plwc_profile, plwc_reflection, plwc_governor, plwc_sandbox_run, plwc_workspace_operation and plwc_document_operation.
Installation and integrity
Use Windows 11 x64. Python is required for the gateway; Node.js is additionally required for the Chat Bridge. Docker Desktop with Linux containers and WSL 2 is required for document and sandbox operations. The installer checks prerequisites and asks before optional runtime downloads.
Without available Docker runtimes, profile and workspace functions remain usable in Safe Mode; document and sandbox operations are unavailable.
The official installer is PLwC-Setup-1.0.0-installer-r27.exe, SHA-256:
aa1650fd560b73d0920ce6a4f070f290602cafe271b35e6b6314fa3af25ffe23
The EXE has no Windows Authenticode signature (NotSigned). Its release manifest has an independently verified RSA signature. The release includes the signed manifest, the public trust anchor, the final runtime lock and SHA256SUMS.txt.
The unchanged V9 runtime digests are:
Sources, licenses and support
The release sources are bound to commit 0c1c367c00bb7f5bb265d129f4daa7b73167b313 and tag v1.0.0. Changes to this README do not alter that release tag or its runtime/installer artifacts.
Corresponding GPL/LGPL sources, image mapping and replacement instructions are provided alongside the binaries. Third-party components retain their own licenses and applicable modification and replacement rights.
PLwC-owned components use the PolyForm Internal Use License 1.0.0, with Personal Use Permission and Official Redistribution Permission. These permit the specified private/internal use and free sharing of complete, unmodified official releases. Modified distribution and commercial offerings require a separate agreement. Earlier lawfully published Apache 2.0 content retains its original rights; see licensing.
Known status inconsistency: successful Python and Node.js executions can report sandbox_ready: false. The agreed execution tests completed successfully; this display inconsistency is documented.
Contact: [email protected]. Voluntary support on Ko-fi.
Source: README.md at commit c8f21ed
Tools
0Version history
2- v1.0.1-rc.1LatestOct 12, 2026
- v0.2.0-rc18.dev9Sep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.