Practical overview
When it fits
Use Hound when an MCP-compatible client needs web retrieval tools available within an agent workflow, especially when the workflow combines search with fetching or crawling, or needs to read PDFs.
Who it is for
- People configuring an MCP-compatible AI assistant to retrieve web content during agent workflows.
- Developers who want to run web research tools locally or deploy an HTTP MCP service with Docker.
- Teams building agent workflows that need page crawling or PDF text extraction.
Documented uses
- Search the web and return ranked results to an AI agent.
- Fetch a URL, extract readable page content, or capture a screenshot.
- Crawl pages within a domain and return page content as Markdown.
- Extract text from PDFs, including scanned documents through OCR.
Requirements & limits
The repository documents a pip installation, a Docker deployment, and MIT licensing. Its README describes keyless search and separately supports adding keys for named search providers.
- The primary interface is an MCP server, so an MCP-compatible client is needed to use its tools.
- The full setup installs Chromium through Playwright; the documented lean package omits browser dependencies and runs in HTTP-only mode with reduced capability.
- Docker Compose provides an HTTP MCP endpoint for clients that support HTTP transport.
- Search can use documented keyless local engines or configured provider keys.
- The project documents bot-protection handling, but retrieval from a protected site is not guaranteed.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install Hound for a local MCP client
Install the full browser-enabled Hound package before connecting an MCP client.
Before you start
- Python and pip
- Playwright and Chromium installation support
Steps
Install the package with the command below.
pip install hound-mcp[all]Install Chromium with
playwright install chromium.Point an MCP client at the
houndcommand.
Expected outcome
The MCP client is configured to connect to the locally installed Hound command.
Guide limitations
- This guide covers installation and connection configuration, not a verified client workflow.
- Browser-based retrieval requires the documented browser setup.
Start Hound as an HTTP MCP service with Docker Compose
Launch the documented Docker Compose deployment and identify its MCP endpoint.
Before you start
- Docker and Docker Compose
- A host address reachable by the MCP client
Steps
Clone the Hound repository.
Change into the
master-fetchdirectory.Run
docker-compose up -d.Configure an HTTP-capable MCP client to use
http://:8765/mcp, or localhost when connecting on the same machine.
Expected outcome
Hound is configured as an HTTP MCP server at the documented endpoint.
Guide limitations
- The README identifies HTTP-capable clients as a requirement for this connection method.
- The documented steps do not establish that every deployment environment or client will work identically.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 12 October 2026
- Original website title
- dondai1234/master-fetch · Official homepage title · retained in its source language

