# Desktop MCP Integration Kit Windows .NET10 WinForms sample app, current-user named-pipe bridge, stdio MCP shim, create-only installer/remover and connector JSON output. Requires Windows10/11, .NET10 SDK and Python3.10+. No model subscription or hosted service required to run the protocol tests; using your own assistant is optional and follows its own terms. `python install.py install C:\Users\you\AppData\Local\DesktopMcpSample` builds a fresh framework-dependent installation. Run Desktop/DesktopSample.exe, edit the sample note and explicitly enable both sharing controls. Closing the app revokes access. The session unlock is a sharing gate, not password authentication. Your Windows account is the security boundary. Note text is in memory only. `python install.py connector ` prints one generic MCP config entry. Merge it into your chosen compatible assistant's configuration yourself; this kit does not modify existing assistant settings. Launch the shim at Shim/desktop-sample-mcp.exe as a local stdio server. Ask the assistant to call status, then read_note. Only that note can be read. No shell, filesystem, delete, signing, network or arbitrary write tool is exposed. Tool results are sent to your assistant under its own data policy. Disable sharing for private content. `python install.py uninstall ` removes only the recorded installation after checking every file hash and refusing unknown/modified files. Close both app and assistant shim first. No admin rights, registry edits or startup tasks required. Tests: `python -m unittest discover -s tests -v`. Builds in a temporary folder, launches the real app backend in synthetic headless mode and real stdio shim, performs MCP initialize/list/call across the actual Windows pipe, exercises locked, disabled and not-running states, then removes its installation. This demonstrates transport/tool execution; it is not evidence that a particular assistant UI has loaded the connector. Native visual and assistant-host acceptance remain pending. The sample uses an inherited MCP protocol implementation supporting published 2025 protocol versions. It is a developer sample, not a universal assistant-brand compatibility promise. Keep payloads small and use with trusted same-user clients; the bridge is not an isolation boundary against hostile processes in your account.