Available in the Claude Connectors Directory
Add Vaquill AI Primary Law in one click from Claude. No API key to paste. Works in claude.ai,
Claude Desktop, Claude Code and Cowork.
This is the only path that works in Cowork. A Cowork session runs in an Anthropic cloud container that never sees your machine’s environment, so a key held in
~/.zshenv cannot reach it. See Claude Code plugin for the difference, and why the plugin cannot cover Cowork on its own.Connect
1
Open Claude's connector settings
On claude.ai: Settings > Connectors > Add custom connector.
On Claude Desktop: the same Connectors panel.
In Claude Code:
claude mcp add --transport http --scope user vaquill https://mcp.vaquill.ai/mcp, then /mcp to complete sign-in.2
Paste the URL
3
Click Connect and approve
Claude sends you to Vaquill to sign in, then shows a consent screen naming what Claude is asking for. Approve it once and the decision is remembered, so reconnecting later does not ask again.
4
Make one live call
A green connection proves nothing. See Verify it works below.
Verify it works
The only real test is one live call, and the cheapest one is free:“Use Vaquill to list statutes coverage for California.”
list_statutes_coverage costs 0 credits. A normal response means you are done. An error means the connection never carried an identity.
Test each surface separately. Claude Code, claude.ai, Claude Desktop and Cowork take different code paths, and Cowork syncs its tooling at session start, so start a fresh Cowork session rather than reloading an open one.
What happens to your API key
You do not create one. On your first connect, Vaquill provisions a key for the connector automatically and holds it server-side. Claude never sees it. Two consequences worth knowing:- It does not count against your plan’s key cap. Connector keys are tracked separately from the keys you create by hand, so connecting does not consume one of your 2 (or 5, on Business) active-key slots, and it cannot lock you out of creating one.
- It does not appear in your dashboard key list. That list shows only keys you created, so the connector’s key cannot be seen or revoked from there. Disconnecting the connector in Claude stops Claude using it, but does not itself revoke the key; contact support if you need it revoked outright.
Scope: United States only
The connector serves the US corpus: the US Code, all 50 state codes plus DC and Puerto Rico, federal and state regulations, court rules, constitutions, agency guidance and adjudications, session laws and the Federal Register. India is not available over OAuth. The India corpus is served from a separate, deliberately disjoint document athttps://mcp.vaquill.ai/in/mcp, and it authenticates with a vq_key_ API key in an Authorization header rather than a Connect button. There is no consent flow for it yet. See Vaquill MCP for the key-based setup.
That separation is intentional in both directions: a US connection never exposes India tools, and the reverse. Connect only the corpus you need, because every connected server keeps its tool definitions in context for the whole conversation.
Which one should I use
Use the connector for Claude with no setup, and as the only option in Cowork. Use the plugin in Claude Code when you want the ten slash commands and the research skill on top of the tools. Use an API key for any client that is not Claude.
You can run the connector and the plugin together, but there is no reason to: both expose the same 25 tools, and two copies of the same catalogue sit in context for the whole conversation.