DevDocs is a powerful tool that transforms documentation research into an efficient process. It intelligently crawls technical documentation websites, extracts meaningful content, and organizes it into a searchable format accessible through an MCP server. This allows developers to implement new technologies faster without spending weeks reading documentation.
For Mac/Linux users:
# Clone the repository
git clone https://github.com/cyberagiinc/DevDocs.git
# Navigate to the project directory
cd DevDocs
# Start all services using Docker
./docker-start.sh
For Windows users:
# Clone the repository
git clone https://github.com/cyberagiinc/DevDocs.git
# Navigate to the project directory
cd DevDocs
# Start all services using Docker
docker-start.bat
This command will:
Once the services are running, you can access:
If you encounter permission issues on Windows, you may need to run the script as administrator or manually set permissions on the logs, storage, and crawl_results directories.
Manually setting permissions via Command Prompt (as Administrator):
icacls logs /grant Everyone:F /T
icacls storage /grant Everyone:F /T
icacls crawl_results /grant Everyone:F /T
For debugging purposes, you can view container logs:
# View logs from a specific container
docker logs devdocs-frontend
docker logs devdocs-backend
docker logs devdocs-mcp
docker logs devdocs-crawl4ai
# Follow logs in real-time
docker logs -f devdocs-backend
DevDocs is designed to work seamlessly with Claude. To set up the integration:
Follow these steps to configure Cline/Roo Cline for optimal use with DevDocs:
The MCP server can be interacted with through various utility scripts:
# Verify the MCP server's health
./check_mcp_health.sh
# Restart and test MCP configuration
./restart_and_test_mcp.sh
For advanced crawling options, you can use the Crawl4AI service directly:
# Check the status of Crawl4AI
./check_crawl4ai.sh
# Run Crawl4AI in debug mode
./debug_crawl4ai.sh
To view crawl results in a formatted view:
./view_result.sh
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "devdocs" '{"command":"docker","args":["run","--name","devdocs-mcp","--network","host","devdocs-mcp:latest"]}'See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:
{
"mcpServers": {
"devdocs": {
"command": "docker",
"args": [
"run",
"--name",
"devdocs-mcp",
"--network",
"host",
"devdocs-mcp:latest"
]
}
}
}To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json2. Add this to your configuration file:
{
"mcpServers": {
"devdocs": {
"command": "docker",
"args": [
"run",
"--name",
"devdocs-mcp",
"--network",
"host",
"devdocs-mcp:latest"
]
}
}
}3. Restart Claude Desktop for the changes to take effect