📡 MCP Radar

DuvInc/duvlify

Beautiful docs for humans. Native tools for agents. An open-source Astro framework for documentation you own end to end: Markdown in, static site with search, an API reference and an MCP server out.

12 stars
1 forks
TypeScript
momentum ▲ 26.0
created 2026-08-14
on radar since 2026-08-19
star trend 8 → 12 since 2026-08-19
astrocloudflare-workersdocs-as-codedocumentationmcpmodel-context-protocolopenapistatic-site-generator
View on GitHub ↗Homepage ↗

About duvlify

Beautiful docs for humans. Native tools for agents.

A documentation framework you own end to end: write Markdown, get a fast static site with search, an API reference, generated share cards, and a Model Context Protocol server that lets AI agents query your docs directly.

Built on Astro. No framework runtime in the browser, no hosted service in the middle, no per-seat pricing, and no watermark on your pages. The output is HTML.

duvlify.dev: the documentation, built with Duvlify from the content/ folder of this repository.

A fresh clone runs with nothing configured. Search works, the agent tools answer, and npm test passes, because every service integration defaults to off and retrieval falls back to an index built at compile time.

content/ is this project's own documentation. It is what duvlify.dev serves, and it doubles as a live demo of every component. Replace it with your pages.

handbook/ is the copy that survives step 1 of Making it yours. Replacing content/ deletes this framework's own documentation from your repository, and the links in the table below point at duvlify.dev, a host you do not control, describing a version you have not forked. handbook/ holds the same pages as plain Markdown, snapshotted from the build, so the manual stays in your clone.

Once content/ is yours, treat handbook/ as frozen. It is the manual for the commit you started from, and it stays correct however far your own pages move from it. Nothing reads it: no build step, no test, no route. So delete it when you no longer need it. What you must not do is regenerate it: that rebuilds it f

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/DuvInc--duvlify.html)

Related MCP servers

bkspace/starlight-mcp

MCP server for your Astro/Starlight docs — search_docs, get_doc, list_docs over stateless streamable HTTP. Astro integration + pure handler + Cloudflare glue.

⭐ 8TypeScript
Arshdeep54/huell

Self-hosted, git-connected docs platform — push to deploy, docs.json + MDX, with a CLI and MCP server for AI-agent-native authoring.

⭐ 3TypeScript
ForkPoint/agent-lighthouse

Lighthouse-style audits for AI-agent readiness, LLM crawlers, MCP clients, and the agentic web

⭐ 16TypeScript
Trainspotting31/memory-buddy

Shared memory layer for AI agents. Deploy once, connect Hermes/Trae/Cursor/Claude Desktop via MCP - they all share one memory. $0/month on Cloudflare free tier.

⭐ 10TypeScript
do-md/homekb

Local-first personal Markdown knowledge base with semantic search, AI Q&A, MCP, desktop/web clients, and a self-hostable zero-data-at-rest relay.

⭐ 6TypeScript
leynier/exeora

Secure execution for AI agents, on any machine. Connect any MCP client to the development environment on any machine you can run a command on (even your own laptop) - no open ports, no tunnels, and yo

⭐ 6TypeScript

📬 Get the weekly radar in your inbox

The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.