MCP Server ยท Claude Desktop ยท Claude Code ยท GitHub Copilot
โญ 600+ developers installed

Docs that
never go stale

AI-powered documentation health monitor.
Detects stale code comments and suggests updates using Claude.

Get Started View on GitHub
NuGetLivingDocs.Mcp issuesopen licenseMIT
livingdocs-mcp โ€” bash
$ livingdocs-mcp scan /path/to/your/repo
 
Scanning /path/to/repo ...
Files examined : 12
Stale docs : 2
 
[โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ] 100% src/Tax.cs
doc updated : 2024-09-01
code changed: 2025-01-15
 
[โ–ˆโ–ˆโ–ˆโ–ˆโ–‘โ–‘โ–‘โ–‘โ–‘โ–‘] 40% src/Auth.cs
doc updated : 2024-12-01
code changed: 2025-01-28

Everything you need
to keep docs healthy

Three free tools, two powerful Pro capabilities. Plug into your workflow via MCP.

Free
scan_repo

Scan a repo and list stale doc files with staleness percentage from 0โ€“100%. Know exactly where rot lives.

Free
query_docs

Answer natural-language questions about your codebase using its doc comments. Ask Claude what a module does.

Free
suggest_doc_update

Ask Claude to rewrite a stale doc comment with an updated, accurate description based on the current code.

Pro
sync_confluence

Write updated docs back to Confluence pages automatically. Creates pages if they don't exist.

Pro
scan_org

Scan all repos in a GitHub org and return an org-wide staleness report. Track documentation health at scale.

Pro
write_docs

Write Claude-generated docs to docs/<File>.md with a UTC timestamp on every run. Builds a full audit trail of doc history inside your repo.

From stale to sharp
in three steps

01
Install & connect

Install via dotnet tool install. Add your MCP config to Claude Desktop, Claude Code, or VS Code. Takes under 2 minutes.

02
Scan for staleness

LivingDocs compares when doc comments were last updated vs when code changed. Returns a staleness score per file.

03
Claude writes the fix

Ask Claude to suggest or directly apply doc updates. It reads the current code and rewrites comments to match reality.

Up and running
in minutes

Requires .NET 10 SDK. Install globally via NuGet, then configure once for your tools.

Global Install
Claude Desktop
Claude Code
VS Copilot
# Install globally via NuGet
$ dotnet tool install -g LivingDocs.Mcp
 
# Quick scan test
$ livingdocs-mcp scan /path/to/your/repo
# ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"livingdocs": {
"command": "livingdocs-mcp",
"env": { "ANTHROPIC_API_KEY": "sk-ant-..." }
}
}
}
# Register globally:
$ claude mcp add livingdocs -s user -- livingdocs-mcp
 
# Then chat naturally:
scan this repo for stale docs
what does the Auth module do?
suggest a fix for src/Tax.cs
# Add .vscode/mcp.json to your project (VS Code 1.99+)
{
"servers": {
"livingdocs": {
"type": "stdio",
"command": "livingdocs-mcp"
}
}
}
 
# Open Copilot chat โ†’ switch to Agent mode โ†’ tools available

Works where
you already work

๐Ÿค–
Claude Desktop

Add livingdocs as an MCP server. Scan, query, and update docs from the Claude chat interface.

โŒจ๏ธ
Claude Code

Register globally or per-project. LivingDocs tools appear in your Claude Code chat context.

๐Ÿ› ๏ธ
GitHub Copilot

VS Code 1.99+ agent mode support. Drop in a .vscode/mcp.json and all tools are available.

๐Ÿ“„
Confluence Pro

Automatically sync updated docs to Confluence pages. Creates pages that don't yet exist.

๐Ÿ—‚๏ธ
Git Repo Pro

Write Claude-generated docs to docs/<File>.md inside your repo. Timestamped on every run โ€” no external tools needed.

Scans across 5 languages

โ—† C#
โ—† TypeScript
โ—† JavaScript
โ—† Python
โ—† Go

Simple, transparent pricing

Start free. Upgrade when you need more.

Free
$0
forever

For individual developers who want to keep their docs healthy.

Scan repo for stale docs
Query docs with natural language
Claude-powered doc suggestions
C#, TypeScript, JS, Python, Go
Install Free โ†’
Enterprise
Custom
annual or one-time

For large teams needing air-gapped deployments and bring-your-own LLM.

Everything in Pro
Offline license โ€” no internet required
Azure OpenAI / on-prem LLM support
Self-contained binary (no .NET SDK)
Priority support & custom invoicing
Contact Us โ†’

SLA & Support

Response times

  • Bug reports โ€” acknowledged within 48 hours
  • Security issues โ€” acknowledged within 24 hours
  • Feature requests โ€” reviewed within 5 business days
  • Enterprise support โ€” priority response within 12 hours

Support channels

Uptime

  • LivingDocs runs as a local MCP server โ€” no hosted infrastructure, no downtime dependency
  • NuGet package availability follows NuGet.org SLA

Last updated: 2026-05-19 ยท Novaders LLP