Architecture
Canonical architecture for MCP-Crawl4AI
Architecture
MCP-Crawl4AI uses a single-module FastMCP server backed by one lifespan-managed AsyncWebCrawler.
Canonical tool surface: scrape, crawl, close_session, and get_artifact.
System Overview
Rendering diagram...
High-level architecture of MCP-Crawl4AI
Core Components
FastMCP v3 Server
Handles transport, MCP protocol plumbing, and registration for tools/resources/prompts.
Lifespan Manager
Initializes and tears down a shared AsyncWebCrawler once per server lifecycle.
Canonical Tool Surface
| Tool | Purpose |
|---|---|
scrape | Canonical single/batch page scraping envelope |
crawl | Canonical list/deep traversal envelope |
close_session | Explicit session shutdown |
get_artifact | Artifact retrieval for captured runs |
Resource Surface
| Resource URI | Description |
|---|---|
config://server | Server configuration, capabilities, and tool inventory |
crawl4ai://version | Server, crawl4ai, and fastmcp versions |
Data Flow
Rendering diagram...
Canonical scrape/crawl execution flow
Found an issue with this page? Submit a GitHub issue