Unlock the knowledge trapped on your hard drive. Works with Claude Desktop, Claude Code, and the macOS menu bar.
Download punt-quarry.mcpb and double-click to install. Claude Desktop will prompt you for a data directory.
Attach a document to your conversation and ask Claude to index it:
"Index this report"
"What does it say about Q3 margins?"
That's it. Everything runs locally — no API keys, no cloud accounts. The embedding model (~500 MB) downloads automatically on first use.
curl -fsSL https://raw.githubusercontent.com/punt-labs/quarry/0cbb5e3/install.sh | shManual install (if you already have uv)
uv tool install punt-quarry
quarry install
quarry doctorVerify before running
curl -fsSL https://raw.githubusercontent.com/punt-labs/quarry/0cbb5e3/install.sh -o install.sh
shasum -a 256 install.sh
cat install.sh
sh install.shThen start using it:
quarry ingest-file notes.md # index a file
quarry search "my topic" # search by meaning, not keywordsIndex anything you have. PDFs, scanned documents, images, spreadsheets, presentations, source code, Markdown, LaTeX, DOCX, HTML, and webpages. Quarry reads each format the way you would and extracts the knowledge inside.
Search by meaning. "What did the Q3 report say about margins?" finds relevant passages even if they never use the word "margins." This is semantic search — it understands what you mean, not just what you typed.
Give your LLM access. As an MCP server, Quarry lets Claude Desktop and Claude Code search your indexed documents directly. Ask Claude about something in your files and it pulls the relevant context automatically.
Keep things organized. Named databases separate work from personal. Directory sync watches your folders and re-indexes when files change. Collections group documents within a database.
| Source | What happens |
|---|---|
| PDF (text pages) | Text extraction via PyMuPDF |
| PDF (image pages) | OCR (local by default; optional cloud backend) |
| Images (PNG, JPG, TIFF, BMP, WebP) | OCR (local by default; optional cloud backend) |
| Spreadsheets (XLSX, CSV) | Tabular serialization preserving structure |
| Presentations (PPTX) | Slide-per-chunk with tables and speaker notes |
| HTML / webpages | Boilerplate stripping, converted to Markdown |
| Text files (TXT, MD, LaTeX, DOCX) | Split by headings, sections, or paragraphs |
| Source code (30+ languages) | AST parsing into functions and classes |
The easiest way to install is the .mcpb file — download and double-click. Claude Desktop handles the rest.
Alternatively, quarry install (from the CLI) also configures Claude Desktop automatically.
Manual setup (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"quarry": {
"command": "/path/to/uvx",
"args": ["--from", "punt-quarry", "quarry", "mcp"]
}
}
}Use the absolute path to uvx (e.g. /opt/homebrew/bin/uvx). quarry install resolves this automatically.
Note: Uploaded files in Claude Desktop live in a sandbox that Quarry cannot access. Use ingest_content for uploaded content, or provide local file paths to ingest_file.
Quarry Menu Bar is a native macOS companion app that puts your knowledge base one click away. It sits in the menu bar and lets you search across all your indexed documents without switching apps.
- Semantic search with instant results
- Switch between named databases
- Syntax-highlighted results for code, Markdown, and prose
- Detail view with full page context
The app manages its own quarry serve process automatically — no manual server setup needed. Requires macOS 14 (Sonoma) or later and punt-quarry installed.
quarry install configures Claude Code automatically. To set up manually:
claude mcp add quarry -- uvx --from punt-quarry quarry mcpOnce configured, Claude Code can call these tools on your behalf:
| Tool | What it does |
|---|---|
search_documents |
Semantic search with optional filters |
ingest_file |
Index a file by path |
ingest_url |
Fetch and index a webpage |
ingest_content |
Index inline text (for uploads, clipboard, etc.) |
get_documents |
List indexed documents |
get_page |
Get raw text for a specific page |
delete_document |
Remove a document |
list_collections |
List collections |
delete_collection |
Remove a collection |
register_directory |
Register a directory for sync |
deregister_directory |
Remove a directory registration |
sync_all_registrations |
Re-index all registered directories |
list_registrations |
List registered directories |
list_databases |
List named databases |
use_database |
Switch to a different database |
status |
Database stats |
# Ingest
quarry ingest-file report.pdf # index a file
quarry ingest-file report.pdf --overwrite # replace existing data
quarry ingest-url https://example.com/page # index a webpage
# Search
quarry search "revenue trends" # semantic search
quarry search "revenue" --limit 5 # limit results
quarry search "tests" --page-type code # only code results
quarry search "revenue" --source-format .xlsx # only spreadsheet results
quarry search "deploy" --document README.md # search within one document
# Manage documents
quarry list # list indexed documents
quarry delete report.pdf # remove a document
quarry collections # list collections
# Directory sync
quarry register ~/Documents/notes # watch a directory
quarry sync # re-index all registered directories
quarry registrations # list registered directories
quarry deregister notes # stop watching
# System
quarry doctor # health check
quarry databases # list all databases with stats
quarry serve # start HTTP API serverKeep separate databases for different purposes:
quarry ingest-file report.pdf --db work
quarry ingest-file recipe.md --db personal
quarry search "revenue" --db work
quarry databases # list all databasesEach database is fully isolated — its own vector index and sync registry. The default database is called default.
You can point MCP servers at different databases:
{
"mcpServers": {
"work": {
"command": "/path/to/uvx",
"args": ["--from", "punt-quarry", "quarry", "mcp", "--db", "work"]
}
}
}Quarry works with zero configuration. These environment variables are available for customization:
| Variable | Default | Description |
|---|---|---|
OCR_BACKEND |
local |
local (offline, no setup) or textract (AWS, better for degraded scans) |
QUARRY_ROOT |
~/.quarry/data |
Base directory for all databases (log path configured separately via LOG_PATH) |
CHUNK_MAX_CHARS |
1800 |
Max characters per chunk (~450 tokens) |
CHUNK_OVERLAP_CHARS |
200 |
Overlap between consecutive chunks |
For advanced settings (Textract polling, embedding model, paths), see Advanced Configuration.
Quarry works entirely offline by default. Cloud backends are available for specialized use cases.
Better character accuracy on degraded scans, faxes, and low-resolution images. For clean digital documents, local OCR produces equivalent search results.
export OCR_BACKEND=textract
export AWS_ACCESS_KEY_ID=...
export AWS_SECRET_ACCESS_KEY=...
export AWS_DEFAULT_REGION=us-east-1
export S3_BUCKET=my-bucketSee docs/AWS-SETUP.md for IAM policies and full setup.
Cloud-accelerated embedding for large-scale batch ingestion (thousands of files). Search always uses the local model regardless of this setting.
export EMBEDDING_BACKEND=sagemaker
export SAGEMAKER_ENDPOINT_NAME=quarry-embeddingDeploy with ./infra/manage-stack.sh deploy. See docs/AWS-SETUP.md for details.
- Google Drive connector
quarry sync --watchfor live filesystem monitoring- PII detection and redaction
For product vision and positioning, see PR/FAQ.
uv run ruff check .
uv run ruff format --check .
uv run mypy src/ tests/
uv run pytest # run the test suiteQuarry is fully typed (py.typed) and can be used as a Python library. See CONTRIBUTING.md for setup, architecture, and how to add new formats.
- Changelog
- AWS Setup Guide — IAM, S3, SageMaker deployment
- Search Quality and Tuning
- Backend Abstraction Design
- Non-Functional Design
- PR/FAQ — product vision and positioning