doc-hub

doc-hub-mcp is an MCP Server that provides search and retrieval for enterprise WeChat (WeCom) and Feishu/Open Platform documentation. It packages Markdown docs and serves them through a simple MCP interface, allowing you to ask natural language questions and receive relevant API and documentation results. Typical usage involves starting the MCP server with the provided npx command and then querying the server from your AI assistant or development tool. The server exposes the documentation corpus so you can quickly look up API references, integration guides, and platform specifics while coding.

Once the server is running, you can also trigger internal utilities such as the included data scraping commands to populate or refresh the documentation dataset. These tools, such as scraping full WeCom or Feishu content, are designed to ensure the catalog stays up-to-date with platform documentation. If you’re using integration tooling like Claude Code, Codex, or Cursor, you may configure the MCP as a small, pluggable data source that the assistant can query during development sessions.

Prerequisites:

• Node.js (LTS version recommended) and npm installed on your system
• Internet access to fetch the MCP package via npx

Installation steps:

1. Verify Node.js and npm versions

   • node -v
   • npm -v

2. Run the MCP server via npx (no local installation required):

   npx -y doc-hub-mcp@latest

3. (Optional) Persist configuration for your environment You can create a small config referencing the MCP server, for example:

   { "mcpServers": { "doc-hub-mcp": { "command": "npx", "args": ["-y", "doc-hub-mcp@latest"] } } }

4. If you want to customize environment variables, set them before running (examples below):

   export DOC_ROOT=/path/to/docs export DOC_NAMESPACE=local-docs export MCP_SERVER_NAME=doc-hub

5. Start using the server with your preferred integration tool, following the tool's documentation for adding an MCP source named doc-hub-mcp.

Tips and caveats:

• First run may download a large dataset (often ~100 MB); startup can take several minutes depending on network speed.
• If the tool doesn’t show results, verify that the MCP server configuration uses valid JSON/TOML-like structures in your environment and that the command/args array matches the example (npx doc-hub-mcp@latest).
• If you need to customize document sources, use the environment variables DOC_ROOT and DOC_NAMESPACE to point to your local markdown corpus and namespace.
• This project has moved to SpecFusion; the old doc-hub-mcp project is archived and no longer maintained. Consider migrating to the newer SpecFusion workflow for broader platform coverage and up-to-date features.
• For troubleshooting, ensure your network allows fetching the required package and that your runtime environment supports spawning a child process via npx.