dify-docs

The dify-docs MCP server provides tooling to generate documentation assets for Dify-based projects. It exposes a server that can render, transform, and serve documentation content, enabling you to automate documentation generation as part of your build or CI pipeline. Typical usage involves starting the MCP server locally or in CI, then sending requests to its endpoints to generate or fetch docs, templates, and related assets. Once running, you can integrate with your existing tooling to generate markdown, HTML, or JSON representations of your documentation based on your project's sources and templates.

Primary capabilities include: starting the server to serve document generation endpoints, requesting template-driven documentation generation, and retrieving generated outputs in structured formats suitable for publishing or further processing. If you have custom templates or content sources, configure the server to point to those locations so the generated docs match your brand and structure.

Prerequisites:

• Node.js (16+ or as required by the project)
• npm or pnpm

Install steps:

1. Clone or download the repository containing the dify-docs MCP server.
2. Navigate to the project directory:
   • cd path/to/dify-docs-mcp-server
3. Install dependencies:
   • npm install (or: npm ci if you have a package-lock.json)
4. (Optional) configure environment variables if needed, e.g., PORT and LOG_LEVEL.
5. Start the server:
   • node server.js
   • or use a script if provided in package.json, e.g., npm run start
6. Verify the server is running by visiting http://localhost:3000 (or your configured port).

Notes:

• Ensure any required content sources or templates are accessible before starting.
• If a different start command is specified in your package.json, use that command accordingly.

Tips:

• If you encounter port conflicts, set a custom PORT via environment variable before starting the server (PORT=4000 node server.js).
• Check logs (LOG_LEVEL) for debugging: set LOG_LEVEL=debug for verbose output.
• If the server fails to load templates or content sources, verify file paths and permissions.
• When integrating into CI, consider running the MCP server in the background and exposing endpoints securely, then cleanly terminating after job completion.
• Ensure that any template or content source you rely on is updated consistently to avoid mismatches in generated docs.