MCP server
The Consuela MCP server exposes 16 tools over the Model Context Protocol, giving AI assistants direct access to crawl sessions, page-level findings, redirect analysis, and on-demand crawls. It reads from the same SQLite database the desktop app writes, so any session you have already recorded is available immediately.
Setup
The MCP server supports two transports. Stdio runs the
consuela-mcp binary directly — most desktop
clients, including Claude Desktop, use this mode. Streamable
HTTP connects to the API server at POST /mcp,
useful when the crawler runs on a remote host or inside the hosted tier.
Stdio transport
Point CONSUELA_DB at a crawl database and start
the binary:
CONSUELA_DB=/path/to/crawls.db consuela-mcp To register it with Claude Desktop in one step:
claude mcp add consuela /path/to/consuela-mcp Streamable HTTP transport
When the API server is running, the MCP endpoint is available at
POST /mcp. If the server requires authentication,
set CONSUELA_MCP_TOKEN in the client's environment
to pass a bearer token with each request.
Session tools
Session tools list and inspect the crawl sessions stored in the database.
Every crawl — whether started from the desktop app, the CLI, or the
crawl_site tool below — creates a session.
Page tools
Page tools query individual page records within a session, filter by status or URL pattern, and surface broken links and missing image alt text.
Analysis tools
Analysis tools run higher-level inspections over an entire session — redirect health, chain depth, and headless-rendering diagnostics.
Crawl tools
Crawl tools let an AI assistant start a crawl directly, without switching to the desktop app or CLI. Single-page fetches return results inline; full site crawls persist to the database as a new session.
Host tools
Host tools inspect the system's host-file configuration, which can affect how crawled URLs resolve.