[{"_1":2,"_310":-5,"_311":-5},"loaderData",{"_3":4,"_29":30,"_31":32,"_254":255},"root",{"_5":6,"_14":15},"toasts",[7],{"_8":9,"_10":11,"_12":13},"uid","019726cf-269b-74b8-afa5-1b4db9fb4d53","title","Tool not found","type","error","visitor",{"_16":17,"_18":19},"viewportWidth",1280,"visitorSession",{"_20":21,"_23":24,"_25":-5,"_26":27,"_28":-5},"attributes",[22],"BOT","id",7058884,"membership","referenceId","01971406-43e3-74e8-b880-2f000258007a","userAccount","routes/_public/_layout",{},"routes/_public/mcp/servers/~namespace/~slug/_pages/_layout",{"_33":34,"_75":-5,"_76":35,"_36":77,"_172":173,"_253":124},"availableLocales",[35,47,54,61,68],{"_36":37,"_40":44,"_45":46},"mcpServer",{"_38":39,"_40":41,"_42":43},"description","Integrates with Claude to enable intelligent querying of documentation data, transforming crawled technical documentation into an actionable resource that LLMs can directly interact with.","name","DevDocs MCP Server","readme","# DevDocs by CyberAGI 🚀\n\n

\n $\"DevDocs$ \n\n\n

\n Turn Weeks of Documentation Research into Hours of Productive Development\n

\n\n

\n Perfect For •\n Features •\n Why DevDocs •\n Getting Started •\n Scripts •\n Compare to FireCrawl •\n Discord •\n DevDocs Roadmap\n

\n\n## 🚀 Technology Partners\n\n

\n\n $\"Anthropic\"$ \n \n $\"OpenAI\"$ \n \n $\"CyberAGI\"$ \n \n $\"Crawl4AI\"$ \n\n

\n\n## 🎯 Perfect For\n\n### 🏢 Enterprise Software Developers\nSkip weeks of reading documentation and dealing with technical debt. Implement ANY technology faster by letting DevDocs handle the heavy lifting of documentation understanding.\n\n### 🕸️ Web Scrapers\nPull entire contents of websites with Smart Discovery of Child URLs up to level 5. Perfect for both internal and external website documentation with intelligent crawling.\n\n### 👥 Development Teams\nLeverage internal documentation with built-in MCP servers and Claude integration for intelligent data querying. Transform your team's knowledge base into an actionable resource.\n\n### 🚀 Indie Hackers\nDevDocs + VSCode(cline) + Your Idea = Ship products fast with ANY technology. No more getting stuck in documentation hell when building your next big thing.\n\n## ✨ Features\n\n### 🧠 Intelligent Crawling\n- **Smart Depth Control**: Choose crawl depth from 1-5 levels\n- **Automatic Link Discovery**: Finds and categorizes all related content\n- **Selective Crawling**: Pick exactly what you want to extract\n- **Child URL Detection**: Automatically discovers and maps website structure\n\n### ⚡ Performance & Speed\n- **Parallel Processing**: Crawl multiple pages simultaneously\n- **Smart Caching**: Never waste time on duplicate content\n- **Lazy Loading Support**: Handles modern web apps effortlessly\n- **Rate Limiting**: Respectful crawling that won't overload servers\n\n### 🎯 Content Processing\n- **Clean Extraction**: Get content without the fluff\n- **Multiple Formats**: Export to MD or JSON for LLM fine-tuning\n- **Structured Output**: Logically organized content\n- **MCP Server Integration**: Ready for AI processing\n\n### 🛡️ Enterprise Features\n- **Error Recovery**: Auto-retry on failures\n- **Full Logging**: Track every operation\n- **API Access**: Integrate with your tools\n- **Team Management**: Multiple seats and roles\n\n## 🤔 Why DevDocs?\n\n### The Problem\nDocumentation is everywhere and LLMs are OUTDATED in their knowledge. Reading it, understanding it, and implementing it takes weeks of research and development even for senior engineers. **We cut down that time to hours.**\n\n### Our Solution\nDevDocs brings documentation to you. Point it at any tech documentation URL, and watch as it:\n1. Discovers all related pages to that technology\n2. Extracts meaningful content without the fluff\n3. Organizes information logically inside an MCP server ready for your LLM to query\n4. Presents it in a clean, searchable format in MD or JSON for finetuning LLM purpose\n\n🔥 We want anyone in the world to have the ability to build amazing products quickly using the most cutting edge LLM technology. \n\n## 💰 Pricing Comparison\n\n| Feature | DevDocs | Firecrawl |\n|---------|---------|-----------|\n| Free Tier | Unlimited pages | None |\n| Starting Price | Free Forever | $16/month |\n| Enterprise Plan | Custom | $333/month |\n| Crawl Speed | 1000/min | 20/min |\n| Depth Levels | Up to 5 | Limited |\n| Team Seats | Unlimited | 1-5 seats |\n| Export Formats | MD, JSON, LLM-ready MCP servers | Limited formats |\n| API Access | Coming Soon | Limited |\n| Model Context Protocol Integration | ✅ | ❌ |\n| Support | Priority Available via Discord | Standard only |\n| Self-hosted (free use) | ✅ | ❌ |\n\n## 🚀 Getting Started\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# Configure environment variables\n# Copy the template file to .env\ncp .env.template .env\n\n# Ensure NEXT_PUBLIC_BACKEND_URL in .env is set correctly (e.g., http://localhost:24125)\n# This allows the frontend (running in your browser) to communicate with the backend service.\n\n\n# Start all services using Docker\n./docker-start.sh\n```\n\nFor Windows users: Experimental Only (Not Tested Yet)\n```cmd\n# Clone the repository\ngit clone https://github.com/cyberagiinc/DevDocs.git\n\n# Navigate to the project directory\n\ncd DevDocs\n\n# Configure environment variables\n# Copy the template file to .env\n\ncopy .env.template .env\n\n# Ensure NEXT_PUBLIC_BACKEND_URL in .env is set correctly (e.g., http://localhost:24125)\n\n# This allows the frontend (running in your browser) to communicate with the backend service.\n\n# Prerequisites: Install WSL 2 and Docker Desktop\n# Docker Desktop for Windows requires WSL 2. Please ensure you have WSL 2 installed and running first.\n# 1. Install WSL 2: Follow the official Microsoft guide: https://learn.microsoft.com/en-us/windows/wsl/install\n# 2. Install Docker Desktop for Windows: Download and install from the official Docker website. Docker Desktop includes Docker Compose.\n\n\n\n# Start all services using Docker\ndocker-start.bat\n```\n

Note for Windows Users

\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

\n\n

Note about docker-compose.yml on Windows

\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

\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.\n\n## 📜 Scripts and Their Purpose\n\nDevDocs includes various utility scripts to help with development, testing, and maintenance. Here's a quick reference:\n\n### Startup Scripts\n- `start.sh` / `start.bat` / `start.ps1` - Start all services (frontend, backend, MCP) for local development.\n- `docker-start.sh` / `docker-start.bat` - Start all services using Docker containers.\n\n### MCP Server Scripts\n- `check_mcp_health.sh` - Verify the MCP server's health and configuration status.\n- `restart_and_test_mcp.sh` - Restart Docker containers with updated MCP configuration and test connectivity.\n\n### Crawl4AI Scripts\n- `check_crawl4ai.sh` - Check the status and health of the Crawl4AI service.\n- `debug_crawl4ai.sh` - Run Crawl4AI in debug mode with verbose logging for troubleshooting.\n- `test_crawl4ai.py` - Run tests against the Crawl4AI service to verify functionality.\n- `test_from_container.sh` - Test the Crawl4AI service from within a Docker container.\n\n### Utility Scripts\n- `view_result.sh` - Display crawl results in a formatted view.\n- `find_empty_folders.sh` - Identify empty directories in the project structure.\n- `analyze_empty_folders.sh` - Analyze empty folders and categorize them by risk level.\n- `verify_reorganization.sh` - Verify that code reorganization was successful.\n\nThese scripts are organized in the following directories:\n- Root directory: Main scripts for common operations\n- `scripts/general/`: General utility scripts\n- `scripts/docker/`: Docker-specific scripts\n- `scripts/mcp/`: MCP server management scripts\n- `scripts/test/`: Testing and verification scripts\n\n## 🌍 Built for Developers, by Developers\n\nDevDocs is more than a tool—it's your documentation companion that:\n- **Saves Time**: Turn weeks of research into hours\n- **Improves Understanding**: Get clean, organized documentation\n- **Enables Innovation**: Build faster with any technology\n- **Supports Teams**: Share knowledge efficiently\n- **LLM READY**: Modern times require modern solutions, using devdocs with LLM is extremely easy and intuitive. With minimal configuration you can run Devdocs and Claude App and recognizes DevDocs's MCP server ready to chat with your data. \n\n## 🛠️ Setting Up the Cline/Roo Cline for Rapid software development.\n\n1. **Open the \"Modes\" Interface** \n - In **Roo Code**, click the **+** to create a new Mode-Specific Prompts.\n
\n \n2. **Name** \n - Give the mode a **Name** (e.g., `Research_MCP`). \n
\n3. **Role Definition Prompt**\n

Prompt

\n\n```\nExpertise and Personality: Expertise: Developer documentation retrieval, technical synthesis, and documentation search. Personality: Systematic, detail-oriented, and precise. Provide well-structured answers with clear references to documentation sections.\n\nBehavioral Mandate: Always use the Table Of Contents and Section Access tools when addressing any query regarding the MCP documentation. Maintain clarity, accuracy, and traceability in your responses.\n```\n

\n
\n\n4. **Mode-Specific Custom Instructions Prompt**\n

Prompt

\n\n\n```\n1. Table Of Contents Tool: Returns a full or filtered list of documentation topics. \n2. Section Access Tool: Retrieves the detailed content of specific documentation sections.\n\nGeneral Process: Query Interpretation: Parse the user's query to extract key topics, keywords, and context. Identify the likely relevant sections (e.g., API configurations, error handling) from the query.\n\nDiscovery via Table Of Contents: Use the Table Of Contents tool to search the documentation index for relevant sections. Filter or scan titles and metadata for matching keywords.\n\nDrill-Down Using Section Access: For each identified relevant document or section, use the Section Access tool to retrieve its content. If multiple parts are needed, request all related sections to ensure comprehensive coverage.\n\nSynthesis and Response Formation: Combine the retrieved content into a coherent and complete answer. Reference section identifiers or document paths for traceability. Validate that every aspect of the query has been addressed.\n\nError Handling: If no matching sections are found, adjust the search parameters and retry. Clearly report if the query remains ambiguous or if no relevant documentation is available.\n\nMandatory Tool Usage: \nEnforcement: Every time a query is received that requires information from the MCP server docs, the agent MUST first query the Table Of Contents tool to list potential relevant topics, then use the Section Access tool to retrieve the necessary detailed content.\n\nSearch & Retrieve Workflow: \nInterpret and Isolate: Identify the key terms and data points from the user's query.\n\nIndex Lookup: Immediately query the Table Of Contents tool to obtain a list of relevant documentation sections.\n\nTargeted Retrieval: For each promising section, use the Section Access tool to get complete content.\n\nInformation Synthesis: Merge the retrieved content, ensuring all necessary details are included and clearly referenced.\n\nFallback and Clarification: If initial searches yield insufficient data, adjust the query parameters and retrieve additional sections as needed.\n\nCustom Instruction Loading: Additional custom instructions specific to Research_MCP mode may be loaded from the .clinerules-research-mcp file in your workspace. These may include further refinements or constraints based on evolving documentation structures or query types.\n\nFinal Output Construction: The final answer should be organized, directly address the query, and include clear pointers (e.g., section names or identifiers) back to the MCP documentation. Ensure minimal redundancy while covering all necessary details.\n```\n\n

\n
\n\n## 🤝 Join Our Community\n\n- 🌟 [Star us on GitHub](https://github.com/cyberagi/devdocs)\n- 👋🏽 [Reach out to our founder on Linkedin](https://www.linkedin.com/in/shubhamkhichi/)\n- 💬 [Join our Discord Community](https://discord.gg/2594NueRg8)\n\n## 🏆 Success Stories\n\n\"DevDocs turned our 3-week implementation timeline into 2 days. It's not just a crawler, it's a development accelerator.\" - *Senior Engineer at Fortune 100 Company*\n\n\"Launched my SaaS in half the time by using DevDocs to understand and implement new technologies quickly.\" - *Successful Indie Hacker*\n\n## 🛣️ DevDocs Roadmap\n\nThis roadmap outlines the upcoming enhancements and features planned for DevDocs, our advanced web crawling platform powered by Crawl4AI. Each item is designed to leverage Crawl4AI’s capabilities to their fullest, ensuring a robust, efficient, and user-friendly web crawling experience.\n\n⸻\n\n### 1. Enhanced Crawler Logic for Dynamic Content\n\n- Implement `wait_for_images=True` to ensure all images are fully loaded before extraction.\n- Set `scan_full_page=True` to force the crawler to scroll through the entire page, triggering lazy-loaded content.\n- Introduce `scroll_delay` to add delays between scroll steps, allowing content to load properly.\n- Incorporate `wait_for` parameters to wait for specific DOM elements indicative of content loading completion.\n\n---\n\n### 2. Hot Loading with Browser Pooling\n\n- Implement a pool of pre-warmed browser instances to avoid the overhead of launching a new browser for each task.\n- Utilize `use_persistent_context=True` to maintain session data across tasks, reducing the need for repeated logins and setups.\n\n---\n\n### 3. Revamped Docker Containers with Latest DevDocs Integration\n\n- Update Docker images to incorporate the latest DevDocs features and optimizations.\n- Include environment variables for API tokens (`CRAWL4AI_API_TOKEN`) to secure API endpoints.\n- Set appropriate memory limits and resource constraints to optimize performance.\n\n---\n\n### 4. Multi-OS Docker Instance Support\n\n- Create Docker images for different architectures (e.g., `x86_64`, `ARM`) to support a wide range of systems.\n- Implement CI/CD pipelines to build and test images across multiple OS environments, ensuring compatibility and stability.\n\n---\n\n### 5. Memory-Adaptive Crawling\n\n- Integrate DevDocs’ `MemoryAdaptiveDispatcher` to dynamically adjust concurrency based on system memory availability.\n- Implement built-in rate limiting to prevent overwhelming target websites and avoid out-of-memory errors.\n\n---\n\n### 6. PDF Upload and Extraction in UI\n\n- Utilize DevDocs’ capability to export pages as PDFs (`pdf=True`) and extract content from them.\n- Develop frontend components to handle PDF uploads, display extracted content, and allow users to interact with the data.\n\n---\n\n### 7. Hosted Environment with Persistent Storage and Enhanced UX\n\n- Implement BYO-databases solutions to store data privately, crawl results, and configurations across sessions.\n- Design intuitive dashboards and interfaces for users to manage their crawls, view results, and configure settings.\n- Ensure responsive design and accessibility across various browsers.\n\n## Star History\n\n[![Star History Chart](https://api.star-history.com/svg?repos=cyberagiinc/DevDocs&type=Timeline)](https://star-history.com/#cyberagiinc/DevDocs&Timeline)\n\n

Made with ❤️ by CyberAGI Inc in 🇺🇸

\n\n

\n _{Make Software Development Better Again Contribute to DevDocs}\n

\n\n","English","tag","en-US",{"_36":48,"_40":52,"_45":53},{"_38":49,"_40":50,"_42":51},"Se integra con Claude para permitir la consulta inteligente de datos de documentación, transformando la documentación técnica rastreada en un recurso práctico con el que los LLM pueden interactuar directamente.","Servidor MCP de DevDocs","# DevDocs de CyberAGI 🚀\n\n## 🚀 Socios tecnológicos\n\n## 🎯 Perfecto para\n\n### Desarrolladores de software empresarial\n\nEvite semanas de lectura de documentación y gestión de deuda técnica. Implemente cualquier tecnología más rápido dejando que DevDocs se encargue de la ardua tarea de comprender la documentación.\n\n### 🕸️ Raspadores web\n\nExtraiga todo el contenido de sitios web con Smart Discovery of Child URL hasta el nivel 5. Perfecto para documentación de sitios web internos y externos con rastreo inteligente.\n\n### 👥 Equipos de desarrollo\n\nAproveche la documentación interna con servidores MCP integrados e integración con Claude para consultas de datos inteligentes. Transforme la base de conocimientos de su equipo en un recurso práctico.\n\n### 🚀 Hackers independientes\n\nDevDocs + VSCode(cline) + Tu idea = Entrega productos rápidamente con cualquier tecnología. Olvídate de la documentación innecesaria al desarrollar tu próximo gran proyecto.\n\n## ✨ Características\n\n### 🧠 Rastreo inteligente\n\n* **Control de profundidad inteligente** : elija la profundidad de rastreo entre 1 y 5 niveles\n* **Descubrimiento automático de enlaces** : encuentra y clasifica todo el contenido relacionado\n* **Rastreo selectivo** : elige exactamente lo que quieres extraer\n* **Detección de URL secundaria** : descubre y mapea automáticamente la estructura del sitio web\n\n### ⚡ Rendimiento y velocidad\n\n* **Procesamiento paralelo** : rastrear varias páginas simultáneamente\n* **Almacenamiento en caché inteligente** : nunca pierda tiempo con contenido duplicado\n* **Soporte de carga diferida** : maneja aplicaciones web modernas sin esfuerzo\n* **Limitación de velocidad** : rastreo respetuoso que no sobrecargará los servidores\n\n### 🎯 Procesamiento de contenido\n\n* **Extracción limpia** : obtenga contenido sin superfluidades\n* **Múltiples formatos** : Exportación a MD o JSON para el ajuste fino de LLM\n* **Salida estructurada** : contenido organizado lógicamente\n* **Integración del servidor MCP** : lista para el procesamiento de IA\n\n### 🛡️ Funciones empresariales\n\n* **Recuperación de errores** : reintento automático en caso de fallos\n* **Registro completo** : seguimiento de cada operación\n* **Acceso API** : Integre con sus herramientas\n* **Gestión de equipos** : Múltiples puestos y roles\n\n## 🤔 ¿Por qué DevDocs?\n\n### El problema\n\nLa documentación está por todas partes y los LLM están DESACTUALIZADOS en cuanto a sus conocimientos. Leerla, comprenderla e implementarla requiere semanas de investigación y desarrollo, incluso para ingenieros sénior. **Reducimos ese tiempo a horas.**\n\n### Nuestra solución\n\nDevDocs te trae la documentación. Dirígelo a cualquier URL de documentación técnica y observa cómo:\n\n1. Descubre todas las páginas relacionadas con esa tecnología.\n2. Extrae contenido significativo sin superfluidades\n3. Organiza la información de forma lógica dentro de un servidor MCP listo para que su LLM la consulte\n4. Lo presenta en un formato limpio y buscable en MD o JSON para afinar el propósito del LLM.\n\n🔥Queremos que cualquier persona en el mundo tenga la capacidad de crear productos increíbles rápidamente utilizando la tecnología LLM más avanzada.\n\n## 💰 Comparación de precios\n\n| Característica | Documentos de desarrollo | Firecrawl |\n| ------------------------------------------------ | --------------------------------------------- | ------------------ |\n| Nivel gratuito | Páginas ilimitadas | Ninguno |\n| Precio inicial | Libre para siempre | $16/mes |\n| Plan Empresarial | Costumbre | $333/mes |\n| Velocidad de arrastre | 1000/min | 20/min |\n| Niveles de profundidad | Hasta 5 | Limitado |\n| Asientos del equipo | Ilimitado | 1-5 asientos |\n| Formatos de exportación | Servidores MCP compatibles con MD, JSON y LLM | Formatos limitados |\n| Acceso a la API | Muy pronto | Limitado |\n| Integración del protocolo de contexto del modelo | ✅ | ❌ |\n| Apoyo | Prioridad disponible a través de Discord | Sólo estándar |\n| Autoalojado (uso gratuito) | ✅ | ❌ |\n\n## 🚀 Primeros pasos\n\nDevDocs está diseñado para ser fácil de usar con Docker y requiere una configuración mínima para nuevos usuarios.\n\n### Prerrequisitos\n\n* [Docker](https://docs.docker.com/get-docker/) instalado en su sistema\n* Git para clonar el repositorio\n\n### Inicio rápido con Docker (recomendado)\n\nPara usuarios de Mac/Linux:\n\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# Configure environment variables\n# Copy the template file to .env\ncp .env.template .env\n\n# Ensure NEXT_PUBLIC_BACKEND_URL in .env is set correctly (e.g., http://localhost:24125)\n# This allows the frontend (running in your browser) to communicate with the backend service.\n\n\n# Start all services using Docker\n./docker-start.sh\n```\n\nPara usuarios de Windows: solo experimental (aún no probado)\n\n```cmd\n# Clone the repository\ngit clone https://github.com/cyberagiinc/DevDocs.git\n\n# Navigate to the project directory\n\ncd DevDocs\n\n# Configure environment variables\n# Copy the template file to .env\n\ncopy .env.template .env\n\n# Ensure NEXT_PUBLIC_BACKEND_URL in .env is set correctly (e.g., http://localhost:24125)\n\n# This allows the frontend (running in your browser) to communicate with the backend service.\n\n# Prerequisites: Install WSL 2 and Docker Desktop\n# Docker Desktop for Windows requires WSL 2. Please ensure you have WSL 2 installed and running first.\n# 1. Install WSL 2: Follow the official Microsoft guide: https://learn.microsoft.com/en-us/windows/wsl/install\n# 2. Install Docker Desktop for Windows: Download and install from the official Docker website. Docker Desktop includes Docker Compose.\n\n\n\n# Start all services using Docker\ndocker-start.bat\n```\n\n> Si tiene problemas con los permisos, puede que tenga que ejecutar el script como administrador o configurar manualmente los permisos en los directorios logs, storage y crawl\\_results. El script utiliza el comando `icacls` para configurar los permisos, lo que podría requerir privilegios elevados en algunos sistemas Windows.\n>\n> **Configuración manual de permisos en Windows** :\n>\n> Si necesita establecer permisos manualmente, puede hacerlo mediante la GUI de Windows o la línea de comandos:\n>\n> **Usando el Explorador de Windows** :\n>\n> 1. Haga clic derecho en cada directorio (registros, almacenamiento, resultados de rastreo)\n> 2. Seleccione \"Propiedades\"\n> 3. Vaya a la pestaña \"Seguridad\"\n> 4. Haga clic en \"Editar\" para cambiar los permisos.\n> 5. Haga clic en \"Agregar\" para agregar usuarios/grupos\n> 6. Escribe \"Todos\" y haz clic en \"Verificar nombres\".\n> 7. Haga clic en \"Aceptar\"\n> 8. Seleccione \"Todos\" en la lista\n> 9. Marque \"Control total\" en \"Permitir\".\n> 10. Haga clic en \"Aplicar\" y \"Aceptar\".\n>\n> **Usando el símbolo del sistema (como administrador)** :\n>\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\n> Si encuentra problemas con el archivo docker-compose.yml (como el error \"El objeto de nivel superior debe ser una asignación\"), el script `docker-start.bat` lo corrige automáticamente, asegurándose de que el archivo tenga el formato y la codificación correctos. Esta corrección se aplica cada vez que ejecuta el script, por lo que no necesita modificar el archivo manualmente.\n\nEste único comando hará lo siguiente:\n\n1. Crea todos los directorios necesarios\n2. Establecer permisos apropiados\n3. Construir e iniciar todos los contenedores Docker\n4. Supervisar los servicios para garantizar que funcionen correctamente\n\n### Acceder a DevDocs\n\nUna vez que los servicios estén en ejecución:\n\n* Interfaz de usuario frontal: \n* API de backend: \n* Servicio Crawl4AI: \n\n### Registros y monitoreo\n\nAl utilizar Docker, se puede acceder a los registros:\n\n1. **Registros de contenedores** (recomendados para depuración):\n\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\nPara detener todos los servicios, presione `Ctrl+C` en la terminal donde se ejecuta docker-start.\n\n## 📜 Los guiones y su propósito\n\nDevDocs incluye varios scripts de utilidad para facilitar el desarrollo, las pruebas y el mantenimiento. Aquí tienes una referencia rápida:\n\n### Scripts de inicio\n\n* `start.sh` / `start.bat` / `start.ps1` - Inicia todos los servicios (frontend, backend, MCP) para el desarrollo local.\n* `docker-start.sh` / `docker-start.bat` : inicia todos los servicios que utilizan contenedores Docker.\n\n### Scripts del servidor MCP\n\n* `check_mcp_health.sh` : verifica el estado de configuración y salud del servidor MCP.\n* `restart_and_test_mcp.sh` : reinicia los contenedores Docker con la configuración de MCP actualizada y prueba la conectividad.\n\n### Scripts de Crawl4AI\n\n* `check_crawl4ai.sh` - Verifica el estado y la salud del servicio Crawl4AI.\n* `debug_crawl4ai.sh` : ejecuta Crawl4AI en modo de depuración con registro detallado para solucionar problemas.\n* `test_crawl4ai.py` : ejecuta pruebas contra el servicio Crawl4AI para verificar la funcionalidad.\n* `test_from_container.sh` : prueba el servicio Crawl4AI desde un contenedor Docker.\n\n### Scripts de utilidad\n\n* `view_result.sh` : muestra los resultados del rastreo en una vista formateada.\n* `find_empty_folders.sh` : identifica directorios vacíos en la estructura del proyecto.\n* `analyze_empty_folders.sh` : analiza carpetas vacías y las clasifica por nivel de riesgo.\n* `verify_reorganization.sh` - Verificar que la reorganización del código fue exitosa.\n\nEstos scripts están organizados en los siguientes directorios:\n\n* Directorio raíz: Scripts principales para operaciones comunes\n* `scripts/general/` : Scripts de utilidad general\n* `scripts/docker/` : Scripts específicos de Docker\n* `scripts/mcp/` : Scripts de administración del servidor MCP\n* `scripts/test/` : Scripts de prueba y verificación\n\n## Creado por desarrolladores, para desarrolladores\n\nDevDocs es más que una herramienta: es su compañero de documentación que:\n\n* **Ahorra tiempo** : convierte semanas de investigación en horas\n* **Mejora la comprensión** : obtenga documentación limpia y organizada\n* **Permite la innovación** : construye más rápido con cualquier tecnología\n* **Apoya a los equipos** : comparte conocimientos de manera eficiente\n* **LISTO PARA LLM** : Los tiempos modernos requieren soluciones modernas. Usar Devdocs con LLM es extremadamente fácil e intuitivo. Con una configuración mínima, puede ejecutar Devdocs y la aplicación Claude, y el servidor MCP de DevDocs está listo para interactuar con sus datos.\n\n## 🛠️ Configuración de Cline/Roo Cline para el desarrollo rápido de software.\n\n1. **Abra la interfaz \"Modos\"**\n\n * En **Roo Code** , haga clic en **+** para crear nuevas indicaciones específicas del modo.\n2. **Nombre**\n\n * Dale un **nombre** al modo (por ejemplo, `Research_MCP` ).\n3. **Indicación de definición de rol**\n\n```\nExpertise and Personality: Expertise: Developer documentation retrieval, technical synthesis, and documentation search. Personality: Systematic, detail-oriented, and precise. Provide well-structured answers with clear references to documentation sections.\n\nBehavioral Mandate: Always use the Table Of Contents and Section Access tools when addressing any query regarding the MCP documentation. Maintain clarity, accuracy, and traceability in your responses.\n```\n\n4. **Aviso de instrucciones personalizadas específicas del modo**\n\n```\n1. Table Of Contents Tool: Returns a full or filtered list of documentation topics. \n2. Section Access Tool: Retrieves the detailed content of specific documentation sections.\n\nGeneral Process: Query Interpretation: Parse the user's query to extract key topics, keywords, and context. Identify the likely relevant sections (e.g., API configurations, error handling) from the query.\n\nDiscovery via Table Of Contents: Use the Table Of Contents tool to search the documentation index for relevant sections. Filter or scan titles and metadata for matching keywords.\n\nDrill-Down Using Section Access: For each identified relevant document or section, use the Section Access tool to retrieve its content. If multiple parts are needed, request all related sections to ensure comprehensive coverage.\n\nSynthesis and Response Formation: Combine the retrieved content into a coherent and complete answer. Reference section identifiers or document paths for traceability. Validate that every aspect of the query has been addressed.\n\nError Handling: If no matching sections are found, adjust the search parameters and retry. Clearly report if the query remains ambiguous or if no relevant documentation is available.\n\nMandatory Tool Usage: \nEnforcement: Every time a query is received that requires information from the MCP server docs, the agent MUST first query the Table Of Contents tool to list potential relevant topics, then use the Section Access tool to retrieve the necessary detailed content.\n\nSearch & Retrieve Workflow: \nInterpret and Isolate: Identify the key terms and data points from the user's query.\n\nIndex Lookup: Immediately query the Table Of Contents tool to obtain a list of relevant documentation sections.\n\nTargeted Retrieval: For each promising section, use the Section Access tool to get complete content.\n\nInformation Synthesis: Merge the retrieved content, ensuring all necessary details are included and clearly referenced.\n\nFallback and Clarification: If initial searches yield insufficient data, adjust the query parameters and retrieve additional sections as needed.\n\nCustom Instruction Loading: Additional custom instructions specific to Research_MCP mode may be loaded from the .clinerules-research-mcp file in your workspace. These may include further refinements or constraints based on evolving documentation structures or query types.\n\nFinal Output Construction: The final answer should be organized, directly address the query, and include clear pointers (e.g., section names or identifiers) back to the MCP documentation. Ensure minimal redundancy while covering all necessary details.\n```\n\n## 🤝 Únete a nuestra comunidad\n\n* 🌟 [Destacanos en GitHub](https://github.com/cyberagi/devdocs)\n* 👋🏽 [Contacta con nuestro fundador en Linkedin](https://www.linkedin.com/in/shubhamkhichi/)\n* 💬 [Únete a nuestra comunidad de Discord](https://discord.gg/2594NueRg8)\n\n## 🏆 Historias de éxito\n\nDevDocs redujo nuestro cronograma de implementación de 3 semanas a 2 días. No es solo un rastreador, es un acelerador de desarrollo. - *Ingeniero sénior en una empresa de Fortune 100*\n\nLancé mi SaaS en la mitad del tiempo usando DevDocs para comprender e implementar nuevas tecnologías rápidamente. - *Hacker independiente exitoso*\n\n## Hoja de ruta de DevDocs\n\nEsta hoja de ruta describe las próximas mejoras y funciones planificadas para DevDocs, nuestra plataforma avanzada de rastreo web impulsada por Crawl4AI. Cada elemento está diseñado para aprovechar al máximo las capacidades de Crawl4AI, garantizando una experiencia de rastreo web robusta, eficiente y fácil de usar.\n\n⸻\n\n### 1. Lógica de rastreo mejorada para contenido dinámico\n\n* Implemente `wait_for_images=True` para garantizar que todas las imágenes estén completamente cargadas antes de la extracción.\n* Establezca `scan_full_page=True` para forzar al rastreador a desplazarse por toda la página, activando así la carga diferida de contenido.\n* Introduzca `scroll_delay` para agregar retrasos entre los pasos de desplazamiento, permitiendo que el contenido se cargue correctamente.\n* Incorpore parámetros `wait_for` para esperar elementos DOM específicos que indiquen la finalización de la carga del contenido.\n\n***\n\n### 2. Carga en caliente con agrupación de navegadores\n\n* Implemente un grupo de instancias de navegador precalentadas para evitar la sobrecarga de iniciar un nuevo navegador para cada tarea.\n* Utilice `use_persistent_context=True` para mantener los datos de la sesión en todas las tareas, lo que reduce la necesidad de inicios de sesión y configuraciones repetidos.\n\n***\n\n### 3. Contenedores Docker renovados con la última integración de DevDocs\n\n* Actualice las imágenes de Docker para incorporar las últimas características y optimizaciones de DevDocs.\n* Incluya variables de entorno para tokens de API ( `CRAWL4AI_API_TOKEN` ) para proteger los puntos finales de API.\n* Establezca límites de memoria y restricciones de recursos adecuados para optimizar el rendimiento.\n\n***\n\n### 4. Compatibilidad con instancias Docker en varios sistemas operativos\n\n* Cree imágenes de Docker para diferentes arquitecturas (por ejemplo, `x86_64` , `ARM` ) para admitir una amplia gama de sistemas.\n* Implemente pipelines de CI/CD para crear y probar imágenes en múltiples entornos de SO, garantizando la compatibilidad y la estabilidad.\n\n***\n\n### 5. Gateo adaptable a la memoria\n\n* Integre `MemoryAdaptiveDispatcher` de DevDocs para ajustar dinámicamente la concurrencia en función de la disponibilidad de memoria del sistema.\n* Implemente una limitación de velocidad incorporada para evitar saturar los sitios web de destino y evitar errores de falta de memoria.\n\n***\n\n### 6. Carga y extracción de PDF en la interfaz de usuario\n\n* Utilice la capacidad de DevDocs para exportar páginas como PDF ( `pdf=True` ) y extraer contenido de ellas.\n* Desarrollar componentes frontend para gestionar cargas de PDF, mostrar contenido extraído y permitir que los usuarios interactúen con los datos.\n\n***\n\n### 7. Entorno alojado con almacenamiento persistente y experiencia de usuario mejorada\n\n* Implemente soluciones de bases de datos BYO para almacenar datos de forma privada, rastrear resultados y configuraciones en todas las sesiones.\n* Diseñe paneles e interfaces intuitivos para que los usuarios administren sus rastreos, vean resultados y configuren ajustes.\n* Asegúrese de que el diseño sea adaptable y tenga accesibilidad en distintos navegadores.\n\n## Historia de las estrellas\n\n[![Gráfico de la historia de las estrellas](https://api.star-history.com/svg?repos=cyberagiinc/DevDocs\\&type=Timeline)](https://star-history.com/#cyberagiinc/DevDocs\\&Timeline)","Spanish","es-ES",{"_36":55,"_40":59,"_45":60},{"_38":56,"_40":57,"_42":58},"Claude と統合してドキュメントデータのインテリジェントなクエリを可能にし、クロールされた技術ドキュメントを LLM が直接対話できる実用的なリソースに変換します。","DevDocs MCP サーバー","# CyberAGI による DevDocs 🚀\n\n## 🚀 テクノロジーパートナー\n\n## 🎯 最適です\n\n### 🏢 エンタープライズソフトウェア開発者\n\n数週間にわたるドキュメントの読み込みと技術的負債への対処を省きましょう。DevDocsにドキュメント理解という重労働を任せることで、あらゆるテクノロジーをより迅速に実装できます。\n\n### 🕸️ ウェブスクレイパー\n\nレベル 5 までの子 URL のスマート検出により、Web サイトのコンテンツ全体を取得します。インテリジェントなクロールにより、内部および外部の Web サイトのドキュメント化に最適です。\n\n### 👥 開発チーム\n\n組み込みのMCPサーバーとClaude統合により、社内ドキュメントを活用し、インテリジェントなデータクエリを実現します。チームのナレッジベースを実用的なリソースへと変換します。\n\n### 🚀 インディーハッカー\n\nDevDocs + VSCode(cline) + あなたのアイデア = あらゆるテクノロジーを使って、製品を迅速にリリース。次の大きなプロジェクトを開発する際に、ドキュメント作成の地獄に陥ることはもうありません。\n\n## ✨ 特徴\n\n### 🧠 インテリジェントクロール\n\n* **スマート深度コントロール**: 1～5 段階の深度から潜行深度を選択\n* **自動リンク検出**:関連するすべてのコンテンツを検索して分類します\n* **選択的クロール**：抽出したいものを正確に選択\n* **子 URL 検出**: ウェブサイトの構造を自動的に検出してマッピングします\n\n### ⚡ パフォーマンスとスピード\n\n* **並列処理**: 複数のページを同時にクロールする\n* **スマートキャッシング**：重複コンテンツに時間を無駄にしない\n* **遅延読み込みサポート**: 最新のウェブアプリを簡単に処理します\n* **レート制限**: サーバーに過負荷をかけない丁寧なクロール\n\n### 🎯 コンテンツ処理\n\n* **クリーン抽出**：余分なものを省いたコンテンツを取得\n* **複数のフォーマット**: LLM の微調整のために MD または JSON にエクスポート\n* **構造化された出力**：論理的に整理されたコンテンツ\n* **MCPサーバー統合**：AI処理に対応\n\n### 🛡️ エンタープライズ機能\n\n* **エラー回復**: 失敗時の自動再試行\n* **完全なログ記録**：すべての操作を追跡\n* **APIアクセス**: ツールとの統合\n* **チーム管理**：複数の席と役割\n\n## 🤔 なぜ DevDocs なのか?\n\n### 問題\n\nドキュメントは至る所にあり、法学修士（LLM）の知識は時代遅れです。ドキュメントを読み、理解し、実装するには、上級エンジニアでさえ数週間の研究開発が必要です。**私たちはその時間を数時間に短縮します。**\n\n### 私たちのソリューション\n\nDevDocsはドキュメントをお届けします。任意の技術ドキュメントのURLを指定するだけで、次のような表示が見られます。\n\n1. その技術に関連するすべてのページを検出します\n2. 無駄な情報を排除して意味のあるコンテンツを抽出する\n3. MCPサーバー内で情報を論理的に整理し、LLMがクエリできるように準備します。\n4. LLM の目的を微調整するために、MD または JSON でクリーンで検索可能な形式で提示します。\n\n🔥 私たちは、世界中の誰もが最先端の LLM テクノロジーを使用して素晴らしい製品を迅速に構築できるようにしたいと考えています。\n\n## 💰 価格比較\n\n| 特徴 | 開発ドキュメント | ファイヤークロール |\n| ---------------- | -------------------- | --------- |\n| 無料枠 | ページ数無制限 | なし |\n| 開始価格 | 永遠に無料 | 月額16ドル |\n| エンタープライズプラン | カスタム | 月額333ドル |\n| クロール速度 | 1000/分 | 20/分 |\n| 深度レベル | 最大5 | 限定 |\n| チームシート | 無制限 | 1～5席 |\n| エクスポート形式 | MD、JSON、LLM対応MCPサーバー | 限定フォーマット |\n| APIアクセス | 近日公開 | 限定 |\n| モデルコンテキストプロトコル統合 | ✅ | ❌ |\n| サポート | Discord経由で優先的に利用可能 | 標準のみ |\n| セルフホスト（無料使用） | ✅ | ❌ |\n\n## 🚀 はじめに\n\nDevDocs は Docker で簡単に使用できるように設計されており、新しいユーザーは最小限のセットアップで済みます。\n\n### 前提条件\n\n* システムに[Docker](https://docs.docker.com/get-docker/)がインストールされている\n* リポジトリのクローンを作成するためのGit\n\n### Docker のクイックスタート (推奨)\n\nMac/Linux ユーザーの場合:\n\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# Configure environment variables\n# Copy the template file to .env\ncp .env.template .env\n\n# Ensure NEXT_PUBLIC_BACKEND_URL in .env is set correctly (e.g., http://localhost:24125)\n# This allows the frontend (running in your browser) to communicate with the backend service.\n\n\n# Start all services using Docker\n./docker-start.sh\n```\n\nWindows ユーザー向け: 実験的機能のみ (まだテストされていません)\n\n```cmd\n# Clone the repository\ngit clone https://github.com/cyberagiinc/DevDocs.git\n\n# Navigate to the project directory\n\ncd DevDocs\n\n# Configure environment variables\n# Copy the template file to .env\n\ncopy .env.template .env\n\n# Ensure NEXT_PUBLIC_BACKEND_URL in .env is set correctly (e.g., http://localhost:24125)\n\n# This allows the frontend (running in your browser) to communicate with the backend service.\n\n# Prerequisites: Install WSL 2 and Docker Desktop\n# Docker Desktop for Windows requires WSL 2. Please ensure you have WSL 2 installed and running first.\n# 1. Install WSL 2: Follow the official Microsoft guide: https://learn.microsoft.com/en-us/windows/wsl/install\n# 2. Install Docker Desktop for Windows: Download and install from the official Docker website. Docker Desktop includes Docker Compose.\n\n\n\n# Start all services using Docker\ndocker-start.bat\n```\n\n> 権限に関する問題が発生した場合、スクリプトを管理者として実行するか、logs、storage、crawl\\_resultsディレクトリの権限を手動で設定する必要がある場合があります。スクリプトは`icacls`コマンドを使用して権限を設定するため、一部のWindowsシステムでは昇格した権限が必要になる場合があります。\n>\n> **Windows で権限を手動で設定する**:\n>\n> 権限を手動で設定する必要がある場合は、Windows GUI またはコマンドラインを使用して設定できます。\n>\n> **Windowsエクスプローラーの使用**:\n>\n> 1. 各ディレクトリ（logs、storage、crawl\\_results）を右クリックします。\n> 2. 「プロパティ」を選択\n> 3. 「セキュリティ」タブに移動します\n> 4. 権限を変更するには「編集」をクリックしてください\n> 5. 「追加」をクリックしてユーザー/グループを追加します\n> 6. 「Everyone」と入力し、「名前を確認」をクリックします\n> 7. 「OK」をクリック\n> 8. リストから「全員」を選択します\n> 9. 「許可」の下の「フルコントロール」にチェックを入れます\n> 10. 「適用」と「OK」をクリックします\n>\n> **コマンドプロンプトを使用する（管理者として）** ：\n>\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\n> docker-compose.yml ファイルで問題（「トップレベルオブジェクトはマッピングである必要があります」エラーなど）が発生した場合、 `docker-start.bat`スクリプトはファイルの形式とエンコーディングが正しいことを確認することで自動的に修正します。この修正はスクリプトを実行するたびに適用されるため、ファイルを手動で変更する必要はありません。\n\nこの単一のコマンドは次のことを行います。\n\n1. 必要なディレクトリをすべて作成する\n2. 適切な権限を設定する\n3. すべてのDockerコンテナをビルドして起動する\n4. サービスが適切に実行されているか監視する\n\n### DevDocsへのアクセス\n\nサービスが実行されたら:\n\n* フロントエンド UI: \n* バックエンド API: \n* Crawl4AI サービス: \n\n### ログと監視\n\nDocker を使用する場合、ログにアクセスできます。\n\n1. **コンテナログ**(デバッグに推奨):\n\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\nすべてのサービスを停止するには、docker-start が実行されているターミナルで`Ctrl+C`を押します。\n\n## 📜 スクリプトとその目的\n\nDevDocsには、開発、テスト、メンテナンスに役立つさまざまなユーティリティスクリプトが含まれています。以下にクイックリファレンスを示します。\n\n### 起動スクリプト\n\n* `start.sh` / `start.bat` / `start.ps1` - ローカル開発用のすべてのサービス (フロントエンド、バックエンド、MCP) を開始します。\n* `docker-start.sh` / `docker-start.bat` - Docker コンテナを使用してすべてのサービスを開始します。\n\n### MCP サーバースクリプト\n\n* `check_mcp_health.sh` - MCP サーバーの健全性と構成ステータスを確認します。\n* `restart_and_test_mcp.sh` - 更新された MCP 構成で Docker コンテナを再起動し、接続をテストします。\n\n### Crawl4AI スクリプト\n\n* `check_crawl4ai.sh` - Crawl4AI サービスのステータスと健全性をチェックします。\n* `debug_crawl4ai.sh` - トラブルシューティングのために、詳細なログ記録を伴うデバッグモードで Crawl4AI を実行します。\n* `test_crawl4ai.py` - Crawl4AI サービスに対してテストを実行し、機能を検証します。\n* `test_from_container.sh` - Docker コンテナ内から Crawl4AI サービスをテストします。\n\n### ユーティリティスクリプト\n\n* `view_result.sh` - クロール結果をフォーマットされたビューで表示します。\n* `find_empty_folders.sh` - プロジェクト構造内の空のディレクトリを識別します。\n* `analyze_empty_folders.sh` - 空のフォルダーを分析し、リスクレベル別に分類します。\n* `verify_reorganization.sh` - コードの再編成が成功したことを確認します。\n\nこれらのスクリプトは次のディレクトリに整理されています。\n\n* ルートディレクトリ: 共通操作のメインスクリプト\n* `scripts/general/` : 一般的なユーティリティスクリプト\n* `scripts/docker/` : Docker固有のスクリプト\n* `scripts/mcp/` : MCP サーバー管理スクリプト\n* `scripts/test/` : テストおよび検証スクリプト\n\n## 🌍 開発者による、開発者のための開発\n\nDevDocs は単なるツールではありません。次のような機能を備えたドキュメント作成ツールです。\n\n* **時間を節約**：数週間の調査を数時間で完了\n* **理解の向上**：整理されたわかりやすいドキュメントを作成する\n* **イノベーションを可能に**: あらゆるテクノロジーでより速く構築\n* **チームをサポート**：知識を効率的に共有\n* **LLM対応**：現代社会には最新のソリューションが求められます。DevdocsとLLMの組み合わせは非常に簡単で直感的です。最小限の設定でDevdocsとClaude Appを実行でき、DevDocsのMCPサーバーを認識してデータとやり取りできるようになります。\n\n## 🛠️ 迅速なソフトウェア開発のために Cline/Roo Cline をセットアップします。\n\n1. **「モード」インターフェースを開く**\n\n * **Roo Code**で、 \\*\\*+\\*\\*をクリックして新しいモード固有のプロンプトを作成します。\n2. **名前**\n\n * モードに**名前を**付けます (例: `Research_MCP` )。\n3. **役割定義プロンプト**\n\n```\nExpertise and Personality: Expertise: Developer documentation retrieval, technical synthesis, and documentation search. Personality: Systematic, detail-oriented, and precise. Provide well-structured answers with clear references to documentation sections.\n\nBehavioral Mandate: Always use the Table Of Contents and Section Access tools when addressing any query regarding the MCP documentation. Maintain clarity, accuracy, and traceability in your responses.\n```\n\n4. **モード固有のカスタム指示プロンプト**\n\n```\n1. Table Of Contents Tool: Returns a full or filtered list of documentation topics. \n2. Section Access Tool: Retrieves the detailed content of specific documentation sections.\n\nGeneral Process: Query Interpretation: Parse the user's query to extract key topics, keywords, and context. Identify the likely relevant sections (e.g., API configurations, error handling) from the query.\n\nDiscovery via Table Of Contents: Use the Table Of Contents tool to search the documentation index for relevant sections. Filter or scan titles and metadata for matching keywords.\n\nDrill-Down Using Section Access: For each identified relevant document or section, use the Section Access tool to retrieve its content. If multiple parts are needed, request all related sections to ensure comprehensive coverage.\n\nSynthesis and Response Formation: Combine the retrieved content into a coherent and complete answer. Reference section identifiers or document paths for traceability. Validate that every aspect of the query has been addressed.\n\nError Handling: If no matching sections are found, adjust the search parameters and retry. Clearly report if the query remains ambiguous or if no relevant documentation is available.\n\nMandatory Tool Usage: \nEnforcement: Every time a query is received that requires information from the MCP server docs, the agent MUST first query the Table Of Contents tool to list potential relevant topics, then use the Section Access tool to retrieve the necessary detailed content.\n\nSearch & Retrieve Workflow: \nInterpret and Isolate: Identify the key terms and data points from the user's query.\n\nIndex Lookup: Immediately query the Table Of Contents tool to obtain a list of relevant documentation sections.\n\nTargeted Retrieval: For each promising section, use the Section Access tool to get complete content.\n\nInformation Synthesis: Merge the retrieved content, ensuring all necessary details are included and clearly referenced.\n\nFallback and Clarification: If initial searches yield insufficient data, adjust the query parameters and retrieve additional sections as needed.\n\nCustom Instruction Loading: Additional custom instructions specific to Research_MCP mode may be loaded from the .clinerules-research-mcp file in your workspace. These may include further refinements or constraints based on evolving documentation structures or query types.\n\nFinal Output Construction: The final answer should be organized, directly address the query, and include clear pointers (e.g., section names or identifiers) back to the MCP documentation. Ensure minimal redundancy while covering all necessary details.\n```\n\n## 🤝 コミュニティに参加する\n\n* 🌟 [GitHub でスターを付けてください](https://github.com/cyberagi/devdocs)\n* 👋🏽 [LinkedInで創設者に連絡を取る](https://www.linkedin.com/in/shubhamkhichi/)\n* 💬 [Discordコミュニティに参加する](https://discord.gg/2594NueRg8)\n\n## 🏆 成功事例\n\n「DevDocsのおかげで、3週間かかっていた実装期間が2日に短縮されました。これは単なるクローラーではなく、開発を加速させるツールです。」 - *Fortune 100企業のシニアエンジニア*\n\n「DevDocsを活用して新しいテクノロジーを素早く理解��、実装することで、SaaSを半分の時間で立ち上げることができました。」 -*成功したインディーハッカー*\n\n## 🛣️ DevDocs ロードマップ\n\nこのロードマップでは、Crawl4AIを搭載した高度なウェブクローリングプラットフォームであるDevDocsに今後予定されている機能強化と新機能の概要を説明します。各項目はCrawl4AIの機能を最大限に活用し、堅牢で効率的、そしてユーザーフレンドリーなウェブクローリング体験を実現するように設計されています。\n\n⸻\n\n### 1. 動的コンテンツ向けの強化されたクローラーロジック\n\n* 抽出前にすべての画像が完全に読み込まれるようにするには`wait_for_images=True`を実装します。\n* `scan_full_page=True`を設定すると、クローラーがページ全体をスクロールして、遅延読み込みコンテンツをトリガーするようになります。\n* `scroll_delay`を導入して、スクロールステップ間に遅延を追加し、コンテンツが適切に読み込まれるようにします。\n* コンテンツの読み込み完了を示す特定の DOM 要素を待機するために`wait_for`パラメータを組み込みます。\n\n***\n\n### 2. ブラウザプーリングによるホットロード\n\n* 各タスクごとに新しいブラウザを起動するオーバーヘッドを回避するために、事前にウォーミングアップされたブラウザインスタンスのプールを実装します。\n* `use_persistent_context=True`を使用すると、タスク間でセッションデータを維持し、繰り返しログインやセットアップを行う必要性が減ります。\n\n***\n\n### 3. 最新のDevDocs統合によるDockerコンテナの刷新\n\n* 最新の DevDocs 機能と最適化を組み込むために Docker イメージを更新します。\n* API エンドポイントを保護するために、API トークン ( `CRAWL4AI_API_TOKEN` ) の環境変数を含めます。\n* パフォーマンスを最適化するには、適切なメモリ制限とリソース制約を設定します。\n\n***\n\n### 4. マルチOS Dockerインスタンスのサポート\n\n* さまざまなアーキテクチャ (例: `x86_64` 、 `ARM` ) 用の Docker イメージを作成して、幅広いシステムをサポートします。\n* CI/CD パイプラインを実装して、複数の OS 環境にわたってイメージを構築およびテストし、互換性と安定性を確保します。\n\n***\n\n### 5. メモリ適応型クロール\n\n* DevDocs の`MemoryAdaptiveDispatcher`を統合して、システムメモリの可用性に基づいて同時実行性を動的に調整します。\n* 組み込みのレート制限を実装して、ターゲット Web サイトの過負荷を防ぎ、メモリ不足エラーを回避します。\n\n***\n\n### 6. UIでのPDFのアップロードと抽出\n\n* DevDocs の機能を利用してページを PDF ( `pdf=True` ) としてエクスポートし、そこからコンテンツを抽出します。\n* PDF のアップロードを処理し、抽出されたコンテンツを表示し、ユーザーがデータを操作できるようにするためのフロントエンドコンポーネントを開発します。\n\n***\n\n### 7. 永続ストレージと強化されたUXを備えたホスト環境\n\n* BYO データベースソリューションを実装して、データを非公開に保存し、結果や構成をセッション間でクロールします。\n* ユーザーがクロールを管理し、結果を表示し、設定を構成できるように、直感的なダッシュボードとインターフェースを設計します。\n* さまざまなブラウザ間でのレスポンシブなデザインとアクセシビリティを確保します。\n\n## スターの歴史\n\n[![星の歴史チャート](https://api.star-history.com/svg?repos=cyberagiinc/DevDocs\\&type=Timeline)](https://star-history.com/#cyberagiinc/DevDocs\\&Timeline)","Japanese","ja-JP",{"_36":62,"_40":66,"_45":67},{"_38":63,"_40":64,"_42":65},"Claude와 통합하여 문서 데이터에 대한 지능적 쿼리를 활성화하고, 크롤링된 기술 문서를 LLM이 직접 상호 작용할 수 있는 실행 가능한 리소스로 변환합니다.","DevDocs MCP 서버","# CyberAGI의 DevDocs 🚀\n\n## 🚀 기술 파트너\n\n## 🎯 완벽한\n\n### 🏢 엔터프라이즈 소프트웨어 개발자\n\n몇 주 동안 문서를 읽고 기술 부채를 처리하는 데 시간을 허비하지 마세요. DevDocs가 문서 이해라는 어려운 작업을 처리하여 어떤 기술이든 더 빠르게 구현할 수 있습니다.\n\n### 🕸️ 웹 스크래퍼\n\n최대 레벨 5까지 자식 URL의 스마트 발견을 통해 웹사이트의 전체 콘텐츠를 가져옵니다. 지능형 크롤링을 통해 내부 및 외부 웹사이트 문서에 적합합니다.\n\n### 👥 개발팀\n\n내장된 MCP 서버와 Claude 통합을 통해 내부 문서를 활용하여 지능적인 데이터 쿼리를 수행하세요. 팀의 지식 기반을 활용 가능한 리소스로 전환하세요.\n\n### 🚀 인디 해커\n\nDevDocs + VSCode(cline) + 당신의 아이디어 = 어떤 기술로든 빠르게 제품을 출시하세요. 다음 프로젝트를 개발할 때 더 이상 문서화의 늪에 빠질 필요가 없습니다.\n\n## ✨ 특징\n\n### 🧠 지능형 크롤링\n\n* **스마트 깊이 제어** : 1~5단계에서 크롤링 깊이를 선택하세요\n* **자동 링크 검색** : 모든 관련 콘텐츠를 찾아 분류합니다.\n* **선택적 크롤링** : 추출하려는 내용을 정확히 선택하세요\n* **자식 URL 감지** : 웹사이트 구조를 자동으로 감지하고 매핑합니다.\n\n### ⚡ 성능 및 속도\n\n* **병렬 처리** : 여러 페이지를 동시에 크롤링\n* **스마트 캐싱** : 중복 콘텐츠에 시간을 낭비하지 마세요\n* **Lazy Loading 지원** : 최신 웹 앱을 손쉽게 처리합니다.\n* **속도 제한** : 서버에 과부하를 주지 않는 존중하는 크롤링\n\n### 🎯 콘텐츠 처리\n\n* **깨끗한 추출** : 불필요한 내용 없이 콘텐츠 추출\n* **다양한 형식** : LLM 미세 조정을 위해 MD 또는 JSON으로 내보내기\n* **구조화된 출력** : 논리적으로 구성된 콘텐츠\n* **MCP 서버 통합** : AI 처리 준비 완료\n\n### 🛡️ 엔터프라이즈 기능\n\n* **오류 복구** : 실패 시 자동 재시도\n* **전체 로깅** : 모든 작업 추적\n* **API 액세스** : 도구와 통합\n* **팀 관리** : 여러 자리와 역할\n\n## 🤔 왜 DevDocs인가요?\n\n### 문제\n\n문서는 어디에나 있고 LLM의 지식은 시대에 뒤떨어져 있습니다. 이를 읽고, 이해하고, 구현하는 데는 선임 엔지니어조차도 몇 주씩 연구하고 개발해야 합니다. **저희는 그 시간을 몇 시간으로 단축했습니다.**\n\n### 우리의 솔루션\n\nDevDocs는 문서를 제공합니다. 기술 문서 URL을 DevDocs에 입력하면 다음과 같은 결과를 확인할 수 있습니다.\n\n1. 해당 기술과 관련된 모든 페이지를 검색합니다.\n2. 불필요한 내용 없이 의미 있는 콘텐츠를 추출합니다.\n3. LLM이 쿼리할 수 있도록 MCP 서버 내부에 논리적으로 정보를 구성합니다.\n4. LLM 목적을 미세 조정하기 위해 MD 또는 JSON 형식으로 깔끔하고 검색 가능한 형식으로 제공합니다.\n\n🔥 우리는 전 세계 누구나 최첨단 LLM 기술을 사용하여 놀라운 제품을 빠르게 만들 수 있는 능력을 갖기를 바랍니다.\n\n## 💰 가격 비교\n\n| 특징 | DevDocs | 파이어크롤 |\n| --------------- | ----------------------- | ------- |\n| 무료 티어 | 무제한 페이지 | 없음 |\n| 시작 가격 | 영원히 무료 | 월 16달러 |\n| 엔터프라이즈 플랜 | 관습 | 월 333달러 |\n| 크롤 속도 | 1000/분 | 20/분 |\n| 깊이 수준 | 최대 5개 | 제한된 |\n| 팀 좌석 | 제한 없는 | 1~5석 |\n| 내보내기 형식 | MD, JSON, LLM 지원 MCP 서버 | 제한된 형식 |\n| API 액세스 | 곧 출시 예정 | 제한된 |\n| 모델 컨텍스트 프로토콜 통합 | ✅ | ❌ |\n| 지원하다 | Discord를 통해 우선적으로 이용 가능 | 표준만 |\n| 셀프 호스팅(무료 사용) | ✅ | ❌ |\n\n## 🚀 시작하기\n\nDevDocs는 Docker와 함께 사용하기 쉽도록 설계되어 신규 사용자도 최소한의 설정만으로 사용할 수 있습니다.\n\n### 필수 조건\n\n* 시스템에 [Docker가](https://docs.docker.com/get-docker/) 설치됨\n* 저장소 복제를 위한 Git\n\n### Docker 빠른 시작(권장)\n\nMac/Linux 사용자의 경우:\n\n지엑스피1\n\nWindows 사용자의 경우: 실험용(아직 테스트되지 않음)\n\n```cmd\n# Clone the repository\ngit clone https://github.com/cyberagiinc/DevDocs.git\n\n# Navigate to the project directory\n\ncd DevDocs\n\n# Configure environment variables\n# Copy the template file to .env\n\ncopy .env.template .env\n\n# Ensure NEXT_PUBLIC_BACKEND_URL in .env is set correctly (e.g., http://localhost:24125)\n\n# This allows the frontend (running in your browser) to communicate with the backend service.\n\n# Prerequisites: Install WSL 2 and Docker Desktop\n# Docker Desktop for Windows requires WSL 2. Please ensure you have WSL 2 installed and running first.\n# 1. Install WSL 2: Follow the official Microsoft guide: https://learn.microsoft.com/en-us/windows/wsl/install\n# 2. Install Docker Desktop for Windows: Download and install from the official Docker website. Docker Desktop includes Docker Compose.\n\n\n\n# Start all services using Docker\ndocker-start.bat\n```\n\n> 권한 문제가 발생하면 스크립트를 관리자 권한으로 실행하거나 로그, 저장소 및 crawl\\_results 디렉터리에 대한 권한을 수동으로 설정해야 할 수 있습니다. 스크립트는 `icacls` 명령을 사용하여 권한을 설정하는데, 일부 Windows 시스템에서는 이 작업에 높은 권한이 필요할 수 있습니다.\n>\n> **Windows에서 수동으로 권한 설정하기** :\n>\n> 수동으로 권한을 설정해야 하는 경우 Windows GUI나 명령줄을 사용하여 설정할 수 있습니다.\n>\n> **Windows 탐색기 사용** :\n>\n> 1. 각 디렉토리(로그, 저장소, 크롤링 결과)를 마우스 오른쪽 버튼으로 클릭합니다.\n> 2. \"속성\"을 선택하세요\n> 3. \"보안\" 탭으로 이동하세요\n> 4. 권한을 변경하려면 \"편집\"을 클릭하세요.\n> 5. 사용자/그룹을 추가하려면 \"추가\"를 클릭하세요.\n> 6. \"모두\"를 입력하고 \"이름 확인\"을 클릭하세요.\n> 7. \"확인\"을 클릭하세요\n> 8. 목록에서 \"모두\"를 선택하세요\n> 9. \"허용\"에서 \"전체 제어\"를 체크하세요.\n> 10. \"적용\"과 \"확인\"을 클릭하세요\n>\n> **명령 프롬프트 사용(관리자 권한으로)** :\n>\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\n> docker-compose.yml 파일에 문제가 발생하는 경우(예: \"최상위 객체는 매핑이어야 합니다\" 오류), `docker-start.bat` 스크립트가 파일의 형식과 인코딩을 올바르게 설정하여 자동으로 문제를 해결합니다. 이 수정 사항은 스크립트를 실행할 때마다 적용되므로 파일을 수동으로 수정할 필요가 없습니다.\n\n이 단일 명령은 다음을 수행합니다.\n\n1. 필요한 모든 디렉토리를 만듭니다\n2. 적절한 권한 설정\n3. 모든 Docker 컨테이너를 빌드하고 시작합니다.\n4. 서비스가 제대로 실행되는지 모니터링합니다.\n\n### DevDocs에 액세스하기\n\n서비스가 실행되면:\n\n* 프런트엔드 UI: \n* 백엔드 API: \n* Crawl4AI 서비스: \n\n### 로그 및 모니터링\n\nDocker를 사용하면 로그에 액세스할 수 있습니다.\n\n1. **컨테이너 로그** (디버깅에 권장):\n\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\n모든 서비스를 중지하려면 docker-start가 실행 중인 터미널에서 `Ctrl+C` 누릅니다.\n\n## 📜 스크립트와 그 목적\n\nDevDocs에는 개발, 테스트 및 유지 관리에 도움이 되는 다양한 유틸리티 스크립트가 포함되어 있습니다. 간단한 참고 자료는 다음과 같습니다.\n\n### 시작 스크립트\n\n* `start.sh` / `start.bat` / `start.ps1` - 로컬 개발을 위해 모든 서비스(프런트엔드, 백엔드, MCP)를 시작합니다.\n* `docker-start.sh` / `docker-start.bat` - Docker 컨테이너를 사용하여 모든 서비스를 시작합니다.\n\n### MCP 서버 스크립트\n\n* `check_mcp_health.sh` - MCP 서버의 상태와 구성 상태를 확인합니다.\n* `restart_and_test_mcp.sh` - 업데이트된 MCP 구성 및 테스트 연결로 Docker 컨테이너를 다시 시작합니다.\n\n### Crawl4AI 스크립트\n\n* `check_crawl4ai.sh` - Crawl4AI 서비스의 상태와 건강 상태를 확인합니다.\n* `debug_crawl4ai.sh` - 문제 해결을 위해 자세한 로깅을 사용하여 디버그 모드에서 Crawl4AI를 실행합니다.\n* `test_crawl4ai.py` - Crawl4AI 서비스에 대한 테스트를 실행하여 기능을 확인합니다.\n* `test_from_container.sh` - Docker 컨테이너 내에서 Crawl4AI 서비스를 테스트합니다.\n\n### 유틸리티 스크립트\n\n* `view_result.sh` - 크롤링 결과를 서식이 지정된 보기로 표시합니다.\n* `find_empty_folders.sh` - 프로젝트 구조에서 빈 디렉토리를 식별합니다.\n* `analyze_empty_folders.sh` - 빈 폴더를 분석하고 위험 수준별로 분류합니다.\n* `verify_reorganization.sh` - 코드 재구성이 성공했는지 확인합니다.\n\n이러한 스크립트는 다음 디렉토리에 정리되어 있습니다.\n\n* 루트 디렉토리: 일반적인 작업을 위한 주요 스크립트\n* `scripts/general/` : 일반 유틸리티 스크립트\n* `scripts/docker/` : Docker 관련 스크립트\n* `scripts/mcp/` : MCP 서버 관리 스크립트\n* `scripts/test/` : 테스트 및 검증 스크립트\n\n## 🌍 개발자를 위해, 개발자가 만들었습니다\n\nDevDocs는 단순한 도구가 아닙니다. 다음과 같은 기능을 갖춘 문서 작성 도우미입니다.\n\n* **시간 절약** : 몇 주 걸리는 연구를 몇 시간으로 단축\n* **이해력 향상** : 깔끔하고 체계적인 문서 얻기\n* **혁신을 가능하게 합니다** : 어떤 기술로든 더 빠르게 구축하세요\n* **팀 지원** : 지식을 효율적으로 공유합니다\n* **LLM 준비 완료** : 현대 사회에는 최신 솔루션이 필요합니다. LLM과 함께 DevDocs를 사용하는 것은 매우 쉽고 직관적입니다. 최소한의 구성으로 DevDocs와 Claude 앱을 실행하고 DevDocs의 MCP 서버를 인식하여 데이터와 소통할 수 있습니다.\n\n## 🛠️ 신속한 소프트웨어 개발을 위한 Cline/Roo Cline 설정.\n\n1. **\"모드\" 인터페이스를 엽니다**\n\n * **Roo Code** 에서 **+를** 클릭하여 새로운 모드별 프롬프트를 만듭니다.\n2. **이름**\n\n * 모드에 **이름을** 지정합니다(예: `Research_MCP` ).\n3. **역할 정의 프롬프트**\n\n```\nExpertise and Personality: Expertise: Developer documentation retrieval, technical synthesis, and documentation search. Personality: Systematic, detail-oriented, and precise. Provide well-structured answers with clear references to documentation sections.\n\nBehavioral Mandate: Always use the Table Of Contents and Section Access tools when addressing any query regarding the MCP documentation. Maintain clarity, accuracy, and traceability in your responses.\n```\n\n4. **모드별 사용자 정의 지침 프롬프트**\n\n```\n1. Table Of Contents Tool: Returns a full or filtered list of documentation topics. \n2. Section Access Tool: Retrieves the detailed content of specific documentation sections.\n\nGeneral Process: Query Interpretation: Parse the user's query to extract key topics, keywords, and context. Identify the likely relevant sections (e.g., API configurations, error handling) from the query.\n\nDiscovery via Table Of Contents: Use the Table Of Contents tool to search the documentation index for relevant sections. Filter or scan titles and metadata for matching keywords.\n\nDrill-Down Using Section Access: For each identified relevant document or section, use the Section Access tool to retrieve its content. If multiple parts are needed, request all related sections to ensure comprehensive coverage.\n\nSynthesis and Response Formation: Combine the retrieved content into a coherent and complete answer. Reference section identifiers or document paths for traceability. Validate that every aspect of the query has been addressed.\n\nError Handling: If no matching sections are found, adjust the search parameters and retry. Clearly report if the query remains ambiguous or if no relevant documentation is available.\n\nMandatory Tool Usage: \nEnforcement: Every time a query is received that requires information from the MCP server docs, the agent MUST first query the Table Of Contents tool to list potential relevant topics, then use the Section Access tool to retrieve the necessary detailed content.\n\nSearch & Retrieve Workflow: \nInterpret and Isolate: Identify the key terms and data points from the user's query.\n\nIndex Lookup: Immediately query the Table Of Contents tool to obtain a list of relevant documentation sections.\n\nTargeted Retrieval: For each promising section, use the Section Access tool to get complete content.\n\nInformation Synthesis: Merge the retrieved content, ensuring all necessary details are included and clearly referenced.\n\nFallback and Clarification: If initial searches yield insufficient data, adjust the query parameters and retrieve additional sections as needed.\n\nCustom Instruction Loading: Additional custom instructions specific to Research_MCP mode may be loaded from the .clinerules-research-mcp file in your workspace. These may include further refinements or constraints based on evolving documentation structures or query types.\n\nFinal Output Construction: The final answer should be organized, directly address the query, and include clear pointers (e.g., section names or identifiers) back to the MCP documentation. Ensure minimal redundancy while covering all necessary details.\n```\n\n## 🤝 커뮤니티에 가입하세요\n\n* 🌟 [GitHub에서 별점을 주세요](https://github.com/cyberagi/devdocs)\n* 👋🏽 [LinkedIn에서 창립자에게 연락하세요](https://www.linkedin.com/in/shubhamkhichi/)\n* 💬 [Discord 커뮤니티에 가입하세요](https://discord.gg/2594NueRg8)\n\n## 🏆 성공 사례\n\n\"DevDocs 덕분에 3주가 걸리던 구현 일정이 2일로 단축되었습니다. 단순한 크롤러가 아니라 개발 가속기입니다.\" - *Fortune 100 기업 수석 엔지니어*\n\n\"DevDocs를 사용하여 새로운 기술을 빠르게 이해하고 구현함으로써 SaaS를 절반의 시간 안에 출시했습니다.\" - *성공적인 인디 해커*\n\n## 🛣️ DevDocs 로드맵\n\n이 로드맵은 Crawl4AI 기반의 고급 웹 크롤링 플랫폼인 DevDocs의 향후 개선 사항과 기능을 간략하게 설명합니다. 각 항목은 Crawl4AI의 기능을 최대한 활용하여 강력하고 효율적이며 사용자 친화적인 웹 크롤링 환경을 보장하도록 설계되었습니다.\n\n⸻\n\n### 1. 동적 콘텐츠를 위한 향상된 크롤러 로직\n\n* 모든 이미지가 추출되기 전에 완전히 로드되도록 `wait_for_images=True` 를 구현합니다.\n* `scan_full_page=True` 설정하면 크롤러가 전체 페이지를 스크롤하여 지연 로드된 콘텐츠를 트리거합니다.\n* 스크롤 단계 사이에 지연 시간을 추가하여 콘텐츠가 제대로 로드될 수 있도록 `scroll_delay` 도입했습니다.\n* `wait_for` 매개변수를 통합하여 콘텐츠 로딩 완료를 나타내는 특정 DOM 요소를 기다립니다.\n\n***\n\n### 2. 브라우저 풀링을 통한 핫 로딩\n\n* 각 작업마다 새 브라우저를 실행하는 오버헤드를 피하기 위해 미리 예열된 브라우저 인스턴스 풀을 구현합니다.\n* `use_persistent_context=True` 사용하면 작업 전반에 걸쳐 세션 데이터를 유지하여 반복적인 로그인과 설정의 필요성을 줄일 수 있습니다.\n\n***\n\n### 3. 최신 DevDocs 통합으로 개편된 Docker 컨테이너\n\n* 최신 DevDocs 기능과 최적화를 통합하도록 Docker 이미지를 업데이트합니다.\n* API 엔드포인트를 보호하려면 API 토큰( `CRAWL4AI_API_TOKEN` )에 대한 환경 변수를 포함합니다.\n* 성능을 최적화하려면 적절한 메모리 한도와 리소스 제약 조건을 설정합니다.\n\n***\n\n### 4. 다중 OS Docker 인스턴스 지원\n\n* 다양한 아키텍처(예: `x86_64` , `ARM` )에 대한 Docker 이미지를 만들어 광범위한 시스템을 지원합니다.\n* 여러 OS 환경에서 이미지를 빌드하고 테스트하기 위해 CI/CD 파이프라인을 구현하여 호환성과 안정성을 보장합니다.\n\n***\n\n### 5. 메모리 적응형 크롤링\n\n* DevDocs의 `MemoryAdaptiveDispatcher` 통합하여 시스템 메모리 가용성에 따라 동시성을 동적으로 조정합니다.\n* 타겟 웹사이트에 과부하가 걸리는 것을 방지하고 메모리 부족 오류를 피하기 위해 내장된 속도 제한 기능을 구현합니다.\n\n***\n\n### 6. UI에서 PDF 업로드 및 추출\n\n* DevDocs의 기능을 활용하여 페이지를 PDF로 내보내고( `pdf=True` ) 해당 페이지에서 콘텐츠를 추출합니다.\n* PDF 업로드를 처리하고, 추출된 콘텐츠를 표시하고, 사용자가 데이터와 상호 작용할 수 있도록 프런트엔드 구성요소를 개발합니다.\n\n***\n\n### 7. 영구 저장소와 향상된 UX를 갖춘 호스팅 환경\n\n* 세션 전반에 걸쳐 데이터를 비공개로 저장하고 결과를 크롤링하고 구성하기 위해 BYO 데이터베이스 솔루션을 구현합니다.\n* 사용자가 크롤링을 관리하고, 결과를 보고, 설정을 구성할 수 있도록 직관적인 대시보드와 인터페이스를 디자인합니다.\n* 다양한 브라우저에서 반응형 디자인과 접근성을 보장합니다.\n\n## 스타 역사\n\n[![별 역사 차트](https://api.star-history.com/svg?repos=cyberagiinc/DevDocs\\&type=Timeline)](https://star-history.com/#cyberagiinc/DevDocs\\&Timeline)","Korean","ko-KR",{"_36":69,"_40":73,"_45":74},{"_38":70,"_40":71,"_42":72},"与 Claude 集成，实现文档数据的智能查询，将抓取的技术文档转换为 LLM 可以直接交互的可操作资源。","DevDocs MCP 服务器","# CyberAGI 的 DevDocs 🚀\n\n## 🚀 技术合作伙伴\n\n## 🎯 非常适合\n\n### 🏢 企业软件开发人员\n\n无需花费数周时间阅读文档并处理技术债务。DevDocs 可帮助您快速实施任何技术，轻松理解文档。\n\n### 🕸️ 网络爬虫\n\n使用智能发现子 URL 功能提取网站的全部内容，最高可达 5 级。非常适合通过智能抓取来获取内部和外部网站文档。\n\n### 👥 开发团队\n\n利用内置 MCP 服务器和 Claude 集成的内部文档进行智能数据查询。将团队的知识库转化为可操作的资源。\n\n### 🚀 独立黑客\n\nDevDocs + VSCode(cline) + 你的想法 = 使用任何技术快速交付产品。构建下一个重大项目时，无需再受困于文档的泥潭。\n\n## ✨ 特点\n\n### 🧠 智能爬取\n\n* **智能深度控制**：选择 1-5 级爬行深度\n* **自动链接发现**：查找并分类所有相关内容\n* **选择性抓取**：准确选择您想要提取的内容\n* **儿童网址检测**：自动发现并映射网站结构\n\n### ⚡ 性能与速度\n\n* **并行处理**：同时抓取多个页面\n* **智能缓存**：不再浪费时间在重复内容上\n* **延迟加载支持**：轻松处理现代 Web 应用程序\n* **速率限制**：合理的爬取，不会造成服务器过载\n\n### 🎯 内容处理\n\n* **干净提取**：获取无意义的内容\n* **多种格式**：导出为 MD 或 JSON 进行 LLM 微调\n* **结构化输出**：逻辑组织的内容\n* **MCP 服务器集成**：为 AI 处理做好准备\n\n### 🛡️ 企业功能\n\n* **错误恢复**：失败时自动重试\n* **完整日志记录**：跟踪每个操作\n* **API 访问**：与您的工具集成\n* **团队管理**：多个席位和角色\n\n## 🤔 为什么选择 DevDocs？\n\n### 问题\n\n文档随处可见，而法学硕士（LLM）的知识体系已经过时了。即使对于高级工程师来说，阅读、理解和实施这些知识体系也需要数周的研究和开发时间。而**我们则将这个时间缩短到了几个小时。**\n\n### 我们的解决方案\n\nDevDocs 为您提供文档。将其指向任何技术文档 URL，即可看到：\n\n1. 发现与该技术相关的所有页面\n2. 提取有意义的内容，不要废话\n3. 在 MCP 服务器内逻辑地组织信息，以供 LLM 查询\n4. 以干净、可搜索的 MD 或 JSON 格式呈现，用于微调 LLM 目的\n\n🔥 我们希望世界上任何人都有能力使用最前沿的 LLM 技术快速构建出令人惊叹的产品。\n\n## 💰 价格比较\n\n| 特征 | 开发文档 | 火爬 |\n| --------- | ------------------------ | ------- |\n| 免费套餐 | 无限页面 | 没有任何 |\n| 起始价格 | 永远免费 | 每月16美元 |\n| 企业计划 | 风俗 | 每月333美元 |\n| 爬行速度 | 1000/分钟 | 20次/分钟 |\n| 深度级别 | 最多 5 个 | 有限的 |\n| 团队席位 | 无限 | 1-5个座位 |\n| 导出格式 | 支持 MD、JSON、LLM 的 MCP 服务器 | 格式有限 |\n| API 访问 | 即将推出 | 有限的 |\n| 模型上下文协议集成 | ✅ | ❌ |\n| 支持 | 优先通过 Discord 提供 | 仅限标准 |\n| 自托管（免费使用） | ✅ | ❌ |\n\n## 🚀 入门\n\nDevDocs 的设计使其易于与 Docker 配合使用，新用户只需进行最少的设置。\n\n### 先决条件\n\n* 您的系统上安装了[Docker](https://docs.docker.com/get-docker/)\n* Git 用于克隆存储库\n\n### Docker 快速入门（推荐）\n\n对于 Mac/Linux 用户：\n\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# Configure environment variables\n# Copy the template file to .env\ncp .env.template .env\n\n# Ensure NEXT_PUBLIC_BACKEND_URL in .env is set correctly (e.g., http://localhost:24125)\n# This allows the frontend (running in your browser) to communicate with the backend service.\n\n\n# Start all services using Docker\n./docker-start.sh\n```\n\n对于 Windows 用户：仅实验性（尚未测试）\n\n```cmd\n# Clone the repository\ngit clone https://github.com/cyberagiinc/DevDocs.git\n\n# Navigate to the project directory\n\ncd DevDocs\n\n# Configure environment variables\n# Copy the template file to .env\n\ncopy .env.template .env\n\n# Ensure NEXT_PUBLIC_BACKEND_URL in .env is set correctly (e.g., http://localhost:24125)\n\n# This allows the frontend (running in your browser) to communicate with the backend service.\n\n# Prerequisites: Install WSL 2 and Docker Desktop\n# Docker Desktop for Windows requires WSL 2. Please ensure you have WSL 2 installed and running first.\n# 1. Install WSL 2: Follow the official Microsoft guide: https://learn.microsoft.com/en-us/windows/wsl/install\n# 2. Install Docker Desktop for Windows: Download and install from the official Docker website. Docker Desktop includes Docker Compose.\n\n\n\n# Start all services using Docker\ndocker-start.bat\n```\n\n> 如果遇到权限问题，您可能需要以管理员身份运行该脚本，或手动设置 logs、storage 和 crawl\\_results 目录的权限。该脚本使用`icacls`命令设置权限，这在某些 Windows 系统上可能需要提升权限。\n>\n> **在 Windows 上手动设置权限**：\n>\n> 如果您需要手动设置权限，则可以使用 Windows GUI 或命令行进行设置：\n>\n> **使用Windows资源管理器**：\n>\n> 1. 右键单击每个目录（logs、storage、crawl\\_results）\n> 2. 选择“属性”\n> 3. 转到“安全”选项卡\n> 4. 点击“编辑”更改权限\n> 5. 点击“添加”添加用户/组\n> 6. 输入“Everyone”并点击“检查姓名”\n> 7. 点击“确定”\n> 8. 在列表中选择“所有人”\n> 9. 勾选“允许”下的“完全控制”\n> 10. 点击“应用”和“确定”\n>\n> **使用命令提示符（以管理员身份）** ：\n>\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\n> 如果您遇到 docker-compose.yml 文件的问题（例如“顶级对象必须是映射”错误）， `docker-start.bat`脚本会自动修复此问题，方法是确保文件具有正确的格式和编码。每次运行脚本时都会应用此修复，因此您无需手动修改文件。\n\n此命令将：\n\n1. 创建所有必要的目录\n2. 设置适当的权限\n3. 构建并启动所有 Docker 容器\n4. 监控服务以确保其正常运行\n\n### 访问 DevDocs\n\n服务运行后：\n\n* 前端用户界面： \n* 后端 API： \n* Crawl4AI服务： \n\n### 日志和监控\n\n使用 Docker 时，可以访问日志：\n\n1. **容器日志**（建议用于调试）：\n\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\n要停止所有服务，请在运行 docker-start 的终端中按`Ctrl+C` 。\n\n## 📜 脚本及其用途\n\nDevDocs 包含各种实用脚本，可帮助进行开发、测试和维护。以下是快速参考：\n\n### 启动脚本\n\n* `start.sh` / `start.bat` / `start.ps1` - 启动本地开发的所有服务（前端、后端、MCP）。\n* `docker-start.sh` / `docker-start.bat` - 使用 Docker 容器启动所有服务。\n\n### MCP 服务器脚本\n\n* `check_mcp_health.sh` - 验证 MCP 服务器的健康和配置状态。\n* `restart_and_test_mcp.sh` - 使用更新的 MCP 配置重新启动 Docker 容器并测试连接性。\n\n### Crawl4AI脚本\n\n* `check_crawl4ai.sh` - 检查 Crawl4AI 服务的状态和健康状况。\n* `debug_crawl4ai.sh` - 在调试模式下运行 Crawl4AI，并使用详细日志记录进行故障排除。\n* `test_crawl4ai.py` - 针对 Crawl4AI 服务运行测试以验证功能。\n* `test_from_container.sh` - 在 Docker 容器内测试 Crawl4AI 服务。\n\n### 实用程序脚本\n\n* `view_result.sh` - 以格式化的视图显示抓取结果。\n* `find_empty_folders.sh` - 识别项目结构中的空目录。\n* `analyze_empty_folders.sh` - 分析空文件夹并按风险级别对其进行分类。\n* `verify_reorganization.sh` - 验证代码重组是否成功。\n\n这些脚本组织在以下目录中：\n\n* 根目录：常用操作的主要脚本\n* `scripts/general/` ：通用实用程序脚本\n* `scripts/docker/` ：Docker 特定的脚本\n* `scripts/mcp/` ：MCP 服务器管理脚本\n* `scripts/test/` ：测试和验证脚本\n\n## 🌍 由开发人员为开发人员构建\n\nDevDocs 不仅仅是一个工具，它还是您的文档伴侣：\n\n* **节省时间**：将数周的研究缩短为数小时\n* **提高理解力**：获得清晰、有条理的文档\n* **支持创新**：利用任何技术更快地构建\n* **支持团队**：高效共享知识\n* **LLM 就绪**：现代时代需要现代解决方案，使用带有 LLM 的 Devdocs 极其简单直观。只需极少的配置，即可运行 Devdocs 和 Claude App，并识别 DevDocs 的 MCP 服务器，随时可以与您的数据进行交互。\n\n## 🛠️ 设置 Cline/Roo Cline 以实现快速软件开发。\n\n1. **打开“模式”界面**\n\n * 在**Roo Code**中，单击\\*\\*+\\*\\*以创建新的模式特定提示。\n2. **姓名**\n\n * 为模式**命名**（例如， `Research_MCP` ）。\n3. **角色定义提示**\n\n```\nExpertise and Personality: Expertise: Developer documentation retrieval, technical synthesis, and documentation search. Personality: Systematic, detail-oriented, and precise. Provide well-structured answers with clear references to documentation sections.\n\nBehavioral Mandate: Always use the Table Of Contents and Section Access tools when addressing any query regarding the MCP documentation. Maintain clarity, accuracy, and traceability in your responses.\n```\n\n4. **模式特定的自定义指令提示**\n\n```\n1. Table Of Contents Tool: Returns a full or filtered list of documentation topics. \n2. Section Access Tool: Retrieves the detailed content of specific documentation sections.\n\nGeneral Process: Query Interpretation: Parse the user's query to extract key topics, keywords, and context. Identify the likely relevant sections (e.g., API configurations, error handling) from the query.\n\nDiscovery via Table Of Contents: Use the Table Of Contents tool to search the documentation index for relevant sections. Filter or scan titles and metadata for matching keywords.\n\nDrill-Down Using Section Access: For each identified relevant document or section, use the Section Access tool to retrieve its content. If multiple parts are needed, request all related sections to ensure comprehensive coverage.\n\nSynthesis and Response Formation: Combine the retrieved content into a coherent and complete answer. Reference section identifiers or document paths for traceability. Validate that every aspect of the query has been addressed.\n\nError Handling: If no matching sections are found, adjust the search parameters and retry. Clearly report if the query remains ambiguous or if no relevant documentation is available.\n\nMandatory Tool Usage: \nEnforcement: Every time a query is received that requires information from the MCP server docs, the agent MUST first query the Table Of Contents tool to list potential relevant topics, then use the Section Access tool to retrieve the necessary detailed content.\n\nSearch & Retrieve Workflow: \nInterpret and Isolate: Identify the key terms and data points from the user's query.\n\nIndex Lookup: Immediately query the Table Of Contents tool to obtain a list of relevant documentation sections.\n\nTargeted Retrieval: For each promising section, use the Section Access tool to get complete content.\n\nInformation Synthesis: Merge the retrieved content, ensuring all necessary details are included and clearly referenced.\n\nFallback and Clarification: If initial searches yield insufficient data, adjust the query parameters and retrieve additional sections as needed.\n\nCustom Instruction Loading: Additional custom instructions specific to Research_MCP mode may be loaded from the .clinerules-research-mcp file in your workspace. These may include further refinements or constraints based on evolving documentation structures or query types.\n\nFinal Output Construction: The final answer should be organized, directly address the query, and include clear pointers (e.g., section names or identifiers) back to the MCP documentation. Ensure minimal redundancy while covering all necessary details.\n```\n\n## 🤝加入我们的社区\n\n* 🌟[在 GitHub 上为我们点赞](https://github.com/cyberagi/devdocs)\n* 👋🏽[在 Linkedin 上联系我们的创始人](https://www.linkedin.com/in/shubhamkhichi/)\n* 💬[加入我们的 Discord 社区](https://discord.gg/2594NueRg8)\n\n## 🏆 成功案例\n\nDevDocs 将我们原本 3 周的实施时间缩短到了 2 天。它不仅仅是一个爬虫，更是一个开发加速器。——*财富 100 强公司高级工程师*\n\n“通过使用 DevDocs 快速理解和实施新技术，我的 SaaS 上线时间缩短了一半。”——*成功的独立黑客*\n\n## 🛣️ DevDocs 路线图\n\n本路线图概述了我们由 Crawl4AI 提供支持的先进网络爬虫平台 DevDocs 即将推出的增强功能和特性。每一项改进都旨在充分利用 Crawl4AI 的功能，确保提供强大、高效且用户友好的网络爬虫体验。\n\n⸻\n\n### 1.增强动态内容爬虫逻辑\n\n* 实现`wait_for_images=True`以确保在提取之前所有图像都已完全加载。\n* 设置`scan_full_page=True`强制爬虫滚动整个页面，触发延迟加载内容。\n* 引入`scroll_delay`以在滚动步骤之间添加延迟，从而允许内容正确加载。\n* 结合`wait_for`参数来等待指示内容加载完成的特定 DOM 元素。\n\n***\n\n### 2. 使用浏览器池进行热加载\n\n* 实现预热浏览器实例池，以避免为每个任务启动新浏览器的开销。\n* 利用`use_persistent_context=True`跨任务维护会话数据，减少重复登录和设置的需要。\n\n***\n\n### 3. 改进的 Docker 容器，集成最新的 DevDocs\n\n* 更新 Docker 镜像以包含最新的 DevDocs 功能和优化。\n* 包括 API 令牌（ `CRAWL4AI_API_TOKEN` ）的环境变量以保护 API 端点。\n* 设置适当的内存限制和资源约束以优化性能。\n\n***\n\n### 4. 多操作系统 Docker 实例支持\n\n* 为不同的架构（例如`x86_64` 、 `ARM` ）创建 Docker 镜像，以支持各种系统。\n* 实施 CI/CD 管道以跨多个操作系统环境构建和测试图像，确保兼容性和稳定性。\n\n***\n\n### 5. 内存自适应爬行\n\n* 集成 DevDocs 的`MemoryAdaptiveDispatcher`以根据系统内存可用性动态调整并发性。\n* 实施内置速率限制，以防止目标网站不堪重负并避免内存不足错误。\n\n***\n\n### 6. UI 中的 PDF 上传和提取\n\n* 利用 DevDocs 的功能将页面导出为 PDF（ `pdf=True` ）并从中提取内容。\n* 开发前端组件来处理 PDF 上传、显示提取的内容并允许用户与数据交互。\n\n***\n\n### 7. 具有持久存储和增强用户体验的托管环境\n\n* 实施 BYO 数据库解决方案以私密存储数据、抓取结果以及跨会话配置。\n* 为用户设计直观的仪表板和界面来管理他们的爬网、查看结果和配置设置。\n* 确保响应式设计和跨各种浏览器的可访问性。\n\n## 星史\n\n[![星空历史图](https://api.star-history.com/svg?repos=cyberagiinc/DevDocs\\&type=Timeline)](https://star-history.com/#cyberagiinc/DevDocs\\&Timeline)","Chinese","zh-CN","githubUser","locale",{"_78":79,"_80":81,"_20":87,"_93":39,"_94":39,"_95":96,"_99":100,"_121":-5,"_23":122,"_123":124,"_125":126,"_40":41,"_151":112,"_152":-5,"_153":-5,"_154":-5,"_155":-5,"_156":157,"_162":-5,"_133":108,"_163":164,"_168":-5,"_8":169,"_170":171},"addedAt","2025-04-03T01:01:55.436436198Z","argumentsJsonSchema",{"_82":83,"_84":85,"_12":86},"properties",{},"required",[],"object",[88,89,90,91,92],"category:documentation-access","category:rag-systems","hosting:hybrid","language:typescript","license_grade:a","descriptionMarkdown","descriptionPlainText","githubProject",{"_42":43,"_97":98},"url","https://github.com/cyberagiinc/devdocs","githubRepository",{"_101":102,"_103":104,"_105":-5,"_106":107,"_40":108,"_109":110,"_114":115,"_116":117,"_119":120},"defaultBranch","feature-main","fullName","cyberagiinc/DevDocs","githubTreeId","language","TypeScript","DevDocs","owner",{"_111":112,"_8":113},"login","cyberagiinc","3X5m9Vs928","recentStargazers",45,"spdxLicense",{"_40":118},"Apache 2.0","stargazers",1569,"glamaJson",4893,"inspectable",false,"integrations",[127,137,144],{"_128":129,"_38":135,"_8":136},"brand",{"_130":131,"_40":132,"_133":134},"logoSvgPath","M20.317 4.3698a19.7913 19.7913 0 00-4.8851-1.5152.0741.0741 0 00-.0785.0371c-.211.3753-.4447.8648-.6083 1.2495-1.8447-.2762-3.68-.2762-5.4868 0-.1636-.3933-.4058-.8742-.6177-1.2495a.077.077 0 00-.0785-.037 19.7363 19.7363 0 00-4.8852 1.515.0699.0699 0 00-.0321.0277C.5334 9.0458-.319 13.5799.0992 18.0578a.0824.0824 0 00.0312.0561c2.0528 1.5076 4.0413 2.4228 5.9929 3.0294a.0777.0777 0 00.0842-.0276c.4616-.6304.8731-1.2952 1.226-1.9942a.076.076 0 00-.0416-.1057c-.6528-.2476-1.2743-.5495-1.8722-.8923a.077.077 0 01-.0076-.1277c.1258-.0943.2517-.1923.3718-.2914a.0743.0743 0 01.0776-.0105c3.9278 1.7933 8.18 1.7933 12.0614 0a.0739.0739 0 01.0785.0095c.1202.099.246.1981.3728.2924a.077.077 0 01-.0066.1276 12.2986 12.2986 0 01-1.873.8914.0766.0766 0 00-.0407.1067c.3604.698.7719 1.3628 1.225 1.9932a.076.076 0 00.0842.0286c1.961-.6067 3.9495-1.5219 6.0023-3.0294a.077.077 0 00.0313-.0552c.5004-5.177-.8382-9.6739-3.5485-13.6604a.061.061 0 00-.0312-.0286zM8.02 15.3312c-1.1825 0-2.1569-1.0857-2.1569-2.419 0-1.3332.9555-2.4189 2.157-2.4189 1.2108 0 2.1757 1.0952 2.1568 2.419 0 1.3332-.9555 2.4189-2.1569 2.4189zm7.9748 0c-1.1825 0-2.1569-1.0857-2.1569-2.419 0-1.3332.9554-2.4189 2.1569-2.4189 1.2108 0 2.1757 1.0952 2.1568 2.419 0 1.3332-.946 2.4189-2.1568 2.4189Z","Discord","slug","discord","Provides community support and priority assistance through the DevDocs Discord server","r6ex7r1ax4",{"_128":138,"_38":142,"_8":143},{"_130":139,"_40":140,"_133":141},"M13.983 11.078h2.119a.186.186 0 00.186-.185V9.006a.186.186 0 00-.186-.186h-2.119a.185.185 0 00-.185.185v1.888c0 .102.083.185.185.185m-2.954-5.43h2.118a.186.186 0 00.186-.186V3.574a.186.186 0 00-.186-.185h-2.118a.185.185 0 00-.185.185v1.888c0 .102.082.185.185.185m0 2.716h2.118a.187.187 0 00.186-.186V6.29a.186.186 0 00-.186-.185h-2.118a.185.185 0 00-.185.185v1.887c0 .102.082.185.185.186m-2.93 0h2.12a.186.186 0 00.184-.186V6.29a.185.185 0 00-.185-.185H8.1a.185.185 0 00-.185.185v1.887c0 .102.083.185.185.186m-2.964 0h2.119a.186.186 0 00.185-.186V6.29a.185.185 0 00-.185-.185H5.136a.186.186 0 00-.186.185v1.887c0 .102.084.185.186.186m5.893 2.715h2.118a.186.186 0 00.186-.185V9.006a.186.186 0 00-.186-.186h-2.118a.185.185 0 00-.185.185v1.888c0 .102.082.185.185.185m-2.93 0h2.12a.185.185 0 00.184-.185V9.006a.185.185 0 00-.184-.186h-2.12a.185.185 0 00-.184.185v1.888c0 .102.083.185.185.185m-2.964 0h2.119a.185.185 0 00.185-.185V9.006a.185.185 0 00-.184-.186h-2.12a.186.186 0 00-.186.186v1.887c0 .102.084.185.186.185m-2.92 0h2.12a.185.185 0 00.184-.185V9.006a.185.185 0 00-.184-.186h-2.12a.185.185 0 00-.184.185v1.888c0 .102.082.185.185.185M23.763 9.89c-.065-.051-.672-.51-1.954-.51-.338.001-.676.03-1.01.087-.248-1.7-1.653-2.53-1.716-2.566l-.344-.199-.226.327c-.284.438-.49.922-.612 1.43-.23.97-.09 1.882.403 2.661-.595.332-1.55.413-1.744.42H.751a.751.751 0 00-.75.748 11.376 11.376 0 00.692 4.062c.545 1.428 1.355 2.48 2.41 3.124 1.18.723 3.1 1.137 5.275 1.137.983.003 1.963-.086 2.93-.266a12.248 12.248 0 003.823-1.389c.98-.567 1.86-1.288 2.61-2.136 1.252-1.418 1.998-2.997 2.553-4.4h.221c1.372 0 2.215-.549 2.68-1.009.309-.293.55-.65.707-1.046l.098-.288Z","Docker","docker","Enables easy deployment and management of the DevDocs service using Docker containers, with scripts for startup, monitoring, and maintenance","zux57decci",{"_128":145,"_38":149,"_8":150},{"_130":146,"_40":147,"_133":148},"M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12","GitHub","github","Allows access to the DevDocs repository for contribution, with features for tracking star history and community engagement","fw1xe3aplz","namespace","npmPackage","prompts","redditPostForeignId","resources","scores",{"_158":159,"_160":-5,"_161":-5},"license",100,"quality","security","simpleIcon","supportedPlatforms",[165,166,167],"WINDOWS","MACOS","LINUX","tools","n7k2p9zf7s","updatedAt","2025-05-27T18:02:15.148148985Z","meta",[174,176,178,185,188,190,193,196,199,202,205,207,210,213,215,217,219,221,223],{"_10":175},"DevDocs MCP Server | Glama",{"_177":39,"_40":38},"content",{"_179":180,"_181":182,"_183":184},"href","https://glama.ai/mcp/servers/@cyberagiinc/DevDocs","rel","canonical","tagName","link",{"_177":41,"_186":187},"property","og:title",{"_177":39,"_186":189},"og:description",{"_177":191,"_186":192},"https://glama.ai/logo.png","og:logo",{"_177":194,"_186":195},"https://glama.ai/mcp/servers/@cyberagiinc/DevDocs/og-image","og:image",{"_177":197,"_186":198},"630","og:image:height",{"_177":200,"_186":201},"1200","og:image:width",{"_177":203,"_186":204},"website","og:type",{"_177":180,"_186":206},"og:url",{"_177":208,"_186":209},"Glama – MCP Hosting Platform","og:site_name",{"_177":211,"_40":212},"summary_large_image","twitter:card",{"_177":208,"_40":214},"twitter:title",{"_177":39,"_40":216},"twitter:description",{"_177":194,"_40":218},"twitter:image",{"_177":197,"_40":220},"twitter:image:height",{"_177":200,"_40":222},"twitter:image:width",{"_224":225},"script:ld+json",{"_226":227,"_228":229},"@context","http://schema.org","@graph",[230],{"_226":231,"_232":233,"_234":235},"https://schema.org","@type","BreadcrumbList","itemListElement",[236,243,247,251],{"_232":237,"_238":239,"_40":240,"_241":242},"ListItem","item","https://glama.ai/","Glama","position",1,{"_232":237,"_238":244,"_40":245,"_241":246},"https://glama.ai/mcp","MCP",2,{"_232":237,"_238":248,"_40":249,"_241":250},"https://glama.ai/mcp/servers","Servers",3,{"_232":237,"_238":180,"_40":41,"_241":252},4,"visitorIsMaintainer","routes/_public/mcp/servers/~namespace/~slug/_pages/reviews/_route",{"_75":-5,"_36":256,"_172":274,"_309":-5},{"_78":79,"_80":257,"_20":260,"_93":39,"_94":39,"_95":261,"_99":262,"_121":-5,"_23":122,"_123":124,"_125":265,"_40":41,"_151":112,"_152":-5,"_153":-5,"_154":-5,"_155":-5,"_156":272,"_162":-5,"_133":108,"_163":273,"_168":-5,"_8":169,"_170":171},{"_82":258,"_84":259,"_12":86},{},[],[88,89,90,91,92],{"_42":43,"_97":98},{"_101":102,"_103":104,"_105":-5,"_106":107,"_40":108,"_109":263,"_114":115,"_116":264,"_119":120},{"_111":112,"_8":113},{"_40":118},[266,268,270],{"_128":267,"_38":135,"_8":136},{"_130":131,"_40":132,"_133":134},{"_128":269,"_38":142,"_8":143},{"_130":139,"_40":140,"_133":141},{"_128":271,"_38":149,"_8":150},{"_130":146,"_40":147,"_133":148},{"_158":159,"_160":-5,"_161":-5},[165,166,167],[275,277,279,281,283,284,285,286,287,288,289,290,291,292,293,294,295,296,297],{"_10":276},"Reviews | DevDocs MCP Server | Glama",{"_177":278,"_40":38},"Read community reviews and feedback for DevDocs MCP Server. Discover user experiences, ratings, strengths, and potential limitations of this MCP implementation from actual users.",{"_179":280,"_181":182,"_183":184},"https://glama.ai/mcp/servers/@cyberagiinc/DevDocs/reviews",{"_177":282,"_186":187},"Reviews | DevDocs MCP Server",{"_177":278,"_186":189},{"_177":191,"_186":192},{"_177":194,"_186":195},{"_177":197,"_186":198},{"_177":200,"_186":201},{"_177":203,"_186":204},{"_177":280,"_186":206},{"_177":208,"_186":209},{"_177":211,"_40":212},{"_177":208,"_40":214},{"_177":278,"_40":216},{"_177":194,"_40":218},{"_177":197,"_40":220},{"_177":200,"_40":222},{"_224":298},{"_226":227,"_228":299},[300],{"_226":231,"_232":233,"_234":301},[302,303,304,305,306],{"_232":237,"_238":239,"_40":240,"_241":242},{"_232":237,"_238":244,"_40":245,"_241":246},{"_232":237,"_238":248,"_40":249,"_241":250},{"_232":237,"_238":180,"_40":41,"_241":252},{"_232":237,"_238":280,"_40":307,"_241":308},"Reviews",5,"review","actionData","errors"]

Rate & Review

MCP directory API