zed -miaoduo

This MCP server integrates Zed with the Miaoduo MCP server ecosystem. It enables Zed-based tooling to communicate with Miaoduo’s MCP endpoints, allowing you to manage tasks, run checks, and exchange data through the Miaoduo MCP interface. The server is exposed as a CLI-driven MCP target that can be launched via npx, leveraging the Miaoduo MCP package to handle protocol details and data formatting. After starting, you can configure your Zed environment to point to the Miaoduo MCP endpoints provided by this server, and use Zed’s workflow features to interact with Miaoduo’s tooling, such as job execution, status queries, and result reporting. The extension acts as a bridge, translating Zed commands into Miaoduo MCP requests and normalizing responses for your development workflows.

Prerequisites:

• Node.js (v14 or newer) and npm installed on your machine
• Access to the Miaoduo MCP package registry (public or private, as required)

Installation steps:

1. Verify Node.js and npm: node -v npm -v

2. Install the Miaoduo MCP server via npx (no global install required): npx -y @miaoduo/miaoduo-mcp-server

3. (Optional) If you prefer a persistent setup, you can install the package locally in your project: mkdir -p mcp cd mcp npm init -y npm install @miaoduo/miaoduo-mcp-server

4. Start the MCP server (via npx or local script): npx -y @miaoduo/miaoduo-mcp-server

5. Configure your MCP client (e.g., Zed) to point at the server’s endpoint as defined by the package’s defaults or your environment configuration.

Tips and considerations:

• Ensure your Miaoduo API token and endpoint URL (if required) are correctly set in environment variables when running the server.
• If you encounter authentication errors, verify token scopes and that the token is valid for MCP operations.
• The server is designed to be used as part of a Zed workflow; ensure your Zed configuration references the correct MCP server name (e.g., zed-miaoduo) defined in mcp_config.
• If the Miaoduo MCP package updates its CLI or interface, you may need to re-run installation to pick up new features or fixes.
• Check for compatibility with your Node.js version and any corporate network restrictions (proxies, firewalls) that could affect npm or npx network access.