Put Vaquill wherever your team already works - Claude, Slack, a marketing site, a Google Sheet. Every integration is open-source, self-hostable, and calls the same Vaquill API under the hood.Documentation Index
Fetch the complete documentation index at: https://vaquill.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
MCP Servers
Plug US statutes, CourtListener, CanLII, and Vaquill’s full corpus into Claude, Cursor, VS Code, or any MCP client.
Chatbots
Legal Q&A in Slack, Discord, Microsoft Teams, Telegram, WhatsApp, or Signal with thread memory and cited sources.
Widgets
Embed a chat widget on any site - one script tag, an iframe, or a full Next.js deployment with voice and history.
Browser Extensions
Research from any browser tab without leaving the page. Chrome, Edge, Brave, Arc, Opera.
Automation
n8n and Make.com templates that turn a Google Sheet of questions into a Sheet of answers and cited sources.
GitHub
Every integration is MIT-licensed and ready to fork.
Pick an integration
| If you want to… | Use |
|---|---|
| Ask legal questions from Claude / Cursor / VS Code | Vaquill MCP |
| Search US federal + state case law from an AI tool | CourtListener MCP |
| Search Canadian case law from an AI tool | CanLII MCP |
| Add legal Q&A to your Slack workspace | Slack bot |
| Add legal Q&A to your Discord server | Discord bot |
| Add legal Q&A to Microsoft Teams | Microsoft Teams bot |
| Add legal Q&A to Telegram | Telegram bot |
| Add legal Q&A to WhatsApp | WhatsApp bot |
| Add legal Q&A to Signal | Signal bot |
| Embed a chat widget on a marketing site | Embedded Chat Widget |
| Self-host a chat widget with Docker | Docker Widget |
| Run a feature-rich widget with voice + history sidebar | Widget Pro |
| Research from any browser tab | Chrome Extension |
| Batch-process legal questions from a Google Sheet | n8n / Make.com |
Common architecture
Every integration is a thin wrapper: take input from the surface (Slack message, browser popup, webhook), callPOST /api/v1/ask, render the answer with cited sources.
One API key (vq_key_...) from your dashboard drives them all. Configuration is via environment variables; every integration ships with a Dockerfile and at least one cloud-deploy recipe.
Build your own
To add a surface we do not ship (Outlook, Notion, a CRM, an internal portal):- Generate a key in your dashboard.
POST /api/v1/askwith{ "question": "..." }andAuthorization: Bearer vq_key_....- Render
data.answer; iteratedata.sourcesfor citations (case name, court, citation, PDF link). - Maintain
chatHistoryclient-side for multi-turn threads.