{"type":"mcp_server","name":"DevDocs","description":"DevDocs by CyberAGI streamlines software development by intelligently crawling and categorizing documentation, enabling faster technology implementation and efficient knowledge management for developers and teams. DevDocs by CyberAGI streamlines software development","category":"Developer Tools","language":"TypeScript","stars":2097,"forks":51,"owner":"cyberagiinc","github_url":"https://github.com/cyberagiinc/DevDocs","homepage":"https://www.cyberagi.ai","setup":"## Setup\n\nDevDocs is designed to be easy to use with Docker, requiring minimal setup for new users.\n\n### Prerequisites\n\n- [Docker](https://docs.docker.com/get-docker/) installed on your system\n- Git for cloning the repository\n\n### Quick Start with Docker (Recommended)\n\nFor Mac/Linux users:\n```bash\n# Clone the repository\ngit clone https://github.com/cyberagiinc/DevDocs.git\n\n# Navigate to the project directory\ncd DevDocs\n\n# Start all services using Docker\n./docker-start.sh\n```\n\nFor Windows users:\n```cmd\n# Clone the repository\ngit clone https://github.com/cyberagiinc/DevDocs.git\n\n# Navigate to the project directory\ncd DevDocs\n\n# Start all services using Docker\ndocker-start.bat\n```\n<details>\n<summary>Note for Windows Users</summary>\n\n> If you encounter permission issues, you may need to run the script as administrator or manually set permissions on the logs, storage, and crawl_results directories. The script uses the `icacls` command to set permissions, which might require elevated privileges on some Windows systems.\n>\n> **Manually Setting Permissions on Windows**: \n>\n> If you need to manually set permissions, you can do so using either the Windows GUI or command line:\n>\n> **Using Windows Explorer**:\n> 1. Right-click on each directory (logs, storage, crawl_results)\n> 2. Select \"Properties\"\n> 3. Go to the \"Security\" tab\n> 4. Click \"Edit\" to change permissions\n> 5. Click \"Add\" to add users/groups\n> 6. Type \"Everyone\" and click \"Check Names\"\n> 7. Click \"OK\"\n> 8. Select \"Everyone\" in the list\n> 9. Check \"Full control\" under \"Allow\"\n> 10. Click \"Apply\" and \"OK\"\n>\n> **Using Command Prompt (as Administrator)**:\n> ```cmd\n> icacls logs /grant Everyone:F /T\n> icacls storage /grant Everyone:F /T\n> icacls crawl_results /grant Everyone:F /T\n> ```\n</details>\n\n<details>\n<summary>Note about docker-compose.yml on Windows</summary>\n\n> If you encounter issues with the docker-compose.yml file (such as \"Top-level object must be a mapping\" error), the `docker-start.bat` script automatically fixes this by ensuring the file has the correct format and encoding. This fix is applied every time you run the script, so you don't need to manually modify the file.\n</details>\n\n\n\nThis single command will:\n1. Create all necessary directories\n2. Set appropriate permissions\n3. Build and start all Docker containers\n4. Monitor the services to ensure they're running properly\n\n### Accessing DevDocs\n\nOnce the services are running:\n- Frontend UI: http://localhost:3001\n- Backend API: http://localhost:24125\n- Crawl4AI Service: http://localhost:11235\n\n### Logs and Monitoring\n\nWhen using Docker, logs can be accessed :\n\n1. **Container Logs** (recommended for debugging):\n   ```bash\n   # View logs from a specific container\n   docker logs devdocs-frontend\n   docker logs devdocs-backend\n   docker logs devdocs-mcp\n   docker logs devdocs-crawl4ai\n   \n   # Follow logs in real-time\n   docker logs -f devdocs-backend\n   ```\n\nTo stop all services, press `Ctrl+C` in the terminal where docker-start is running.","tools":"## Available Tools\n\n1.  Intelligent Crawling: Offers smart depth control, automatic link discovery, selective crawling, and child URL detection.\n2.  Performance & Speed: Provides parallel processing, smart caching, lazy loading support, and rate limiting.\n3.  Content Processing: Enables clean extraction, multiple formats (MD, JSON), structured output, and MCP Server Integration.\n4.  Enterprise Features: Includes error recovery, full logging, API access, and team management.\n5.  MCP Server Scripts: Scripts to verify MCP server's health and configuration status, restart Docker containers with updated MCP configuration and test connectivity.\n6.  Crawl4AI Scripts: Scripts to check the status and health of the Crawl4AI service, run Crawl4AI in debug mode, and run tests against the Crawl4AI service.\n7.  Utility Scripts: Scripts to display crawl results, identify empty directories, analyze empty folders, and verify code reorganization.","faq":null,"created_at":"2025-01-15T05:27:26+00:00","updated_at":"2025-03-28T18:13:52+00:00","source_url":"https://model-context-protocol.com/servers/private-tech-documentation-server-for-developers","related_articles":[]}