Desktop Extensions: One-click local MCP server installation in desktop apps
by modelcontextprotocolTypeScript
Last 12 weeks · 13 commits
5 of 6 standards met
The VS Code extension would benefit from incorporating key agent workflow capabilities currently available in the CLI: Multiple concurrent chat sessions - Support opening multiple tabs to handle several questions or requests simultaneously, rather than being limited to one active query at a time Detailed progress visibility - Replace the generic "thinking..." indicator with step-by-step progress updates showing what the agent is currently processing, similar to the CLI's task monitoring Agent team orchestration - Add the ability to assign work to agent teams, monitor individual agent progress, and view task execution status, bringing the CLI's agent view and workflow management features to the extension These features would significantly improve productivity for users working on complex, multi-faceted development tasks.
Summary Fields marked in are correctly stored in the OS keychain, but the Claude Desktop settings panel displays their values in plain text under Environment variables. This undermines the security guarantee that is supposed to provide. Steps to reproduce 1. Create an extension with a user_config field, e.g.: 2. Wire it through : 3. Install the extension in Claude Desktop and supply a value. 4. Open the extension's settings panel. Observed behaviour The Environment variables section shows the full plaintext value: Expected behaviour Sensitive fields should be masked (e.g. ) in the settings panel, consistent with how they are masked during input. Impact A user leaving their screen unlocked exposes tokens that the keychain was intended to protect. The flag correctly masks the field during input but provides no protection once the extension is installed and the settings panel is opened. References Anthropic engineering post on Desktop Extensions — confirms sensitive values are stored in the OS keychain MANIFEST.md — property description: "mask input and store securely"
Is your feature request related to a problem? Please describe. I love the red alien mascot character in Claude Code — it's absolutely adorable! However, I'm always a little sad when it disappears once a chat session starts. I wish I could keep it visible while I work. Describe the solution you'd like An option in settings to keep the mascot character persistently visible in a fixed position (e.g., pinned to the right side or a corner of the screen) throughout the entire session. A simple toggle would be perfect. Describe alternatives you've considered Having the mascot minimized into a small icon rather than disappearing completely would also be a nice middle ground. Additional context The recent soccer animation is especially cute! ⚽🛸 Being able to see the mascot during coding sessions would make the experience much more enjoyable and fun. Thankyou!
Describe the bug Installing a locally-built bundle fails on Claude Desktop for macOS. The bundle is built and validated successfully ( passes, manifest schema validation passes), and the same MCP server runs fine when registered manually via (). However, installing it as a through the normal install paths fails. The failure is non-deterministic. On the same bundle, one of two outcomes occurs at random, with no correlation to which install path is used: 1. Nothing happens at all — no UI reaction, no error, and no logs (checked , including ). 2. A short delay, then an error toast appears in the top-right of Claude Desktop: (Japanese UI; the leading text means "Failed to process the file:") The message indicates the Electron IPC handler returns without sending a reply. This points to a bug in Claude Desktop's installer / IPC layer rather than the bundle itself. To Reproduce Steps to reproduce the behavior: 1. Build a bundle with (passes validation; bundled , ~6.1MB, 1907 files). 2. Attempt to install it via any of the following paths: Double-click the file (default app: Claude) Drag & drop the file onto the extensions drop area in Claude settings 3. Observe that the install either does nothing (no UI, no error, no logs) or, after a short delay, shows the error toast. 4. The outcome (silent no-op vs. error toast) appears random across attempts and is not tied to a specific install path. Expected behavior The bundle installs successfully (showing the install/permissions UI), or — if installation cannot proceed — a clear, actionable error is shown and logged. Logs No relevant logs are produced. (including ) shows nothing for the failed install attempts. After failed attempts, no partial/extracted artifacts are left behind in (no / leftover folders), suggesting the failure occurs before the extraction phase. The same MCP server works when configured manually, confirming the server itself is functional: Additional context** Claude Desktop version: 1.12603.1 (3df4fd), 2026-06-11T16:57:36.000Z macOS: 26.5 (25F71) Architecture: Apple Silicon (M2) output: validation passes, package size 6.1MB, 27.0MB unpacked, 1907 files, bundled. ():
Repository: modelcontextprotocol/mcpb. Description: Desktop Extensions: One-click local MCP server installation in desktop apps Stars: 2003, Forks: 197. Primary language: TypeScript. Languages: TypeScript (93.5%), JavaScript (6.5%). Latest release: v2.1.2 (7mo ago). Open PRs: 31, open issues: 61. Last activity: 1mo ago. Community health: 87%. Top contributors: joan-anthropic, bryan-anthropic, felixrieseberg, asklar, MarshallOfSound, tobinsouth, domdomegg, himself65, ddworken, vcolin7 and others.