Deskworth and Claude Desktop

Still missingThe bundle deskworth-0.0.29.mcpb exists, 1 438 bytes, digest 376ad2ec…, and it has not been installed in a real Claude Desktop. That is the whole status of this page. Claude Code connecting over stdio proves the server; it proves nothing about a different client and a different install path.

#What the bundle is

A desktop bundle is an archive holding a local MCP server and a manifest, installed in one click and speaking over standard input and output 2. Deskworth’s weighs 1 438 bytes — the same 1 438 from 0.0.24 to 0.0.29 — and that number is the interesting part.

The binary is not inside it. The manifest points at the application already installed on the machine. Copying fifty megabytes into an extension would create two executables that diverge at the first update — the app updates, the extension does not.

• PACKAGEDThe bundle is built and shippedIt is produced by the build, and seven tests hold that its manifest and the server agree on the same tools, the same prompts and the same flag.
• PLANNEDInstalled and called in a real Claude DesktopNot done. Until someone double-clicks it and a tool answers, this page will not say it works — the version negotiation that broke the first Claude Code connection is exactly the kind of thing only a real install finds.
• PLANNEDListed in a connectors directoryA different question again, with its own requirements: tool annotations, a privacy policy, working examples.

#Why local and not remote

Everything Deskworth does happens on the operator’s machine: the vendor CLIs are installed there, the keychain is there, the data room is there. A remote connector’s connection starts from the vendor’s servers, so it could reach none of it 4. The bundle is the shape that fits; the remote connector is the shape that does not.

#Three things that would not change

• The client would call Deskworth; Deskworth would then run its own agents, on its own machine, in its own workspaces.
• A client subscription would not pay for the vendor CLIs those agents drive. Those stay yours, signed in on your machine.
• Deskworth’s sub-agents would remain Deskworth’s. They inherit their parent card’s reach and budget, and no protocol promotes them into a client’s own delegation tree.