Quote with Claude Code and Knack
Claude Code talks to Knack over the same connector as everything else, and it's the one tool with a shortcut: /mcp__knack__quote J-1043 opens a session with the pack, the first page of every drawing and the photo count already in front of it.
On every plan · Knack sends nothing to any AI provider · every answer is a draft
Setup
Two minutes, once.
What you need:
- A Knack account where you're the owner or an estimator (the connection reads costs).
- Claude Code installed and signed in.
-
1
Create a token in Knack, or sign in from Claude Code
Either works. In Knack, open Settings → Integrations → AI tools, press Create token, and copy the Claude Code command Knack shows you — the token is filled in. Or add the connector without a token and let Claude Code sign you in to Knack (
/mcpin Claude Code, then Authenticate). -
2
Run the command
In a terminal:
claude mcp add --transport http knack https://api.knackapp.co.nz/mcp --header "Authorization: Bearer knk_…your token…" --scope user
Or, to sign in instead of pasting a token:claude mcp add --transport http knack https://api.knackapp.co.nz/mcp --scope user
--scope useris the part that makes it yours everywhere. Leave it off and Claude Code registers Knack against the one folder you ran the command in — a session started anywhere else won't see it. -
3
Start a session
Open Claude Code in any folder and type:
/mcp__knack__quote J-1043
The double underscores are Claude Code's own naming for a connector's commands — in the/menu it shows up as knack:quote (MCP), so you can pick it from the list instead of typing it. Use the job number, the job's name, or the customer's name. Claude gets the working pack, the drawings and the site photos in one turn, summarises the job, lists what's already counted, and asks the first questions.
Your first session
Bring a job that's worth the conversation.
Work the job up the way you'd work it up with a good estimator: gear from the drawings, hours from the facts you give it, supply, staging, what to ask the client. When the price is agreed, say so — Claude writes the draft quote into Knack and tells you what's still open. If you keep going after that, it reads the draft back from Knack first, so anything you changed in the builder stays yours.
Everything it writes into Knack is a draft you read, edit and send yourself.
Fair questions
Straight answers.
Token or sign in — which should I use?
Sign in if you can: the connection refreshes itself and ends when you leave the account. A token is right for a machine that runs unattended, or when you want to hand a tool exactly one credential you can revoke by name.
What can it read, what can it write, and what can't it touch?
A connected AI can read this account's customers and sites, your drawings and site photos; every quote you have sent, line by line, with whether it was won; your recipes, symbol links, playbooks and templates; and your costs and margins. It can also add and correct customers and jobs, and set up and change your pricing — price-book items and their prices, your default markup and charge-out rate, recipes (including confirming their rates), symbol links, other names for items, playbooks and quote templates — when you ask it to. These are real changes, not drafts: a price it changes is what new quote lines use from then on. It can never delete anything, and never send a quote to your customer: you do that. Connect only tools you trust — a token or connection can be revoked at any time. It cannot see any other Knack account, and there is nothing about payments in Knack for it to read.
Does it write the actual quote?
No. Everything it writes into Knack is a draft you read, edit and send yourself. The draft lands in the quote builder with every line still yours, and nothing reaches a customer until you press Send.
Other tools: ChatGPT · Claude · Grok · Grok CLI · Cursor · Codex · Gemini CLI · Claude Desktop · or the overview →
Bring the next big one you have to price.
Thirty days, every plan feature, no credit card.