awesome-claude-dxt

This MCP server acts as a gateway for managing and interacting with the Awesome Claude DXT collection. It leverages the MCP protocol to expose a set of tooling endpoints that help you discover, organize, and connect to Claude Desktop/DXT related resources and extensions listed in this curated repository. Users can leverage the server to fetch resource metadata, validate configurations, and coordinate with clients that implement MCP to streamline integration with Claude-based desktop extensions and related tooling. The server is designed to be lightweight and pluggable via the standard MCP manifest conventions, making it straightforward to add or update resources as the repository evolves. Typical usage involves starting the MCP server locally and then querying it through MCP clients to retrieve the list of extensions, their configuration snippets, and any environment recommendations.

Prerequisites:

• Python 3.8+ installed on your system
• Access to a shell/terminal with network access
• Optional: Docker if you prefer containerized deployment

Install and run (via Python runner shown in the repository example):

1. Clone the repository containing this MCP server: git clone https://github.com/milisp/awesome-claude-dxt.git cd awesome-claude-dxt

2. Create a virtual environment (optional but recommended): python -m venv venv source venv/bin/activate # on Windows use venv\Scripts\activate

3. Install dependencies (if a requirements.txt is provided in the repo): pip install -r requirements.txt

4. Start the MCP server (using the example runner configuration): uv run --directory ${__dirname} python ${__dirname}/main.py

If you prefer Docker:

1. Build the image (adjust image name as needed): docker build -t awesome-claude-dxt:latest .

2. Run the container: docker run -i awesome-claude-dxt:latest

Notes:

• Ensure you replace placeholders like ${__dirname} with the actual directory path when not using the MCP runner context.
• If your environment uses a different runtime (for example a Node-based or uvx-based runner), adjust the command and arguments accordingly.

Tips and common issues:

• Ensure the manifest.json in the repository is valid and points to current resources; a stale manifest may cause MCP clients to miss new additions.
• If you encounter connection issues, verify network access and that the MCP server is listening on the expected port.
• Environment variables can be used to customize endpoints or credentials; consider adding VARs like MCP_API_KEY or RESOURCE_PREFIX if your setup requires them.
• When updating resource metadata, keep the structure consistent with other MCP servers (use the same keys as defined in manifest.json examples in this repository).
• For debugging, run the server with verbose logging (where supported by your runner) to capture requests and responses between MCP clients and this server.