Help us improve
Share bugs, ideas, or general feedback.
Generates production-ready Desktop Extension (.dxt) code for an MCP, with manifest.json, MCP server via @modelcontextprotocol/sdk, tools, logging, and docs.
npx claudepluginhub ananddtyagi/claude-code-marketplace --plugin claude-desktop-extensionHow this command is triggered — by the user, by Claude, or both
Slash command
/claude-desktop-extension:claude-desktop-extensionFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
I want to build this as a Desktop Extension, abbreviated as "DXT". Please follow these steps: 1. **Read the specifications thoroughly:** - https://github.com/anthropics/dxt/blob/main/README.md - DXT architecture overview, capabilities, and integration patterns - https://github.com/anthropics/dxt/blob/main/MANIFEST.md - Complete extension manifest structure and field definitions - https://github.com/anthropics/dxt/tree/main/examples - Reference implementations including a "Hello World" example 2. **Create a proper extension structure:** - Generate a valid manifest.json followin...
/claude-desktop-extensionGenerates production-ready Desktop Extension (.dxt) code for an MCP, with manifest.json, MCP server via @modelcontextprotocol/sdk, tools, logging, and docs.
/claude-desktop-extensionBuilds Claude Desktop Extensions (DXT) with MCP server code, tool definitions/schemas, stdio transport config, and manifest.json.
/create-serverScaffolds a new MCP server project with configurable transport, example tools/resources/prompts, Zod/Pydantic validation, error handling, and Claude Desktop config.
/create-pluginGuides end-to-end creation of Claude Code plugins: discover requirements, plan components like skills/agents/hooks, implement, validate, and test. Optional plugin description.
/generate-claude-componentCreates Claude Code components interactively: commands, agents, skills, hooks, rules, plugins. Use ? for discovery mode with goal-based recommendations.
Share bugs, ideas, or general feedback.
I want to build this as a Desktop Extension, abbreviated as "DXT". Please follow these steps:
Read the specifications thoroughly:
Create a proper extension structure:
Follow best development practices:
Test considerations:
Generate complete, production-ready code that can be immediately tested. Focus on defensive programming, clear error messages, and following the exact DXT specifications to ensure compatibility with the ecosystem.