Doc Monitor MCP

Doc Monitor MCP

Enables AI agents to monitor web documentation for changes, perform semantic search with RAG, and analyze breaking changes in APIs.

Category
访问服务器

README

<h1 align="center">Doc Monitor MCP</h1>

Advanced Documentation Monitoring & RAG Server for AI Agents


doc-monitor is an intelligent Model Context Protocol (MCP) server that continuously monitors documentation, detects changes, and provides advanced Retrieval Augmented Generation (RAG) capabilities for AI agents and coding assistants. It automatically crawls web documentation, tracks versions, analyzes change impact, and maintains a searchable knowledge base to help developers stay current with evolving APIs and documentation.

🚀 Key Features

  • 🔍 Smart Documentation Monitoring: Continuously track documentation changes and analyze their impact
  • 📊 Version Control: Automatic versioning of documentation with detailed change tracking
  • 🧠 Impact Analysis: AI-powered analysis of breaking changes and API modifications
  • 🌐 Multi-Format Support: Handle web pages, sitemaps, OpenAPI specs, and text files
  • ⚡ High-Performance Crawling: Parallel processing with memory-adaptive dispatching
  • 🎯 Semantic Search: Vector-based RAG queries with advanced filtering
  • 🔧 MCP Integration: Standards-compliant Model Context Protocol server
  • 🐳 Production Ready: Docker support with comprehensive database schema

🏗️ Architecture

Core Technologies:

  • Python 3.12+ with asyncio for high-performance concurrent operations
  • Crawl4AI for intelligent web crawling and content extraction
  • Supabase with pgvector for vector storage and semantic search
  • OpenAI Embeddings (text-embedding-3-small) for content vectorization
  • FastMCP for Model Context Protocol server implementation

Database Schema:

  • crawled_pages: Document chunks with version tracking and vector embeddings
  • document_changes: Detailed change history with impact analysis
  • monitored_documentations: Active monitoring configuration and metadata

📦 Installation

Docker (Recommended)

git clone https://github.com/iamakash-06/doc-monitor.git
cd doc-monitor
docker build -t doc-monitor .

Local Development

git clone https://github.com/iamakash-06/Doc-Monitor-MCP.git
cd Doc-Monitor-MCP
pip install uv
uv venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate
uv pip install -e .

⚙️ Configuration

Create a .env file in the project root:

# Server Configuration
HOST=0.0.0.0
PORT=8051
TRANSPORT=sse

# OpenAI API
OPENAI_API_KEY=your_openai_api_key

# Supabase Database
SUPABASE_URL=your_supabase_project_url
SUPABASE_SERVICE_KEY=your_supabase_service_key

# Optional: Contextual Embeddings (requires additional OpenAI model access)
MODEL_CHOICE=gpt-4o-mini

🗄️ Database Setup

  1. Create a new Supabase project at supabase.com
  2. Navigate to the SQL Editor in your dashboard
  3. Execute the complete SQL schema from crawled_pages.sql:
# Copy the entire contents of crawled_pages.sql and run in Supabase SQL Editor

This creates the required tables, indexes, functions, and RLS policies.

▶️ Running the Server

Docker

docker run --env-file .env -p 8051:8051 doc-monitor

Local

uv run src/doc_fetcher_mcp.py

The server will start and be available at http://localhost:8051 (SSE) or via stdio transport.

🛠️ MCP Tools API Reference

Documentation Monitoring

monitor_documentation

Start monitoring a documentation URL with automatic change detection.

{
  "name": "monitor_documentation",
  "arguments": {
    "url": "https://api.example.com/docs",
    "notes": "Critical API documentation - monitor for breaking changes"
  }
}

Supported URL Types:

  • Regular web pages (with recursive internal link crawling)
  • Sitemaps (XML format)
  • OpenAPI specifications (JSON/YAML)
  • Text/Markdown files

check_document_changes

Check a specific URL for changes and update the knowledge base.

{
  "name": "check_document_changes", 
  "arguments": {
    "url": "https://api.example.com/docs"
  }
}

check_all_document_changes

Scan all monitored documentation for changes.

{
  "name": "check_all_document_changes",
  "arguments": {}
}

Search & Retrieval

perform_rag_query

Semantic search across all documentation with optional filtering.

{
  "name": "perform_rag_query",
  "arguments": {
    "query": "How to authenticate API requests",
    "source": "api.example.com",
    "match_count": 10,
    "endpoint": "/auth",
    "method": "POST"
  }
}

Management & Analytics

list_monitored_documentations

Get all actively monitored documentation sources.

get_available_sources

List all unique domains/sources in the knowledge base.

get_document_history

View complete change history for a specific URL.

delete_documentation_from_monitoring

Remove a URL from active monitoring.

🔌 Integration Examples

Claude Desktop (SSE Transport)

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "doc-monitor": {
      "transport": "sse",
      "url": "http://localhost:8051/sse"
    }
  }
}

Stdio Transport

{
  "mcpServers": {
    "doc-monitor": {
      "command": "uv",
      "args": ["run", "src/doc_fetcher_mcp.py"],
      "env": {
        "TRANSPORT": "stdio",
        "OPENAI_API_KEY": "your_openai_api_key", 
        "SUPABASE_URL": "your_supabase_url",
        "SUPABASE_SERVICE_KEY": "your_supabase_service_key"
      }
    }
  }
}

🎯 Use Cases

API Documentation Monitoring

# Monitor critical API documentation
monitor_documentation("https://api.stripe.com/docs")

# Check for breaking changes
check_document_changes("https://api.stripe.com/docs") 

# Search for specific functionality
perform_rag_query("payment methods", source="api.stripe.com")

Documentation Change Analysis

The system automatically:

  • 🔍 Detects Changes: Content additions, modifications, and deletions
  • 📈 Analyzes Impact: Identifies breaking changes and API modifications
  • 🚨 Provides Recommendations: Actionable insights for maintaining compatibility
  • 📋 Tracks History: Complete audit trail of all documentation evolution

🔧 Advanced Configuration

Memory and Performance

The server includes adaptive memory management:

CHUNK_SIZE = 5000          # Token limit per chunk
MAX_CONCURRENT = 10        # Parallel crawling limit  
MAX_DEPTH = 3             # Recursive crawling depth
MEMORY_THRESHOLD_PERCENT = 70.0  # Memory usage limit

Contextual Embeddings

Enable enhanced retrieval with contextual embeddings by setting MODEL_CHOICE:

MODEL_CHOICE= text-embedding-3-large # Enables context-aware chunk processing

📄 License

MIT License - see LICENSE for details.

🆘 Support


doc-monitor — Intelligent documentation monitoring and RAG for the AI-powered development workflow.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选