1. Conduid
  2. Developer Tools
  3. server
MCP server · Developer Tools

server

Open-source engine for turning documentation sites into searchable, MCP-accessible context for humans and coding agents.

39Low

Scored 17 days ago · breakdown

About server

server is an MCP server published by git+Amal-David in the Developer Tools category: open-source engine for turning documentation sites into searchable, MCP-accessible context for humans and coding agents.

The repository has 19 stars and 0 forks.

Install

Install
npx @docingest/mcp-server
Claude Code
claude mcp add docingest -- npx -y @docingest/mcp-server
npx
npx -y @docingest/mcp-server

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about server

Powered by Claude · Grounded in docs

I know everything about server. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

4 checks have not been run yet.

README

DocIngest

DocIngest is the open-source engine for turning documentation sites into searchable, MCP-accessible context for humans and coding agents.

It crawls docs, stores them as clean markdown, indexes them for search, and exposes the same corpus through a web UI, CLI, and MCP server. Use it to build a public docs index, self-host an internal corpus, or give coding agents fresher documentation context.

Quick Start • MCP + CLI • Screenshots • Setup Docs • Contributing

Status

What works today

  • ✅ Index documentation sites from the web UI
  • ✅ Browse and search indexed docs at docingest.com
  • ✅ Open docs by domain, copy markdown, and download stored docs
  • ✅ Re-index sources when upstream docs change
  • ✅ Query docs from MCP-compatible coding tools
  • ✅ Use the package as a lightweight CLI for quick lookup

Hosted corpus

  • 📚 The live main deployment currently serves 1,512 latest documentation sites on docingest.com as of April 24, 2026
  • 🗂️ DocIngest stores versioned snapshots per domain, so one docs site can have multiple historical versions behind the scenes
  • ℹ️ The Git repository does not commit the full hosted corpus; the deployed service holds the actual indexed docs data

Still early

  • 🧪 Search/ranking works, but needs deeper tuning
  • 🧪 Loading, empty, and success states need more polish
  • 🧪 Version-aware storage exists, but the product UX around versions is still early
  • ❌ Not yet a mature enterprise docs platform with permissions, collaboration, and admin workflows

Screenshots

Homepage

DocIngest homepage

Index a docs site

DocIngest indexing flow

MCP setup guide

DocIngest MCP guide

Quick Start

Prerequisites

  • Node.js 18+ or Bun
  • Firecrawl, hosted or self-hosted
  • Redis for fast autocomplete/search

Redis is optional for tiny local tests, but recommended for anything serious.

Install

git clone https://github.com/Amal-David/docingest.git
cd docingest
npm install
cd server && npm install && cd ..

Configure

Create .env in the repo root:

CRAWL_PROVIDER=firecrawl
FIRECRAWL_API_KEY=fc-your-api-key-here
FIRECRAWL_API_URL=https://api.firecrawl.dev/v1
REACT_APP_API_URL=http://localhost:8001/api
REDIS_HOST=localhost
REDIS_PORT=6380

For local Docker with self-hosted Firecrawl:

CRAWL_PROVIDER=firecrawl
FIRECRAWL_API_URL=http://localhost:3002/v1
REACT_APP_API_URL=http://localhost:8001/api
REDIS_HOST=localhost
REDIS_PORT=6380

For setup details, use these guides:

Run

Choose the local services you want:

Run everything local:

docker compose --profile firecrawl --profile tools up -d

Run only Redis:

docker compose up -d redis

Run Redis and Firecrawl without the Redis UI:

docker compose --profile firecrawl up -d

Run Redis with the Redis UI:

docker compose --profile tools up -d

Run the app locally:

npm run dev

If port 8001 is already busy, use the alternate local API port:

npm run dev:local

Then open http://localhost:8000.

After indexing docs, build the Redis search index:

cd server
npm run build-index

MCP + CLI

Add DocIngest to Claude Code:

claude mcp add docingest -- npx -y @docingest/mcp-server

Use the same package as a CLI:

npx @docingest/mcp-server find react
npx @docingest/mcp-server read react.dev --topic hooks --max-tokens 5000
npx @docingest/mcp-server search "server components" --limit 5

MCP tools:

  • find-docs finds a library or docs domain
  • read-docs fetches focused documentation content
  • query-docs searches across indexed docs

For editor-specific config, see the MCP server README.

Setup Docs

Use these when you need more than the happy path:

Tech Stack

  • React + TypeScript + Tailwind CSS
  • Node.js + Express + TypeScript
  • Firecrawl for crawling
  • Redis for autocomplete, full-text search, and cached docs
  • File-based markdown storage

Contributing

Contributions are welcome, especially around crawling quality, search/ranking, MCP ergonomics, docs UX, and self-hosting.

License

MIT

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About server

How do I install server?

Run npx @docingest/mcp-server, then add the server to your MCP client's configuration.

Is server safe to use with an AI agent?

Its trust score is 39 out of 100 (low). It passes 1 of the 2 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is server still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.