Questlaw Library runs on your own machine — the client starts it, so there is no endpoint to ping. 49 installs a week from npm. Last commit 27 Oct 2026.
Access your QuestLaw library in GenAI Tools.
What the code does
We read the source, 6 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
execFileSync(impl.command, ['add-generic-password', '-U', '-s', SERVICE, '-a', account, '-w'],
bytes = fs.readFileSync(path.join(vendorDir, file));
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add questlaw-library -e 'QUESTLAW_DISCLOSURE_ACK=<QUESTLAW_DISCLOSURE_ACK>' -- npx -y questlaw-mcp{
"mcpServers": {
"questlaw-library": {
"command": "npx",
"args": [
"-y",
"questlaw-mcp"
],
"env": {
"QUESTLAW_DISCLOSURE_ACK": "<QUESTLAW_DISCLOSURE_ACK>"
}
}
}
}[mcp_servers.questlaw-library]
command = "npx"
args = ["-y", "questlaw-mcp"]
env = { QUESTLAW_DISCLOSURE_ACK = "<QUESTLAW_DISCLOSURE_ACK>" }{
"mcpServers": {
"questlaw-library": {
"command": "npx",
"args": [
"-y",
"questlaw-mcp"
],
"env": {
"QUESTLAW_DISCLOSURE_ACK": "<QUESTLAW_DISCLOSURE_ACK>"
}
}
}
}{
"servers": {
"questlaw-library": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"questlaw-mcp"
],
"env": {
"QUESTLAW_DISCLOSURE_ACK": "<QUESTLAW_DISCLOSURE_ACK>"
}
}
}
}Put your own value in place of
<QUESTLAW_DISCLOSURE_ACK> (Set to 'i-understand' to confirm you accept that this connector shares your decrypted library, including captured opinion text, with your AI client and its provider. Without it the server serves nothing).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
QUESTLAW_VAULT_FILE (A .qlvault export, or a folder to take the newest one from. Defaults to ~/Downloads), QUESTLAW_KEY_ACCOUNT (Which account in the OS secret store holds the QuestLaw account key. Defaults to 'default'. Run `questlaw-library-mcp setup` to store one).
Alternatives to Questlaw Library
same job, measured the same wayGive Claude, Cursor, or another AI assistant direct access to your QuickSnip library.
Your GTM accounts, agents and Inbox, in your AI tool.
Access all your MCPBundles tools in one place. Unified hub for all enabled bundles.
AYA command library as MCP tools: run AYA patterns and commands under your own account.
Access your app analytics, ASO tools, and app market intelligence with Appfigures.
Bring your Knacco library into your AI tool: browse, search, read guides and download files.
Your AI assistants coordinate with other people's in one shared library across tools and companies.
Totem — talk to your wearables with AI. Today: full Whoop access (48 tools).
Questlaw Library — questions
Answers built from our own checks of this server.