OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
MCP & Tooling

Devdocs

DevDocs is a UI-based MCP server that discovers and extracts technical documentation from web pages, organizes it for searching and assistant queries, and describes Markdown and JSON exports. Its repository identifies integrations with Cursor, Windsurf, Cline, Roo Code and Claude Desktop.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Devdocs — OpenViST project profile in MCP & Tooling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Consider DevDocs when you want to bring technical website documentation into an MCP-connected coding workflow and can work with the public repository's documented setup.

Who it is for

  • Developers who want technical documentation available within an MCP-connected coding assistant.
  • Teams looking to retrieve and organize documentation from technical websites.

Documented uses

  • Discover related pages starting from a technical documentation URL.
  • Extract and organize documentation content for assistant queries.
  • Access documentation through a named coding assistant's MCP integration.
Before you choose

Requirements & limits

The repository is public and lists an Apache-2.0 license. The README describes Docker setup for Mac and Linux; its Windows instructions are marked experimental and not tested.

  • The public version is described in the README as not publicly maintained.
  • The README documents Docker setup and requires Docker and Git.
  • The listed assistant integrations are Cursor, Windsurf, Cline, Roo Code and Claude Desktop.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Prepare DevDocs with Docker on Mac or Linux

Set up the repository and start its services using the README's Docker workflow.

Before you start

  • Docker installed
  • Git installed
  • A Mac or Linux environment

Steps

  1. Clone the DevDocs repository and change into its directory.

  2. Copy .env.template to .env.

  3. Set NEXT_PUBLIC_BACKEND_URL to the appropriate backend address, such as http://localhost:24125.

  4. Run ./docker-start.sh to start the services.

Expected outcome

The documented Docker startup process is initiated with the frontend configured to communicate with the backend.

Guide limitations

  • The README warns that the public version is not publicly maintained.
  • These are documented setup steps, not a claim of successful execution or verification.
Documentation 1 ↗
COMPARE OPTIONS

Compare options for AI coding assistance

These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.

ProjectDocumented purposePlatformAccess and requirements
DevdocsDiscover related pages starting from a technical documentation URL.DesktopThe repository is public and lists an Apache-2.0 license. The README describes Docker setup for Mac and Linux; its Windows instructions are marked experimental and not tested.
OvertureInspect a coding agent’s planned steps and branches before code is written.Self-hosted, Server, WebOpen-source software under the MIT license. The documented setup runs the MCP server locally and opens its web interface at `http://localhost:3031` by default.
WigoloSearch the web and fetch pages for an agent’s research task.CLI, Self-hosted, ServerThe quickstart lists macOS, Linux and Windows, and requires Node.js 20 or later with about 1.5 GB of free disk space. The repository labels the project public beta.
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
11 October 2026
Original website title
cyberagiinc/DevDocs · Official homepage title · retained in its source language
How we review sourcesSuggest a correction