mcpb
Desktop Extensions: One-click local MCP server installation in desktop apps
by modelcontextprotocolTypeScript
Commit activity
Last 12 weeks · 0 commits
Community health
5 of 6 standards met
87
✓README✓License✓Contributing✓Code of Conduct○Issue Template✓PR Template
Recent PRs & issues
Quiet · Last activity 2mo ago
See all on GitHub →
The manifest schema rejects inside a entry, allowing only and . A registry that consumes the declared tools as MCP objects therefore cannot accept them, because requires . This is not hypothetical: Smithery's publish endpoint answers 400 with , once per tool, for a bundle whose manifest passes . The result is that a bundle can declare tools that no consumer expecting the MCP shape can use, and declaring them costs a publish rather than gaining anything. Reproduction with 0.3: Removing validates and packs, and is then rejected downstream. Question Is the omission deliberate — being a display hint rather than a capability declaration — or should the entry allow the full shape? If it is deliberate, saying so in MANIFEST.md would help, since the natural reading of a array is that it carries what returns. Filed the mirror of this at https://github.com/arcadeai-labs/smithery-cli/issues/806; the two schemas contradict each other and I have no view on which side should move.
## Summary Fixes modelcontextprotocol/mcpb#241. This narrows the default source map excludes and keeps in packaged bundles. The old defaults could drop runtime files in two common cases: package directories whose names end in , such as CLI shims under that packages probe at module load time The default still excludes normal source map files such as , , , , and . To verify
## Summary substitute system variables inside default values before applying them to substitute missing optional values as empty strings instead of leaving raw placeholders add regression tests for defaults and unset optional config values Fixes #250. Fixes #251. To verify
Recent fixes
Summary This PR adds unit tests for the CLI initialization logic in and introduces a small refactor to improve testability. Several function parameters were renamed (e.g. → , , etc.) to make inputs easier to construct and reason about in isolation during testing. Changes Add unit tests for CLI helper functions in Improve parameter naming for clearer and more testable inputs Test default value resolution: Test MCP configuration generation () Test entry point resolution () Test CLI behavior of across multiple scenarios Validate console output (, ) behavior Test Isolation To ensure deterministic and environment-independent tests: , , and are mocked Console output is captured using spies File system state and user input are simulated This allows the CLI logic to be tested without relying on the actual environment or user interaction. Notes The parameter renaming is purely structural and was introduced to improve test clarity and isolation. Tests only exercise existing behavior and do not introduce functional changes. Impact Improves test coverage for CLI initialization logic and ensures consistent behavior across a wide range of input scenarios. Attribution This contribution was generated with assistance from 3TG. 3TG is a behavior-first test generation tool for TypeScript functions and React components that creates clean, maintainable tests and improves developer productivity. Follow-up If maintainers prefer the previous parameter naming, the tests can be adapted accordingly. The current change aims to improve testability without affecting runtime behavior.
Summary Added a new Desktop Extension example for controlling Microsoft Edge browser on macOS Based on the existing Chrome AppleScript example, adapted for Edge All 10 MCP tools fully tested and working What's New New example extension in that provides MCP tools for Microsoft Edge automation through AppleScript. Features 🌐 Open URLs in new or current tabs 📑 Tab Management: List, switch, close, and reload tabs 🔄 Navigation: Browser history back/forward 💻 JavaScript Execution: Run JS code with result capture 📝 Content Retrieval: Get page text content ℹ️ Tab Information: Get current tab details Implementation Details Platform: macOS only (uses AppleScript) Based on: Chrome AppleScript example structure Runtime: Node.js with MCP SDK All functions tested: Including fixes for JavaScript execution and tab switching Testing All 10 tools have been thoroughly tested: ✅ get_current_tab ✅ list_tabs ✅ open_url ✅ reload_tab ✅ go_back / go_forward ✅ close_tab ✅ get_page_content ✅ switch_to_tab (fixed tab indexing issue) ✅ execute_javascript (fixed result capture) Notes Requires Microsoft Edge to be installed on macOS User needs to enable "Allow JavaScript from Apple Events" in Edge Developer menu Extension follows the same structure and patterns as other examples in the repository 🤖 Generated with Claude Code
Structured data for AI agents
Repository: modelcontextprotocol/mcpb. Description: Desktop Extensions: One-click local MCP server installation in desktop apps Stars: 2084, Forks: 208. Primary language: TypeScript. Languages: TypeScript (93.5%), JavaScript (6.5%). Latest release: v2.1.2 (8mo ago). Open PRs: 31, open issues: 65. Last activity: 2mo ago. Community health: 87%. Top contributors: joan-anthropic, bryan-anthropic, felixrieseberg, asklar, MarshallOfSound, tobinsouth, domdomegg, himself65, ddworken, vcolin7 and others.